The Data migration tab tracks how data moves from the old systems into the new one. Open it from the project menu: Delivery, then Data migration.
What it's for
Data is loaded several times before go-live, and each practice run should be cleaner than the last. The tab lists every migration object (a kind of data, such as customers or open invoices) and records each load: how many records were extracted, loaded and rejected. The error rate is rejected records divided by extracted records. Each object has a target error rate, so you can see which objects are on track.
The load cycles
- Mock load 1First full trial load
- Mock load 2Fixes applied, error rate falling
- Mock load 3Close to production quality
- Dress rehearsalTimed run of the real cutover
- CutoverThe production load
Before you start
Before you track migration
- The project's plan includes Data migration (Professional, Enterprise or a personal plan)
- Your role can edit data migration
- You have the list of objects with their source system and record volumes
- You have agreed an error-rate target for each object
How to set up and record loads
- Add an object
Select Add object. Enter the Object name and, optionally, Reference, Owner, Source system, Target, Record volume, Error rate target (%), Complexity, Status and Notes. The target starts at 2%. Save with Add migration object.
- Record a load
Select Record a load. Pick the Object and Cycle, then set Status, Planned and Actual dates.
- Enter the counts
Enter Extracted, Loaded and Rejected. Loaded plus rejected cannot be more than extracted.
- Save
Select Add load. The Error rate (%) is worked out on save.
Reading the page
- Objects ready or loaded, Records in scope, the Error rate of the latest cycle against its target, and the Next cycle sit at the top.
- Latest cycle shows extracted, loaded and rejected records and the error rate with its target, and lists any objects above their target, worst first.
- Records by cycle stacks loaded and rejected records for each cycle.
- Error rate by cycle draws the error rate against the target line. For all objects the target is weighted by volume, so big objects count for more.
- Migration objects lists every object with its source and target, owner, volume, complexity, status and latest load.
Each error rate is marked within or above its target, with a tick or an exclamation mark as well as colour. Select Loads on an object to see only its cycles in the charts and a table of its loads. Show all objects goes back.
Object statuses are Not started, Mapping, Build, Testing, Ready, Loaded and Blocked. Load statuses are Planned, In progress, Completed and Failed.
Good to know
- Every chart has a toggle to show its numbers as a table instead.
- The default cutover plan includes the final production data loads as runbook activities. See Cutover.
- Data migration needs Professional, Enterprise or a personal plan. See Plans and pricing.
Who can do this
Admins, project managers, data migration leads, functional leads and technical leads can add, edit and delete objects and loads. Everyone else on the project can see the page. See Roles and permissions.