A stalled migration got moving again, for one-fifth of the earlier spend.
An FAA-regulated training provider had spent about $1 million on a platform move. We built a repeatable way to finish it.
Three times the work, in less than half the time.
Those comparisons are the client's own, against the roughly $1 million spent before we joined.
| Before Runpoint | With Runpoint | |
|---|---|---|
| Spend | About $1M | About 1/5 |
| Time | Baseline | Under half |
| Work done | Baseline | 3× |
Each customer moves with its courses, records and certificates intact.
Migration process
Courses, settings, learner records, certificates and progress move together.
Content controls
Staff update courses, tests and customer versions without a developer.
Migration checks
Exceptions are found and moved records are checked at each cutover.
Reusable parts
Shared data, editing and reporting pieces carry on after the move.
Every customer cutover follows the same steps, with checks built in.
- 01Courses and tests · Move
- 02Customer settings · Move
- 03Learner records · Move
- 04Certificates and progress · Move
- 05Exceptions found · Check
- 06Records checked · Check
- 07Customer cut over · Move
The migration had to keep moving while the plan kept changing.
- 01
Move more than files
Each cutover carried courses, settings, records, certificates and progress, still connected.
- 02
Keep up with change
Requirements kept changing and the scope kept growing, so the process changed too.
“The speed of iteration will convince people. It convinced me these last few months.”
What could come next
Next, the provider can harden the platform, improve analytics and automate more of course building. Final cutover is still ahead.
Is a project stuck at your company?
Tell us where it stalled and what has been spent. We'll say what it would take to finish and whether we're the right team.