Business software · 3 min read
Data migration checklist for business software
A safe migration preserves the meaning of records, not just their row count. Define what moves, clean and map the data, rehearse the import and reconcile the result before switching systems. Keep a protected source backup and an agreed fallback until the new system is accepted.
By Raja Wahab, Co-founder, Fixby Studios · Published · 3 min read
Decide what needs to move
List the record types, attachments and history your users actually need. Bringing every old field into a new system can preserve years of confusion. Equally, leaving out important relationships can make apparently complete records unusable.
Assign an owner who can answer questions about meaning. A developer can transform a date format, but cannot decide whether a blank completion date means unfinished, unknown or not applicable.
Create a mapping sheet
| Source detail | Decision to record |
|---|---|
| Customer identifier | How it matches the new customer record |
| Status values | Which old statuses map to which new statuses |
| Dates and times | Format, timezone and treatment of missing values |
| Duplicates | Merge rule and who approves uncertain matches |
| Attachments | Where files go and who may access them |
Clean without destroying evidence
Keep the original export unchanged and work on a copy. Record transformation rules so the process can be repeated. Flag uncertain records for review instead of quietly guessing. If a name or address is ambiguous, a human decision may be required.
Use only the data necessary for testing and protect copies appropriately. Development environments should not become forgotten stores of live customer information.
Rehearse the whole move
Import a representative sample, then a full test export where appropriate. Compare record counts, totals, relationships and a sample of individual histories. Ask users to perform their normal tasks, because technically imported data can still appear in the wrong place.
Record how long the process takes. That helps plan the final cutover rather than discovering too late that the system must be unavailable longer than expected.
Plan cutover and rollback
- Agree when the source stops accepting changes.
- Take the final export and record its time.
- Run the documented import and validation checks.
- Decide who authorises the new system to become the source of truth.
- Define the conditions and practical steps for reverting.
Check after launch
Monitor missing records, duplicate reports and user workarounds. Keep a named contact for migration issues and document corrections. Decommission old access only after the agreed checks and retention decisions have been completed.
A successful migration is one users can trust, explain and recover from, not merely one that displayed a completion message.
Sources
Raja Wahab is co-founder of Fixby Studios, a Huddersfield studio building websites, SEO, social media and business software for small, owner-managed businesses across West Yorkshire.
Next step
Let's get your business seen.
Get a free Blueprint with a clear plan, honest pricing and no jargon.
Tell us which task takes too much time and we'll assess a focused software or automation project. Business software and automation
Prefer to talk it through? Contact Fixby Studios, email info@fixbystudios.co.uk or call 07737 067552.