Data migration checklist: moving business records into new software
Plan a business data migration with a practical guide to cleaning records, mapping fields, testing imports, reconciling results and organising a safe changeover.
By Syed Aalishan Asghar · 17 November 2026 · 9 min read
Your existing records
Files, workbooks and old systems
A controlled migration
Prepare the data.
Prove the result.
Ready for everyday work
Connected, checked and approved
Moving business records into new software is often more demanding than choosing the software itself. Customer details may sit in several workbooks, invoices may use different numbering rules, and important attachments may live in staff folders. An import can finish without an error while leaving the business with incomplete or misleading information. A data migration plan sets out what will move, how it will be checked and when the new system becomes the place people work. This guide explains how to prepare that plan for a customer portal, accounting application, operational system or SaaS product.
1. Decide what the new system actually needs
Start with the work the new software must support on its first day. A service business may need active customers, open quotations, unfinished jobs and unpaid invoices. It may not need every abandoned enquiry from the previous decade. Agree the records required to perform current tasks before asking the developer to transfer everything.
Keep the distinction between migration and retention clear. A record that does not belong in the new application may still need to remain accessible in a controlled archive. Decide who will use that archive, what they need to search and how long the business expects to retain it. Confirm applicable retention obligations with the people responsible for them rather than treating deletion as a technical shortcut.
Write down the boundaries: included systems, record types, date ranges, attachments and exclusions. Name a business owner who can resolve questions about meaning and accuracy. The development team can build an import, but it cannot decide which customer balance is correct or whether two apparently similar records belong to the same organisation.
The migration sequence
Prepare
Choose records and agree cleanup rules
Rehearse
Map fields and test an import
Verify
Check totals, links and documents
Change over
Approve the move and support staff
2. Inventory the source files and their owners
List each source and the person who understands it. Include spreadsheets, existing databases, exported reports, shared drives and separate lists held by individual teams. Record the format, approximate volume and last update. Identify which source is authoritative when several versions claim to contain the same information.
Follow the relationships between records. A customer may have several contacts, invoices, jobs and documents. An invoice may have multiple receipts or credit adjustments. These relationships need stable identifiers so the import connects the right records. Matching on a business name alone can fail when names are abbreviated, misspelled or shared by unrelated organisations.
Preserve an unchanged source snapshot before cleaning or conversion begins. Record where it came from and when it was exported. Work on separate copies so a disputed value can be traced back to the original. This also gives the team a consistent starting point for rehearsal imports instead of testing against a file someone changes halfway through the exercise.
3. Clean records using agreed business rules
Review duplicates, missing required values and inconsistent formats before the final import. Common examples include dates stored as text, telephone numbers with different country-code conventions and customer names entered in several ways. The business should agree what counts as a duplicate and how a preferred record is chosen.
Do not silently invent values to satisfy required fields. If a customer has no email address, decide whether the field should be optional, the record needs review or an alternative contact route should be used. Filling every gap with a made-up address produces a technically complete file that staff cannot trust.
Keep a record of corrections and unresolved exceptions. When two customer records are merged, preserve the reference from each old identifier to the retained one. Where a figure cannot be confirmed, flag it for a named reviewer. A migration is a useful opportunity to improve records, but the cleanup should remain explainable and reversible until the result is accepted.
4. Map fields and preserve their meaning
A field mapping explains how each source value becomes a value in the new system. Record the source column, destination field, expected format and transformation rule. Include units, currencies, time zones and the meaning of statuses. A column called amount may represent a net value in one file and a total including tax in another.
Check how the new product represents concepts that used to be free text. Staff might have entered pending, waiting and on hold for several different situations. If the new system uses defined workflow states, agree which source values map to each state and which ones require review. Do not force an uncertain record into the closest label just to finish the import.
For financial records, involve the person responsible for the accounts in decisions about opening balances, historical transactions and reconciliation. The correct approach depends on what the new application will calculate and retain. Ask for documented rules and independently checked examples. A developer should not reinterpret financial history from column headings alone.
5. Protect access and control external effects
Choose who can export, prepare, upload and approve the data. Business records may contain customer contact details, employee information or documents that should not be copied into every developer environment. Use only the information needed for the task and establish where temporary files will be kept.
Use fictional or appropriately anonymised samples for early mapping work where possible. When realistic data is necessary for a controlled rehearsal, agree access, storage and cleanup arrangements first. Keep credentials out of shared spreadsheets and general migration notes. Record who can authorise a live export and where the approved copy will be transferred.
Make sure rehearsal imports cannot contact real customers, charge payment methods or trigger other live actions. An imported invoice might otherwise cause an automated reminder, or a new customer record might generate an invitation. Review notifications and connected services as part of the migration procedure, including the point at which each one is enabled for normal use.
6. Rehearse with representative records
Run an initial import in a separate environment before scheduling the final changeover. Use records that exercise normal variations: long names, missing optional details, several line items, partial payments, cancelled work and attachments. Include unusual records that staff know have caused problems in the past.
Check the import sequence. Customers may need to exist before their invoices, and invoices before their receipts. Confirm how rejected records are reported and whether a second run updates existing records or creates duplicates. If an import stops partway through, the team needs a defined way to resume or reset it.
Record the time taken for preparation, transfer, import and review. This helps the business plan a realistic changeover window. An import that takes ten minutes may still need several hours of checks and exception handling. Repeat the rehearsal after material changes to the mapping or importer so the final run follows a procedure the team has actually used.
7. Reconcile the result beyond row counts
Compare totals and relationships as well as the number of imported records. A matching customer count does not prove that invoices belong to the correct customers. A plausible overall balance can conceal errors that cancel each other out. Choose checks that reflect the decisions people will make from the new software.
For a quotation and job system, check active customers, open quotations, accepted work, outstanding amounts and attached documents. Select individual examples and trace them from the source through the new application. Ask staff to complete the tasks those records support, such as opening a customer history or preparing a follow-up list.
Keep an exception report showing what was rejected, transformed, omitted or left for review. Agree which differences are expected and which prevent approval. Have the business owner sign off against recorded evidence after corrections are checked. The absence of an import error is one signal; acceptance needs a business review of the result.
What to check after an import
Counts & totals
Included records and financial totals agree with the approved source.
Relationships
Customers, jobs, invoices and receipts stay connected.
Documents
Attachments open and belong to the right record.
Real work
Staff can complete the tasks those records support.
8. Plan the final changeover and recovery route
Choose when the source stops accepting normal updates and when staff begin using the new system. If records continue changing during migration, define how those final changes will be captured. Without a clear cutoff, a payment entered after the export may disappear from the new view, or two teams may work from different versions of the same job.
Assign responsibility for the final export, backup, import, reconciliation and decision to open the system to users. Set the conditions that would postpone the changeover. These might include an unexplained balance difference, missing attachments or an essential workflow that fails with migrated records. Make the decision before staff are asked to rely on the new data.
Document a recovery route and its limits. Returning to the old system becomes more complicated once staff create new records in the replacement. Decide how that new work would be preserved or reconciled if a reversal becomes necessary. Restoring a backup alone may not address transactions entered after the backup was taken.
9. Support staff after the move
Give users a short explanation of what moved, what stayed in the archive and where to report a discrepancy. Show them how old identifiers relate to new records. If a familiar status or report has changed, explain the new meaning rather than assuming the interface will make every difference obvious.
Keep a defined period of closer review after changeover. Ask staff to report missing records, unexpected balances or documents linked to the wrong item. Route those reports to someone who can distinguish a data issue from a product defect or a training question. Record corrections so the team does not make inconsistent fixes across several accounts.
Confirm when temporary exports and rehearsal copies can be removed under the agreed handling arrangements. Preserve the approved migration evidence and source references the business needs. Keep the original system accessible only in the way agreed for the archive, with a clear owner for its security, subscriptions and eventual retirement.
A practical migration checklist before launch
A manageable migration has named owners, clear rules and evidence that the result supports real work. Use the checklist below during planning and again before the final changeover. Mark unresolved questions explicitly rather than allowing them to disappear into an assumption.
Include migration in the software proposal and project schedule from the beginning. It affects discovery, development, testing, staff time and launch. aaliSoft can help assess source records, define the import scope and plan the checks around the business workflows the new product will support.
- Agree included records, excluded history and archive access.
- Identify authoritative sources and preserve an unchanged export.
- Approve cleanup, matching and field-mapping rules.
- Control access and prevent live notifications during rehearsals.
- Test representative records and interruption handling.
- Reconcile counts, totals, relationships and attachments.
- Assign the cutoff, final review and go-live decision.
- Document recovery limits and support after changeover.
Related reading
Software handover checklist: what your business should receive
A practical software handover checklist covering source code, accounts, deployment, backups, documentation, training and support before your project closes.
How to write a software requirements document developers can estimate
Learn how to write a practical software requirements document that defines users, workflows, scope, integrations, acceptance criteria and delivery constraints.
How much does custom software development cost? A practical budgeting guide
Learn what affects custom software development cost, how to compare estimates and how to set a realistic budget for design, development, launch and support.