Switching tools without losing five years of history

Ask an operator why they are still on a tool they complain about weekly and the answer is almost never a feature. It is the four hundred customers, the three years of jobs, and the quiet certainty that moving them will go wrong.

That fear is well earned. Most migrations do go wrong, and they go wrong in a specific way.

The links break, not the records

When data moves between systems, the records usually arrive intact. Customers land. Jobs land. Invoices land. What gets lost is the relationships between them — which invoice belongs to which job, which quote became which booking, which deposit was for what.

The result looks fine at a glance and is useless in practice: a list of invoices attached to nothing, a revenue figure that reads zero because none of the finished work is linked to the money that paid for it.

What to check before you trust a migration

Whatever tool you are moving to, look at these three things before you commit:

• Does it show you a preview? You should see exactly what will be created before anything is written.
• Are your paid jobs still paid? Not “is the invoice there” — does the system know the money arrived.
• Can you run it twice? A good import updates what is already there instead of creating a second copy of everything.

If the answer to any of those is no, the migration is a one-way door with no light on the other side.

Why this is worth the trouble

Every year you stay on the wrong tool because moving is frightening, the pile you would have to move gets bigger. The cheapest time to switch is always now, and the thing to demand is not a smooth sales process — it is a preview.