Start a project Migration planning tool
Move the workflow with the record. Build a practical migration brief that keeps unknowns, evidence references and accountable roles visible.
Free working tool
Map the records, test a representative transfer and agree who owns continuity and cutover.
A practical output
Capture the evidence, owner and unresolved decisions behind the work.
Versioned field/status mapping, evidence-link handling, exclusions and access rules.
Trial population and counts, exception log, document/link checks and permission checks.
Authoritative-system decision, treatment of changes during the move and user-support route.
Cutover authority, recovery/rollback conditions, retained-record access and recorded acceptance checks.
Your original entries, a separate owner for each handoff, open questions, the observable outcome and a review point.
Download JSON or spreadsheet-safe CSV, or print the completed record. The tool does not inspect evidence or give a readiness score.
Explore Journey migration and rolloutUse this before agreeing a move between apprenticeship systems, or before a Journey evaluation. Start with a bounded workflow and a representative cohort description. You can use the record with any supplier; it does not depend on buying Journey.
Choose an observable task, such as a tutor preparing and saving a review with the right programme context and usable evidence links. State the cohort and exclusions. A copied database or a successful import is not the same as an accepted delivery workflow.
List source systems, document stores and record categories. Identify the source of truth for current plans, review decisions, programme history and permissions. Separate material needed in the destination from material that needs retained access elsewhere.
Record how dates, statuses, owners and evidence references should behave. Two fields called complete may represent different decisions. Give the mapping a version and an accountable role, and keep unresolved meanings in the exception log.
Compare agreed record counts and selected values; open relevant evidence links; test the intended user permissions. Include an ordinary record and a meaningful exception. Record what failed, who will resolve it and which checks must be repeated after correction.
Agree which system is authoritative during the trial, how new changes are captured and where staff obtain help. Consider active reviews and other time-sensitive work. A migration plan should explain the transition period as well as the destination.
Name the role that can accept the move. Record the acceptance evidence, unresolved exceptions, rollback triggers and recovery checks. Review retention and decommissioning separately; moving records does not itself authorise deleting the source.
The fictional example moves a single programme team’s review workflow. Mapping v0.2 has an unresolved complete status, the trial has not run and the cutover owner is unknown. The output therefore keeps mapping, reconciliation and cutover open. It still preserves the desired outcome: a tutor can save a review, open its evidence and leave a visible next action.
Create a record to obtain four separate handoffs: mapping, trial reconciliation, continuity and cutover/recovery. Each includes an owner role, evidence to inspect and unresolved points. Evidence recorded means you report that a record exists; the tool does not inspect or approve it. Blank ownership is shown as Owner not assigned.
Use record categories, document titles and fictional examples. Do not paste learner names, identifiers, support notes or evidence. The planner runs in your browser and does not upload entries. Its downloads contain your notes, so store and share them through an appropriate organisational route.
This tool prepares an operational software migration. It does not convert, validate or submit ILR data, establish funding entitlement or determine retention periods. Identify those responsibilities separately and use the current rules, contracts and submission services applicable to your provision.
Ask the supplier to demonstrate the exact workflow and exceptions in your acceptance outcome. Record which steps are supported now, which require configuration or integration and which remain planned. Export the record after every agreed revision; reloading this page clears unsaved entries.
We are evaluating [workflow] for [cohort description], moving [record categories] from [sources] to [destination]. [Excluded records] remain accessible through [retained route].
In mapping [version], [source field/status] means [meaning]. The destination will represent it as [meaning]. [Role] will resolve [open difference] and record the decision in [reference].
[Role] will reconcile [agreed counts and values], open [evidence-reference categories] and test [user permissions]. Exceptions will be recorded in [log] and rechecked after correction.
[Role] will inspect whether [user] can complete [observable task]. Cutover requires [decision evidence]. If [trigger] occurs, [role] will follow [recovery reference].
