Mainstream support is gone
NAV 2018 was the final NAV release. GP modern lifecycle ends 2028; extended support fees climbing every year. Every quarter on legacy is risk added to your books.
The Microsoft Dynamics NAV and GP migration specialists. Move from NAV 2009 / 2013 / 2016 / 2018 or GP 2013 - 2018 to Dynamics 365 Business Central — with your customizations, your reports, your year-end history, and your team intact.
NAV 2018 was the final NAV release. GP modern lifecycle ends 2028; extended support fees climbing every year. Every quarter on legacy is risk added to your books.
Every new feature — Copilot, Power Platform, embedded AI, modern reporting — ships to BC. NAV and GP get security patches, not features. Your competitors are getting the new tools.
Every year on NAV / GP is another year of customizations, another data layer to bring forward, another integration to map. The migration you book now is materially smaller than the same one in 2027.
Cloud migration tool from NAV 2017+. Re-implementation pattern for NAV 2016 and older. Your C/AL customizations are translated to AL extensions — properly, not as bolt-on patches.
GP’s data model is a different animal. We map your chart of accounts, distribution / manufacturing / project modules, and 10+ years of history into BC’s structure — without losing the audit trail.
The most common reason people stay on NAV or GP too long is the fear that upgrading means losing everything they’ve built. Here’s what comes across.
Customers, vendors, items, COA, dimensions — all migrated with relationships intact.
Open and closed transactions, year-end balances, audit trail — queryable from day one.
C/AL or Dexterity code reviewed line-by-line. Translated to AL extensions or retired if BC ships it natively.
SSRS / Jet / Management Reporter rebuilt in Power BI. EDI, bank feeds, payroll — reconnected.
Audit of your NAV / GP install. Customizations catalogued, integrations mapped, modules in scope. You get a written assessment — free.
Fixed-scope, fixed-fee migration plan. Cloud migration tool vs re-implementation decision per module. Cutover date locked.
Parallel-run sandbox. Customizations rebuilt as AL extensions. Reports in Power BI. UAT with your team, not just ours.
Final data sync over the weekend. Monday morning your team logs into BC. Hypercare for 30 days post-cutover.
Tell us your NAV or GP version, your headcount, and what’s holding you back. We’ll come back with a written assessment: cloud migration vs re-implementation, customizations to keep / rewrite / retire, timeline, and a fixed-fee number you can take to your CFO.
hello@upgradetobc.comNo commitment. No sales pressure. Assessment is yours either way.