Move your item lists, balances and useful history into the new system, checked.
Data migration brings your item list, customers, vendors, balances and the history worth keeping into the new system, cleaned and checked before anybody goes live. Your own people verify a sample. Once the cut-over date passes, the old software is read-only and nothing is kept in two places.
Migration decides whether a new system is used or quietly abandoned, more than the screens do. If a counter has to look up a customer’s credit balance in the old software, the staff keep the old software open. Within a month there are two versions of the truth.
What comes across is agreed first, in writing: masters, opening balances, and how far back the history goes. It is cleaned, loaded, and checked by the people whose numbers they are. Then one date is fixed, and everybody works in one place after it.
What your team uses today.
The module takes over these, one at a time, so nothing has to stop while it is set up.
- Copy and paste from sheet to sheet
- A private file of cleaned rates
- Entering the same bill in both programs
The problems this is meant to ease.
What data migration and import does.
What this looks like in a working week.
Illustrative scenarios, written to show the shape of the work. They are not accounts of client systems.
The people who open this every day.
From first conversation to daily use.
Decide what moves
List the data you hold and what you want kept. The note settles it. Some data moves, some stays, some is dropped.
Collect the sources
Hand over exports, sheets and old reports. A register returns showing each file, its date and its owner.
Trial load
A cleaned copy goes into a test area. Staff try it. Rejected rows come back with a reason against each.
Verify and tie out
Your own people check a sample and the balances. Each set is signed off by name and date. Nothing moves without it.
Cut over
On the agreed date the old software turns read only. A closing note records what was loaded. It also lists what stayed behind.
How you would know it is working.
Record where you stand before it goes live, so the change is measured against your own figures.
- Rows loaded against rows rejected, by import
- Opening balances as agreed against as loaded
- Data sets verified, with the verifier named
- Duplicates found and resolved in the item list
- Entries still made in the old software after cut-over
It is one part of a system, not an island.
A module earns its place by what it passes to the next one. These are the connections we set up most often.
- Your accounting software
- Your old billing software
- Excel and CSV files
- Product management
- Customer ledger
Products that include it.
How we would put it in.
Turn the capability into an acceptance check.
Agree what a correct result looks like for this module, including the case that needs a person to intervene.
Opening balances for the ledger
Which differences must be resolved before the old system is retired?
For “Opening balances for the ledger”, compare a sample of linked records and control totals across the old and new systems. Assign an owner to every unexplained difference before cutover.
Background reading: AWS: source and target validation
Item list from billing software
Can you explain the balance from its original documents?
Select a partly settled example in “Item list from billing software”. Ask for the invoice, allocated receipts and remaining balance to be shown together before agreeing the opening figures.
Background reading: ERPNext: outstanding invoices
Questions owners ask about data migration and import.
Our old vendor will not give us our data. What then?
Firms do arrive with no export. We work from whatever can be printed or exported, such as reports and PDFs, and rebuild the masters and balances from those. Some of it is retyping, and we say how much before you commit.
Can we run both systems for a month to be safe?
We advise against it. Two systems means two versions of every balance, and staff choosing whichever is easier that day. Pick a date, move, and keep the old one open for looking up history.
How much history should we bring?
Balances always, and a year or two of transactions for most businesses. Older data is better kept as an archive you can open when needed than loaded and slowing everything down.
Who checks that it came across correctly?
Your people, because they are the only ones who know. We start by looking at what your current software can actually export, then your team checks a sample of each list and every opening balance.
Why do migration quotes vary so widely?
Sources, data condition and the history you wish to keep are the levers. Files in odd formats need more cleaning than a tidy export. Limiting history lowers the work. The quote splits the job into parts once we have studied your files.
What sets the pace of a migration?
How fast your people verify. The first usable release is a trial load of items, customers, vendors and balances for them to check. Each date is fixed in the proposal.
Businesses that ask for this.
Modules that work with it.
Tell us how you handle data migration and import today.
A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements