“We’re switching systems and I’m worried we’ll lose everything.” That worry is reasonable. Years of customer records, invoices, orders and notes live in your current software, and the new system only helps if all of it arrives intact.
The good news is that moving data safely is a well-understood job. It mostly comes down to planning, checking and not rushing the switch. This guide explains what’s involved, what tends to go wrong, and when it makes sense to bring in help.
What is a data migration?
A data migration is moving your information from one system to another. For example, from an old accounting package to a new one, from one online store platform to another, or from a collection of spreadsheets into a proper customer system.
It sounds like copying files, but it’s closer to translating. The two systems almost never store information the same way. One keeps a customer’s name in a single box, the other splits it into first and last name. One stores addresses as one line, the other in five fields. One has a “notes” field, the other doesn’t. Every one of those differences needs a decision about where things go.
What usually goes wrong when businesses switch systems?
The same few problems come up again and again:
- Duplicates. The same customer appears three times under slightly different names, and all three come across.
- Missing history. Current records move, but past orders, old invoices or attachments are left behind, and nobody notices until someone needs them.
- Broken links. Invoices arrive but are no longer attached to the right customer, or orders lose their products.
- Fields that don’t fit. Information with no obvious home in the new system gets dropped, or squashed into a notes field.
- Dates, currencies and formats. A date written day-first becomes month-first, and 3 April turns into 4 March.
- A rushed switch. The old system is switched off before anyone has checked the new one properly.
Most of these are invisible on day one. They show up weeks later, when someone goes looking for a record that isn’t there.
How do you check the data is right after the move?
Checking is the most important part of a migration, and the part most often skipped. A careful check includes:
- Counting. The number of customers, invoices, orders and products should match between the old system and the new one, or differ only for reasons you’ve agreed, such as removed duplicates.
- Totals. Add up money figures, such as outstanding balances and last year’s sales, on both sides. If they match, a great deal else is probably right.
- Spot checks. Pick a sample of real records, including old, unusual and complicated ones, and compare them field by field.
- Your team’s own test. The people who use the system every day know what “looks wrong” far better than any checklist. Give them time to try their normal tasks in the new system before you switch.
We usually do a full practice run first, moving everything into a test copy of the new system, checking it, fixing the problems, and repeating until it comes out clean. Only then do we do it for real.
Can you keep the business running during the switch?
Usually, yes. The common approach is:
- Plan the move around your quiet times. A weekend or the slowest day of the week, not the end of the month or your busiest season.
- Move the bulk early. Old records that no longer change can be moved and checked ahead of time.
- Move the recent changes last. On the day, only the records that changed since the practice run need to come across, which keeps the switch short.
- Keep the old system available to look things up. For a few weeks, with no new work entered into it, so nobody is stuck if they need to check something.
- Agree on a way back. If something serious turns up, you should be able to keep working in the old system while it’s fixed.
To be honest about the limits: there’s often a short window, sometimes a few hours, when neither system should be edited. A good plan makes that window small and puts it at a time that suits you. It doesn’t usually remove it entirely.
When should you bring in help instead of doing it yourself?
A small, simple move can be done in-house. If you’re moving a few hundred contacts from one list to another, the import tool built into the new software is often enough.
It’s worth getting help when:
- The data includes money: invoices, payments, balances or accounting history
- Records are linked to each other, such as customers to orders to products
- You have several years of history that needs to stay usable
- The old system is being switched off, so there’s no going back to it later
- Other systems are connected to the old one and will need connecting to the new one too
That last point is often missed. If your store, your accounting and your email all talk to the old system, the migration includes reconnecting them. That’s integration work, and it’s best planned alongside the move.
What gets done, and what does it cost?
With Agapi, a migration usually runs like this:
- A free 30-minute call in plain English, with no obligation. You tell us what you’re moving from, what you’re moving to, and what worries you.
- A look at your data to find the duplicates, gaps and awkward fields before they become problems.
- A written plan covering what moves where, how it will be checked, and when the switch happens.
- Practice runs, checking and fixing, then the real move at a time that suits you, with the old system kept available to look things up.
The cost depends on how much data there is, how messy it is, and how many other systems need reconnecting, so we scope it first. The price is agreed in writing before any work starts. The work is done by Agapi’s own senior engineers, and you have one consistent point of contact from the first call to the day after the switch.
The short version
Treat a migration as translation, not copying. Clean up first, practise the move, check counts, totals and real records, and switch at a quiet time with a way back. If money, history or connected systems are involved, get help.
If you’re planning a switch, book a free 30-minute call, or read more about what we do.