Microsoft has signaled the end of Dynamics GP. For the companies that have run their finances on it for two decades, the move to Business Central is the most consequential ERP decision they will make in the next several years.
Dynamics GP has been a quietly excellent piece of software for a long time. Its end-of-life means that thousands of companies — most of them mid-market, many of them publicly accountable — are about to do something they have not done in a generation: change the system their books live in.
The move to Business Central is the right move. But it is not a software upgrade. It is a re-platforming. The chart of accounts changes shape. The financial close changes rhythm. The customizations and integrations built up over twenty years either come along, get rebuilt, or get retired. The audit trail must remain intact across the transition. None of this is unsolvable. All of it requires experience.
Shane Hall began working with Microsoft Dynamics GP in 1995 as an end-user implementing the platform inside Canada's National Science & Technology Museum (Ingenium). In 1998, he made the move from end-user to consultant, joining the Boston office of a major national Dynamics partner. He founded Axiom Business Partners in 2002 and went on to build The Closer — the close-management add-on used by hundreds of GP customers and dozens of Dynamics partners — under the Reporting-Central brand.
That history matters in a migration. It means we understand both the platform you are leaving and the one you are moving to, in real depth, from both the consultant's chair and the customer's. We have seen what works at the close. We have seen what breaks during a cutover. We know which decisions matter at the start of a migration and which are safe to leave for later.
Before a migration plan is written, we spend time understanding the current GP environment in detail — the chart of accounts, the customizations, the third-party add-ons, the reporting stack, the integrations, and the operational rhythms of the close. The output is an honest assessment of complexity, risk, and timing. Some companies are six weeks away from being ready. Some are six months.
The Business Central design takes the lessons of the readiness assessment and translates them into a target environment — chart of accounts mapped, dimensions decided, customizations triaged, integrations sequenced. The plan is concrete enough to execute against and honest enough to revise. Most migrations are won or lost in this phase.
The Business Central environment is configured to the agreed design. Master data and historical balances are converted, validated, and reconciled to the GP source of record. Customizations and integrations are rebuilt in AL, the platform's native extension language. The cutover is rehearsed before it is real. The close after go-live is the moment of truth — and the close after go-live is what we plan toward from the first conversation.
The first several closes after go-live receive the same attention as the cutover. Issues that surface get diagnosed and resolved against the design, not papered over with workarounds. By the third close most teams have settled into the new rhythm and the platform is doing what it was meant to do.
Whether the conversation results in an engagement or a referral to a partner better suited to your situation, you will leave it with a sharper sense of what your migration involves.