Process
How a Dynamics 365 migration runs
Four stages, each ending with something you can review and sign off. No stage starts until the previous one is agreed.
- 01
Assess
We inventory your companies, modules, customisations, integrations, reports and data volumes, and agree what “done” means.
- 02
Plan
You get a written scope, a dated plan and a price, with the risks named. Nothing is hidden in an assumptions appendix.
- 03
Migrate
Configuration, data migration rehearsals, rebuilt customisations and integrations, then user testing on your own data.
- 04
Run
Planned cutover, first month-end close alongside your team, and a handover your people can maintain.
1. Assess
Working sessions with the people who use the current system every day, plus a technical review of the database, customisations, add-ons, integrations and reports. Where a Microsoft analysis tool exists — the GP migration assessment, the AX upgrade analyzer — we run it.
You receive: an inventory of what you have, what moves, what is rebuilt and what is retired, with the open questions listed.
2. Plan
The assessment becomes a written scope, a dated plan, a test approach and a price. Risks are named with an owner and a mitigation, not buried in assumptions.
You receive: a statement of work you can hold us to, and a cutover strategy.
3. Migrate
Business Central or Finance & Operations is configured, customisations are rebuilt as extensions, and integrations are reconnected. Data migration is rehearsed on copies of production data and reconciled to your old system’s reports each time. Your team tests real scenarios on real data.
You receive: signed-off test results and a reconciled final rehearsal.
4. Run
A planned cutover with a go/no-go checklist, hands-on support through the first weeks, and your first month-end close done together. Then a handover: documentation, admin training and a list of the improvements worth doing next.
You receive: a live system, a closed first month, and a team that can run it.
Process questions
How long does a migration to Business Central take?
A single-company move from GP, NAV or SL with light customisation is typically planned in months, not years. Multi-entity, heavily customised or AX-to-Finance & Operations projects take longer. The honest answer comes out of the assessment, where we map your data, code and integrations and put dates against them.
Who will actually do the work?
The people you speak to in the assessment are the people who plan and run the migration. We do not hand your project to an unnamed offshore team after the contract is signed.
How do we start?
Fill in the contact form with your current system and version, and use the project field for the number of companies and users and any deadline you are working to. You can paste or attach an RFP if you have one. We reply with a short list of questions and a time for a call.
Next step
Tell us what you run today.
Current system and version, number of companies and users, and any deadline. We reply with the questions we need answered and a time to talk.