Planning a data migration to new business software
Prepare a trial import, verify relationships and set measurable criteria for a safe changeover.

In short
- Write down each field’s meaning, format and authoritative source.
- Include active, closed and unusual records.
- Decide when the old system stops accepting writes and how to catch up changes since the last test.
- Next steps
On this page
Define the source fields
Write down each field’s meaning, format and authoritative source. Record ambiguous statuses and relationships, for example a customer with several addresses. Keep an unchanged export and store conversion rules separately.
Repeat a trial import
Include active, closed and unusual records. Compare counts, totals, keys and a sample of details. Ask users to run the same task in both tools. Repeating the import must not create duplicates.
Set cutover and recovery rules
Decide when the old system stops accepting writes and how to catch up changes since the last test. Set the discrepancies that would postpone launch. Plan how to recover new transactions if the team must return to the old system.
Next steps
Creagrid / actie
Practical checklist
Describe the problem and intended outcome.
Involve the people who use the process every day.
Test the riskiest assumption with a small prototype.
Define tests, ownership and maintenance up front.

