Moving Your Data to a New System Without Stopping Work
The hardest stage in moving to a new system is not choosing it — it is the days just before it goes live. The old data needs cleaning and decisions, and meanwhile the team is caught between two systems: the old one has stopped and the new one has not started. Whatever happens in that gap is either lost or entered twice, and that is where most opening-balance errors come from.
Many projects stumble here — not because the new system is weak, but because the data went in exactly as it was, errors included. The reports came out wrong, and the team lost confidence in the system within the first month. This guide walks through how to run the migration step by step.
What data migration actually means
Migration means converting what you hold in the old system — or in spreadsheets and paper ledgers — into a form the new system understands and can work with. It is not copy and paste. It is three sequential stages: extracting the data, cleaning and reshaping it, then loading and verifying it.
The most important rule: a new system does not fix broken data. If an item is entered twice, it stays duplicated, its stock quantity splits between the two records, and you discover the problem two months later, when rolling back is no longer easy.
Decide what moves and what stays archived
The first mistake most businesses make is trying to move everything from day one. The result is a heavy system full of dead records nobody will ever open. It helps to separate data into three categories:
| Data type | Decision | Note |
|---|---|---|
| Master data (customers, suppliers, items, employees) | Move in full | After cleaning and removing duplicates |
| Opening balances (stock, receivables, banks) | Move as of a set date | Must match the physical count and the accounts |
| Historical transactions (old invoices and vouchers) | Usually kept as an archive | Retain a copy you can go back to |
Before you decide to discard the old system's archive, note that Saudi e-invoicing and tax rules place requirements on retaining invoices and records for defined periods. Review the official rules published by the Zakat, Tax and Customs Authority at zatca.gov.sa, or consult your accountant, before shutting down or deleting any legacy system.
Practical migration steps
- Set a cut-off date: the day balances are calculated and after which all entries go into the new system. It is usually the start of a month or a fiscal year.
- Extract the data: export each file separately and keep an untouched original copy you never edit.
- Clean and standardise: remove duplicates, unify name formats, codes and mobile numbers, and fill in missing mandatory fields.
- Test on a sandbox: load the data into a test environment first, never straight into the live system.
- Reconcile the numbers: compare stock, receivables and balance totals across both systems before you sign off.
- Load and close the old system: once reconciliation passes, go live and block new entries in the old system so data does not split across two places.
Cleaning up: where to start
- Duplicates: the same customer recorded three times with slightly different spellings.
- Missing fields: items with no unit of measure, suppliers with no contact number.
- Inconsistent formats: multiple date formats, mobile numbers sometimes with a country code and sometimes without.
- Dead records: items discontinued for years and customers who stopped buying long ago — flag them rather than carrying them over as they are.
- Arithmetic errors: negative stock balances or unexplained differences. Fix them before the move, not after.
Do not move the mess into a new system and expect the system to sort it out. Software reflects the quality of what you put into it; it does not create it.
Common mistakes
- Migrating without a complete, restorable backup of the old system.
- Switching the old system off before confirming the numbers match in the new one.
- Assigning the whole migration to one employee, with no review by the accountant and the stock controller.
- Picking a go-live date at peak season instead of a quiet period.
- Treating "the data appeared in the system" as proof of success, without checking the totals.
Checklist before final sign-off
- Is there a complete backup of the old system's data stored somewhere safe?
- Does the stock balance in the new system match the latest physical count?
- Do customer and supplier balances match their statements of account?
- Have you run a full cycle on migrated data: order, invoice, collection, report?
- Does the team know the cut-off date, and when entries in the old system stop?
- Have you named an owner for handling any errors that surface in the first two weeks?
How to close the gap
The gap exists because recording requires a ready system. But if the entry point is a WhatsApp message, the team can keep recording from day one while old balances are migrated in the background at a sane pace. The order becomes: switch on the recording channel first, then clean and migrate, then reconcile. Work never stops for a day, and the final reconciliation is between two real numbers rather than a number and somebody’s memory.
See a system run from WhatsApp for how operations can start before migration finishes.