Apprenticeship software migration guide: four-phase blueprint

Phase 1: Discovery and scope lock

• Define exact data entities in scope by programme type and cohort.
• Map critical reporting outputs required by delivery and leadership.
• Agree acceptance criteria before technical migration begins.

Phase 2: Mapping and transformation

• Map learner, evidence, OTJ, review, and progression records.
• Document any field conversions and data normalization rules.
• Flag records requiring manual review before import.

Phase 3: Validation and parallel run

• Validate sample cohorts with tutor, manager, and admin users.
• Reconcile priority reports between old and new workflows.
• Run parallel delivery long enough to confirm confidence.

Phase 4: Cutover and stabilization

• Schedule cutover with clear rollback criteria.
• Track incidents, response times, and user adoption weekly.
• Capture process improvements and lock operating standards.

Frequently asked questions

What are the four phases of an apprenticeship software migration?

Discovery and scope lock, data mapping and transformation, validation and parallel run, then cutover and stabilization. Each phase has distinct sign-off criteria before moving to the next.

What is the biggest risk in an apprenticeship data migration?

Insufficient validation of learner records, OTJ totals, and evidence history before cutover. Providers should reconcile priority reports between old and new systems during a parallel run before committing to go-live.

How long should a parallel run last during an apprenticeship platform migration?

Long enough to confirm confidence across all programme types and reporting cycles — typically two to four weeks depending on cohort size and complexity. The parallel run should include tutor, manager, and admin user validation as well as reconciliation of key reports.