Dynamics GP to Business Central
From a read-only login to a running Business Central tenant.
The whole engagement is organised around one thing: a complete, evidenced inventory of what your GP system does. Everything else is derived from it.
- 1
Week 0: access
You provision a read-only SQL login covering the DYNAMICS system database and the company databases you authorise. If you would rather we never connect to production, restore a copy and point us at that. Share what else you have: Management Reporter or FRx definitions, VBA and modified-form exports, and add-in source code as a zip upload, a Git repository or a file share. If you do not have something, we work from what the database says.
Your involvement: Your IT contact, about an hour.
- 2
Days 1–2: inventory
Connectors read the schema, custom tables, stored procedures, views, triggers and functions, SQL Agent jobs, Integration Manager definitions, ISV tables and SmartLists, and transaction history shows which modules are in active use. The files you share add reports, VBA, modified forms and add-in code. Each object becomes a fact with its evidence attached, repeat reads never create duplicates, and anything that cannot be attributed is listed rather than dropped.
Your involvement: Nobody from your side.
- 3
Days 2–4: classification
The AI FDE Agent reads each item and proposes a disposition with reasoning: replace with native Business Central, rebuild as an extension, retire, or defer. A second model reviews every classification run, and nothing is recorded until it passes. Low-confidence items and contradictions become questions rather than guesses.
Your involvement: A supervising engineer reviews the low-confidence set and approves every question before you see it.
- 4
Week 1–2: interview
You get a short portal interview, by chat or form. Each question says why it is being asked and which decision it unblocks, so it can be answered by whoever knows, at their own pace. Answers become facts and can flip a classification.
Your involvement: Finance and IT leads, typically two to three hours in total.
- 5
Week 2: report and proposal
The Assessment Report and Migration Proposal are generated from templates over the inventory. Every count and price links to the facts behind it, and the proposal lists the assumptions it relies on. Pricing is per item and itemised, so you can argue with a line instead of a total.
Your involvement: You review and approve the scope.
- 6
Then: migration
Signed scope becomes a wave plan. Extensions are rebuilt in AL, native configuration is applied, and data moves through Microsoft's cloud migration in stages: master data, open items, history. Every load is reconciled against GP (trial balance, open receivables and payables, inventory, record counts), and a load that does not reconcile stops there. Reconciliation results are visible to you in the portal.
Your involvement: Testing sessions with your users, an approval for every production step, then cutover on a date you pick. GP stays available as the rollback.
What the AI FDE Agent will not do.
It will not write to GP. The connector refuses any statement that is not a read, and it connects through a login you create as read-only.
It will not write your report. Deliverables are generated from templates over verified facts. No free-form model text reaches you.
It will not write to Business Central on its own. Write access is granted per environment and expires within the hour, and every production step needs a person to approve it.
It will not guess quietly. Anything below the confidence threshold becomes a question with its evidence attached, or an engineer's explicit decision recorded in the audit log.
See your migration cost before you commit to a partner.
Select the modules you run and the customizations built on GP to receive a preliminary figure and request a fixed quote.