Moving off Dynamics GP, NAV or AX with the ledger proven correct before anyone relies on it.
Illustrative. This is a walkthrough of how we run this kind of engagement, not an account of a specific client project. It carries no client and no results, because none are being claimed. Delivered work, with measured outcomes, is on the work pages.
A finance team on a version that is out of mainstream support, with years of history, customisations nobody documented and an auditor asking questions.
We inventory the customisations and work out which are load-bearing, which are habits and which can go. Most estates carry more than they need, and this is the cheapest week to find that out.
What you get
The new environment is configured and the migration pipelines are built as repeatable jobs, not one-off scripts, because you will run them more than once.
What you get
Successive migration runs until the balances tie out, then a parallel period where both systems run and the numbers are compared.
What you get
Cutover and then the first close on the new ledger, with us present. The old system stays available read-only for as long as your auditors need.
What you get
If we cannot find an owner or a reason, it is a candidate for removal, and that is put to the sponsor as a decision with a cost either way. Carrying it forward blind is the expensive option.
This is normal on the first two runs and it is why the runs are scheduled early. The reconciliation report shows exactly which accounts differ and by how much, so it is an investigation rather than a mystery.
We plan the cutover around the audit calendar rather than the project plan. A go-live during fieldwork is a bad trade whichever way the project is running.
Other shapes
