Get on a call with us to see how we can help you
Get a QuoteNAV 2016 is already end of life, and NAV 2018 loses every security update on January 11, 2028. Each month you wait, unsupported NAV keeps costing you in licences, risk, and manual work. Move on your terms: fixed scope, customizations preserved, near-zero downtime.
Unsupported NAV keeps billing you every year: servers, patching, manual reporting, and an enhancement plan you never stop paying. Move the sliders to size what staying really costs, and what Dynamics 365 gives back.
Bank feeds, Power BI, Outlook, e-commerce, EDI: on NAV each one meant a paid connector, a middleware licence, or a developer to keep it alive. On Dynamics 365 they are built in. That recurring integration tax drops off your annual bill.
When support ends, the risk is not a missed update. It is security you cannot patch, no one to call when finance goes down, integrations that quietly break, and a bill that climbs every year you wait. Four business risks compound the longer NAV stays in production.
Extended security updates for NAV 2018 stop on January 11, 2028. Microsoft has confirmed there will be no further extensions. This is the time remaining:
No security updates means no defence against new vulnerabilities. Auditors, insurers, and customers increasingly treat unsupported ERP as a failed control, well before anything is breached.
Microsoft support ends, partners retire their NAV practices, and the engineers who know C/AL retire with them. When finance goes down at month end, there is no escalation path left.
Banks, tax authorities, browsers, and Windows keep moving. Each change can break a NAV connector with no fix coming, and you find out when a payment file or a feed silently stops.
Enhancement premiums, emergency fixes, and rising hosting all compound. Wait until 2027 and you migrate in a scramble, with partner capacity booked and far less room to negotiate.
Every NAV release has a different runway. The earlier you start, the more options you keep on cutover dates, vendor capacity, and license pricing. Use this as the working calendar for your migration plan.
It is the question every NAV team asks first. The honest answer: your C/AL customizations are not thrown away, they are rebuilt as supported AL extensions. Fifteen years of Dynamics NAV migrations means we map every object before we touch it. Here is the split: what lifts cleanly, what we rebuild as modern AL, and what we retire.
Customers, vendors, items, chart of accounts, and dimensions. Lifted and reconciled to your live NAV totals.
Number series, posting groups, payment terms, currencies, and tax configuration carried across exactly as set.
Open and posted transactions, ledger entries, and historical balances, reconciled to the dollar before cutover.
Account schedules, analysis views, saved dimensions, plus users, permission sets, and roles mapped to Microsoft Entra ID.
Every C/AL customization is re-coded as a modern AL extension,
with the business logic preserved.
Classic RDLC and Word report layouts rebuilt as native Dynamics 365 report
objects.
.NET interop and DLL add-ins replaced with extensions or Azure Functions,
since Dynamics 365 SaaS does not run interop.
Direct SQL changes converted to tableextension objects. On-prem integrations
re-architected to Dynamics 365 APIs and webhooks.
Unused objects the discovery surfaces are left behind, not carried forward into the new environment.
Report layouts no one has run in years are retired instead of rebuilt.
Objects with no Dynamics 365 equivalent are documented and dropped.
Sandbox, test, and duplicate records stay in the archive. Add-ons with a native Dynamics 365 or AppSource equivalent are swapped.
Twelve weeks, fixed scope at the start. Here is what happens each week, from discovery to go-live and hypercare. Stages overlap by design, so the team is never offline for more than a planned window.
Stages overlap by design. Parallel-run validation finishes before go-live in week 10, so the cutover weekend is the only planned downtime.
Most NAV migration delays come from undocumented customizations, dirty data, unknown integrations, and unclear ownership. Tick what you can confirm across the four areas below to score your readiness and see exactly where the gaps are.
Tick what you can confirm today. A free Migration Assessment maps every gap before you commit.
Not a generalist that also does ERP. A Dynamics migration team that has moved heavily customized NAV builds, on fixed scope, with the customizations intact.
Real Dynamics NAV and Dynamics 365 engagements, and the numbers our clients reported after the move. Manufacturing, chemicals, and multi-channel commerce.
Annual revenue scaled after migrating to Dynamics 365. Integrated analytics gave real-time visibility, and inventory and customer experience improved across every sales channel.
Global operations and a dealer web portal running on an upgraded Dynamics NAV ERP, with far less manual work.
Manual workload cut by half and production capacity raised after the NAV ERP upgrade.
Twenty minutes with a Dynamics partner who has migrated heavily customized NAV environments. You leave with six things, written down and yours to keep, whether or not you go ahead:
Microsoft Solutions Partner. We reply within one business day.
Grouped by what teams worry about most: cost, customizations, timeline, and risk. Direct answers, no hedging.