A migration plan starts with what you run.
01
Processes and integrations
Document how finance and operations work today, including the systems exchanging information with GP.
02
Data and customisations
Decide which records, history and custom processes need to be carried forward, archived or redesigned.
03
Cutover and continuity
Plan migration, reconciliation, user validation and the decision to go live. Agree the rollback approach and support ownership.
04
People and adoption
Prepare the team for new workflows, reporting and responsibilities before the system becomes part of everyday work.
Six months of planning. A weekend to switch.
01
Use the support date as a planning input
Microsoft’s current lifecycle guidance says Dynamics GP product enhancements, regulatory updates and technical support end on 31 December 2029, with security updates or patches, if needed, available until 30 April 2031. That guidance concerns the product under Modern Lifecycle. Older Fixed Lifecycle versions have their own support dates, so begin with the exact installation.
The migration decision also needs the current business requirements. Identify reporting workarounds, integrations, customisations and operating constraints that affect the target design. A deadline explains urgency; it does not determine how accounts, historical information or business processes should be represented in Business Central.
02
Separate data migration from the reporting and process transition
Microsoft documents migration of supported GP data to Business Central online, with preparation, replication and validation. That technical path does not make every report, interface or custom process equivalent in the new application. Treat those dependencies as named decisions.
Finance should identify the reports and reconciliations it relies on, including Management Reporter packs, spreadsheets and bespoke SQL reporting. Decide which outputs can be met through Business Central and which need an additional reporting approach. Braintree’s published GP route also discusses FYIsoft; any selected reporting product needs its own fit, licensing and delivery scope.
03
Prepare a transition the finance team can accept
Bring the GP version, company structure, chart of accounts, customisations, data volumes and integration owners. Include open transactions and the periods of history needed for operations and analysis. Customer finance owners should approve mapping and reconciliation rules before the final conversion.
The plan should explain what remains operative during preparation, how testing is separated from live trading and who authorises the transition. Microsoft’s migration guidance warns that replication can overwrite target data, making environment planning material to the decision. Promotion eligibility, dual-use rights and any parallel-operation costs require commercial confirmation for the actual customer; they should not be assumed from a headline discount.
04
GP transition decisions to record
Requirement
What to examine
Decision to make
Source and support
Exact version, lifecycle position and third-party components.
The supported route and required preparation.
Financial continuity
Accounts, dimensions, open transactions and key reports.
The mapping and reconciliation that finance will accept.
Historical information
Required periods, detail and retrieval needs.
What migrates and how remaining information stays usable.
EVIDENCE & DOCUMENTATION
See the work in context.
BEFORE YOU DECIDE




