Moving to a new business management system is a major decision, but the hardest part is often the data, rather than choosing or configuring the system. Years of customer, item, invoice, and balance data are spread across old software, Excel spreadsheets, messages, and files, each recorded differently.
If this data is migrated as it is, the new system will inherit the old system’s problems. If it is not migrated carefully, the team will lose trust from the start and return to their own spreadsheets. This guide organises migration into three steps: selection, cleaning, and a trial run.
Not all data is worth migrating
Identify the data you actually need in the new system: active customers, current products, and balances. Ask of each data type: will anyone use it in daily work after the move?
Old data can be archived instead of migrated. Keep a complete copy somewhere secure for reference when needed, but do not burden the new system with data nobody will use.
Classify your data before deciding
- Core data to migrate: Active customers and suppliers, items still sold, units of measurement, and warehouses.
- Opening balances: Stock quantities and customer and supplier balances at the migration date. These need particular accuracy and approval from the person responsible for finance.
- Open transactions: Undelivered sales orders, purchase orders not yet received, and outstanding quotes.
- Historical records: Old invoices and transactions. Archiving is usually enough unless there is a clear reason to migrate them.
Set the migration date
Choose a clear point in time for calculating opening balances, preferably at the end of an accounting period or during a quieter time. Everything before this date stays in the old system, and everything after it is recorded in the new one. This clarity prevents recording the same transaction in both systems.
Review your invoicing requirements too. If your business must issue electronic tax invoices, make sure migration does not break invoice sequencing or conflict with tax system requirements. Consult your accountant before setting the date.
Clean before migrating
Check for duplicates and errors in names and numbers before migration. Errors travel with the data, and correcting them in the new system after they are linked to invoices and transactions is far harder than correcting them in a spreadsheet beforehand.
Most common problems
- Duplicates: One customer recorded twice under slightly different names, or one item with two codes.
- Inconsistency: Units of measurement written in different ways, different spellings of cities, and mobile numbers in multiple formats.
- Missing data: Customers without tax numbers, or items without units or cost prices.
- Obsolete data: Discontinued items and customers who have not dealt with you for a long time.
Prepare migration templates
Request the new system’s import templates before cleaning begins, and organise your data directly in that format. Each system expects specific columns and formats; using the correct template from the start saves an entire round of rearranging. If your item data needs organising from the ground up, the article on preparing product data explains how to build an organised spreadsheet for it.
Keep familiar codes
If your team knows items or customers by specific codes in the old system, consider keeping them or mapping them to new codes. Changing every code at once confuses warehouse and sales users and makes comparing systems during the trial harder.
Prepare a simple mapping table linking each old code to its new code. It will help when checking balances and finding old transactions in the archive after migration.
Assign someone to approve each part’s accuracy. The sales manager approves customer data, the warehouse manager approves items and quantities, and the accountant approves balances. This approval is a sign-off that the data is fit to start with, rather than a formality.
If customer data is scattered and follow-up is unclear, you may find the article on Organise customer follow-up before choosing a system helpful before migrating it.
Do not leave cleaning until the last moment before migration. Start early alongside system setup, because discovering a major item-data or balance problem just before launch leaves two difficult choices: delay migration or start with data you know is wrong.
Trial run
Run the new system on a data sample first and compare results with the old one. The sample should represent real cases: a regular customer, a customer with a balance, an item with multiple units, and a purchase request requiring approvals.
What should you test?
- Do opening balances match the old system at the migration date?
- Do quantities change correctly after a sale or receipt?
- Are invoices issued with the required data and format?
- Does each user see only what they need according to their permissions?
- Do core reports produce figures that can be reconciled with another source?
Ask actual users to carry out their usual processes during the trial, rather than relying only on the implementation team. They will spot missing steps and unclear fields, and this is also a chance to train them before full adoption.
Go-live plan
Before full adoption, write a short migration plan: when transaction entry stops in the old system, when final balances are extracted, who imports and checks them in the new system, and when the team starts using it.
Also define whom users should contact when an initial problem arises and how feedback is recorded. A clear route for questions prevents employees from solving problems in their own ways or returning to old spreadsheets without telling anyone.
Do not shut down the old system too soon
Do not stop the old system before verifying the new one. Keep at least read access until you confirm daily processes and reports work correctly and the team is comfortable with the new system.
Migration is a core part of any system project’s scope, rather than a final extra step. This is why we define data, permissions, and the trial run before implementation in our service for a business resource planning system.
Frequently asked questions
Can all historical data be migrated?
It is technically possible in many cases, but adds effort and complexity and requires more cleaning. In most cases, migrating balances and open transactions and archiving the old history for reference is enough.
Who handles data cleaning?
Your team is best placed to identify correct data, so they provide approval. Technical preparation, such as arranging files in import templates and detecting duplicates, is agreed within the scope of work.
Will both systems run together for a while?
It is preferable to keep the old system available for reference until the new one is verified, while clearly defining where new transactions are recorded to avoid duplication.
How do I start?
Describe the systems and spreadsheets you currently use through contact page, and we will review together what needs migrating and what can simply be archived.