Microsoft has set firm dates for Dynamics GP. Product enhancements, regulatory and tax updates, and technical support end on December 31, 2029. Security updates, if needed, continue only until April 30, 2031. New customers can no longer buy GP licences at all. If your finance team still runs on GP, the question is no longer whether to move, but how to move without disrupting year-end, payroll or reporting.
For most GP customers the natural destination is Dynamics 365 Business Central. It covers the same core ground (general ledger, payables, receivables, purchasing, inventory, bank reconciliation) and runs in the Microsoft cloud, so upgrades and patches become part of the subscription rather than a project every few years. This checklist is the one we work through with Canadian clients before a single record is moved.
1. Decide your timeline from the calendar backwards
Pick a go-live date first, then work backwards. Good cutover points are the start of a fiscal year or the start of a quarter, because opening balances are cleaner and comparatives are easier to report.
- Avoid going live during year-end close, audit fieldwork or a busy sales season.
- Leave at least one full month-end close in Business Central before your fiscal year-end.
- If you run GP payroll, plan the payroll change around a calendar year boundary so T4 reporting comes from one system.
2. Take an honest inventory of what GP is doing today
GP systems that have been running for a decade usually do more than anyone remembers. Before scoping, list:
- Every GP module in use, and which ones are actually used rather than just installed.
- Third-party add-ons and ISV products, and whether each has a Business Central equivalent or is no longer needed.
- Custom reports, SmartLists, Excel refreshable reports and Management Reporter statements that people rely on.
- Integrations: bank files, EDI, e-commerce, CRM, payroll, expense tools and anything that writes directly to SQL.
- Manual workarounds, the spreadsheets that exist because GP could not do something.
This list becomes the fit-gap. Many add-ons are replaced by standard Business Central features; the rest need an app from Microsoft Marketplace or a targeted extension.
3. Clean up before you move, not after
Migration is the cheapest moment to fix data. Agree with the finance team on:
- Inactive customers, vendors and items to archive rather than migrate.
- Duplicate vendors and customers to merge.
- Your chart of accounts. Moving to Business Central is a chance to simplify a segmented GP account string into main accounts plus dimensions.
- Open documents to close in GP before cutover, so fewer open items have to move.
4. Choose how much history to bring
Not every year of GP history belongs in your new ledger. A common approach is:
- Master data: customers, vendors, items, chart of accounts, bank accounts.
- Open balances: open payables and receivables, inventory on hand, and general ledger opening balances.
- Summarized history: monthly GL balances for the comparative years you need to report.
- Detailed history: kept available for lookup rather than loaded as live transactions.
Microsoft's cloud migration tooling for GP to Business Central online can move master records and open balances, and can bring a snapshot of GP history across for reference. Decide early which history auditors and managers really need, because that choice drives effort and testing time.
5. Plan for Canadian specifics
Canadian companies should confirm a few things during design rather than during testing:
- Sales tax: GST/HST and provincial sales tax such as BC PST must be set up correctly in Business Central's tax setup, including recoverable and non-recoverable portions.
- Payroll: Business Central does not include Canadian payroll as standard. If you run payroll in GP today, choose your payroll route (a payroll service or a payroll app that integrates with Business Central) as part of the project.
- Banking: confirm the payment and bank statement file formats your Canadian banks accept, including EFT and positive pay if you use them.
- Multi-currency: if you buy or sell in US dollars, set up currencies and exchange rate updates before you load open documents.
6. Rebuild reporting deliberately
Reports are where users notice a migration first. Map every Management Reporter statement and key SmartList to its Business Central replacement: financial reports, account schedules, Power BI, or Excel reports connected to Business Central. Have the controller sign off on the trial balance, income statement and balance sheet layouts before go-live, not after.
7. Test with real periods
Run at least one full trial migration and one mock month-end close.
- Reconcile the trial balance from GP to Business Central to the cent.
- Reconcile aged payables and receivables, and inventory value.
- Process a realistic sample of transactions end to end: purchase to payment, order to cash, bank reconciliation.
- Time the final data load, so you know how long the cutover weekend really is.
8. Train by role, then support the first close
People adopt a new system when it fits their daily work. Train AP, AR, purchasing and warehouse users on their own processes using your migrated data. Then plan for focused support through the first month-end close in Business Central, when most real questions appear.
9. Keep GP available, read-only
After cutover, keep GP accessible in read-only mode for lookups and audit queries for a period you agree with your auditors. Document where historical data now lives so nobody has to guess.
Where to start
If you are still on GP, the most useful first step is a short assessment: what you run today, what can be retired, and a realistic go-live window ahead of December 2029. Our Dynamics GP to Business Central migration page explains how we run these projects, and you can request a migration assessment when you are ready.