GP & NAV Migration
Microsoft is ending Dynamics GP. The clock is ticking.
The GP Timeline
Microsoft is ending Dynamics GP. The clock is ticking. New GP subscription licenses ended in April 2026. All support, service packs, and regulatory updates end December 2029. If you’re still on GP, or on an older version of NAV, migration to a new ERP isn’t optional. It’s a question of when, and how well you plan it.
Most GP-to-BC migrations take 3 to 9 months. The biggest variables: data volume, customization depth, and integration count. For food processors, the critical path includes:
Your GP database has years of transactions, chart of accounts history, vendor records, and customer data. Some of it is clean. Some of it hasn’t been touched since 2008.
Clean, validated data in Business Central. We migrate what matters, archive what doesn’t, and rebuild what’s broken. Every migrated record gets verified against source data before go-live.
Your GP has customizations. Some are documented. Some were built by a consultant who left five years ago. Some you’re not even sure exist until something breaks.
Every customization audited. We identify what BC handles natively (most of it), what needs to be rebuilt as an AL extension, and what should be retired because nobody uses it anymore. No copy-paste migrations that move your old problems into a new system.
Your processes were designed around GP’s capabilities and limitations. Some of those limitations don’t exist in BC. Some of your workarounds have become “the way we do things” even though the reason for the workaround disappeared years ago.
Processes redesigned for how BC works and how your operation should work. Not a lift-and-shift. A genuine rethink of workflows, approvals, and reporting using BC’s modern capabilities.
Your GP connects to other systems: your bank, your CRM, your e-commerce platform, third-party tools. Some integrations use APIs. Some use file drops. Some use Integration Manager jobs that run on a schedule and break silently.
Every integration mapped, tested, and rebuilt for BC. Modern API connections where possible. Proper error handling and logging so you know when something fails, not three days later when someone notices the data is wrong.
For Canadian processors running GP: The clock is ticking on two fronts. GP end-of-life, and an increasingly complex Canadian regulatory environment. Migrating now means your new BC environment is built for current CFIA, Health Canada, and SFCR requirements from day one.
NAV migrations follow a similar path. NAV and BC share more DNA (BC is NAV’s successor), so the migration is often simpler, but customizations still need to be assessed and rebuilt as extensions.
We’ve built custom migration tooling, including FRAS (Financial Reporting Automation Solution), a custom tool that bridges the gap between GP’s Management Reporter and BC’s native financial reporting. If your finance team depends on Management Reporter, we can make the transition smooth instead of painful.
Still running GP?
The migration doesn’t have to be painful. 30-minute call to review your current GP environment and talk through what a BC migration would look like for your organization.