Data & continuity
Business software data migration: a practical preparation guide
Prepare ERP data migration with item and unit mappings, duplicate cleanup, opening stock, account balances, sample validation, backups and cutover ownership.
Kaduwela, Sri Lanka · Local and remote delivery
The practical answer
Start with an outcome you can verify.
Prepare a migration by defining what must move, preserving a controlled source export, mapping identifiers and units and reconciling a sample before cutover. Approve opening stock and account balances explicitly; a completed import is only one step in establishing a reliable starting position.
Choose what the new system needs to start operating
Separate master records, opening quantities, account balances, attachments and historical transactions. Moving the full history may be useful, but it adds mapping, validation and exception work. Sometimes a controlled archive plus an agreed opening position is the better first step.
List each source system and its export options. Name the business owner who can explain a field or resolve a duplicate. Do not send unnecessary personal or financial records in an initial sales enquiry; use a small anonymized example to discuss the structure.
Map stable identifiers, units and locations
An item name is not always a reliable identity. Similar names, renamed products and duplicate barcodes can cause records to merge incorrectly. Preserve the mapping between old and new identifiers so staff can investigate an imported record.
Check purchase and sales units, decimal precision, container or pack conversions and branch names. A quantity can import successfully but mean the wrong thing if one system records cartons and another expects pieces. Record transformation rules and approve the exceptions.
Reconcile opening stock and balances using agreed definitions
Choose the cutoff date and the totals that will be compared. For stock, use the required location and item detail. For accounts, distinguish opening customer credit, supplier balances, advances and unapplied payments where relevant to the scope.
Run a sample migration before the live one. Compare record counts and totals, then inspect representative rows and transactions. A matching grand total can conceal offsetting errors, so include both summary checks and detailed examples.
Control changes during the cutover window
Decide whether source entry will pause, continue with a delta export or follow another controlled process. Avoid two teams independently correcting the old and new records without a reconciliation plan. Identify who signs off the final opening position.
Keep a controlled source copy and a recovery path. Test that the relevant backup can be restored and that its contents are sufficient for the agreed recovery. Access to exports and backups should be limited to the people who need them.
Validate the first real operating cycle
After import, run a representative purchase, sale, return, payment and report using the imported records. Confirm that search, permissions, units and balances behave as expected. Invite the people who will use the data to review the result.
Keep an issue register with the source reference, observed difference, owner and correction decision. Once the business approves the opening position, subsequent corrections should remain explainable. The aim is a reliable operating record with a clear history of how it was established.
Compare the decisions and the evidence
| Data group | Prepare | Validate |
|---|---|---|
| Items and parties | Identifiers, duplicate decisions and required fields | Counts, mappings and representative records |
| Stock | Units, locations and cutoff quantities | Item/location detail and totals |
| Account balances | Balance definitions and payment treatment | Party-level figures and control totals |
| History and files | Scope, references and permitted access | Searchability, relationships and recovery |
Take it to your next discussion
Your preparation checklist
0 of 12 reviewed
Use this as a discussion checklist. Ticks are kept only while this page is open.
Download the blank checklistQuestions before the next step
Common planning questions
Can you import every old transaction?
That depends on the available exports, data quality, relationships and the scope agreed after review. A complete-history migration needs its own mapping and reconciliation work.
Why can an imported quantity still be wrong?
The source and target may use different units, pack conversions, locations or decimal rules. Validate meaning and business totals as well as whether rows were accepted.
Should we email the full customer database for a quotation?
Start with an anonymized sample and a description of the data volume and structure. Agree a suitable transfer and access process before sharing production records.
Who signs off the opening balances?
The business should appoint owners who understand the underlying stock and account records. The implementation team provides mapping and reconciliation evidence for their approval.
Supporting references
The NCSC guidance emphasizes checking a backup’s contents and knowing how to restore it. A migration plan should include this practical recovery check. NCSC: backing up your data (opens a new tab)
Bring the operating problem
Let’s work through your actual requirements.
Tell us your business type, users, branches, current system and the task you want to improve. We’ll use that context to discuss the right next step.