The things people actually want to know

It depends on how many systems are involved and what condition the data is in — so we scope it in two stages rather than guessing. First a fixed-price discovery, which tells us both exactly what the job is. Then a fixed price for the migration itself, based on what discovery found. You are never asked to sign up to an open-ended hourly rate on an unknown dataset.

A single-system accounting move is usually measured in weeks; a multi-system cloud migration in months. The variable is almost never the transfer itself — it is how long it takes to agree what the data should look like on the other side, and how much cleaning up you decide to do on the way. Discovery gives you a firm timeline before you commit.

Because a fixed price on an unknown dataset is either padded or wrong. Discovery is a small, bounded piece of work that removes the unknowns. If you would rather not proceed afterwards, you still own the output — the inventory and the data profile are yours.

The whole method is built to prevent it. We reconcile record counts and control totals at every stage, run a full trial migration before the real one, and do not sign off a cutover until the target reconciles to the source and you have agreed it does.

That is one of the first questions we ask you, because the honest answer shapes the approach. Some businesses can take a planned weekend; others cannot stop at all, and we design a phased or parallel-run cutover instead.

Every cutover runs from a rehearsed runbook with a tested rollback point. Before we start we confirm you can go back — not that a backup exists, but that a restore has actually been performed.

Rarely. Most migrations are planned around your quiet period, and for continuous operations we run the old and new systems in parallel until you are confident.

Usually far more than you have been told. Platform limits are real, but “you can only bring opening balances” is often a limitation of the tool someone else was using, not of the platform. It is worth asking before you accept it.

That is the normal state of affairs and it is not a reason to delay. A migration is the best opportunity you will ever get to clean up — we profile what you have, show you the duplicates and gaps, and you decide what is worth fixing.

Very often, yes. They know your environment and we know migration. We are happy to work alongside them, or to take the whole thing off their plate.

We give you a decommission plan — what to archive, what you are obliged to retain and for how long, and when it is safe to switch the old system off. Businesses routinely pay for legacy licences years longer than they need to.