Think about the car you drove ten years ago.
It probably ran fine. But parts got harder to find. The repairs got more expensive. The technology inside it fell further behind every year. One day, you needed to drive to work and the car didn't start.
That's not a car problem. That's a timing problem. And it's exactly what's happening right now to thousands of retailers and mid-market businesses still running on-premise ERP systems like Microsoft Dynamics NAV or Great Plains.
The cloud transition conversation isn't theoretical anymore. For companies on aging on-premise systems, it's a question of when, not if.
Microsoft has been deliberate and public about its direction in the Dynamics ecosystem. Dynamics NAV has reached the end of its mainstream support lifecycle. Dynamics GP is on a similar trajectory, with Microsoft signaling that its long-term investment is squarely in Business Central, not in legacy on-premise products.
That matters for a few concrete reasons.
Security patches become less frequent. New features stop arriving. The vendor ecosystem around these products gradually shrinks as ISVs and consultants focus their development resources on Business Central. And the companies still running NAV or GP find themselves maintaining increasingly customized, increasingly fragile environments with fewer people who know how to work inside them.
This is not a slow-moving problem. It compounds. Every year on a legacy system is a year of deferred modernization, and the gap between what your ERP can do and what the market expects keeps widening.
Businesses that completed a NAV to Business Central migration or a Great Plains conversion two years ago are already operating on a platform that receives automatic biannual updates from Microsoft. Their teams are using Copilot-assisted workflows. Their data lives in the cloud, accessible from anywhere, backed by enterprise-grade security infrastructure they don't have to maintain themselves.
The companies still on NAV or GP are paying more to stand still.
Most companies that delay ERP modernization don't make an active choice to stay. They make a series of passive ones. The upgrade feels disruptive. The timing never seems right. The team is stretched. There's always a reason to revisit next quarter.
But on-premise ERP systems don't age gracefully. They accumulate risk in three ways that are worth understanding clearly.
Support risk. When Microsoft reduces support for a product, it means fewer security updates, slower response to vulnerabilities, and diminishing access to certified help when something breaks. For a $50M retailer whose entire operation runs through their ERP, this is not a minor inconvenience.
Integration risk. Legacy systems were not designed to connect with modern commerce tools. Shopify, Magento, WooCommerce, and the broader ecosystem of retail technology has moved on. Maintaining those connections to an aging ERP requires custom middleware, ongoing developer work, and a tolerance for things breaking at the wrong moment. We wrote about this specifically in the context of NAV and Shopify integrations because the pattern is so common and so costly.
Opportunity risk. This one is harder to quantify but arguably the most important. AI capabilities, business process optimization tools, Copilot integrations, Power Platform automation: none of this is available to teams running on an on-premise NAV or GP environment. You can't bolt modern AI onto legacy infrastructure. The data model doesn't support it. The architecture wasn't designed for it.
Companies on Business Central are already using AI to accelerate their financial close, automate purchase order suggestions, and flag inventory anomalies before they become problems. Companies on NAV and GP are watching that capability gap grow.
The word "migration" sounds disruptive. And it can be, if it's handled poorly. But the disruption of a well-planned cloud transition is finite. The disruption of staying on a legacy system is ongoing.
For companies moving from NAV to Business Central, there are two primary paths: a technical upgrade that carries forward existing data and customizations, or a reimplementation that starts with a clean configuration aligned to current business processes. The right answer depends on the age of the existing system, the complexity of customizations, and the degree to which business processes have changed since NAV was first implemented.
For companies on Great Plains, the path is a GP-to-Business Central conversion, which involves migrating financial data and history, rethinking integrations, and configuring Microsoft Business Central to match current operational needs. Because GP and Business Central have different data architectures, this is typically treated as a reimplementation rather than a technical upgrade.
In both cases, the outcome is the same: a cloud-native ERP with built-in AI capabilities, modern integration architecture, automatic updates, and a vendor that is actively investing in the platform.
That's the other thing worth saying clearly. Microsoft is not splitting its attention between Business Central and legacy products. The investment is going one direction. If your operation depends on the Microsoft ecosystem, your long-term position is on Business Central.
The tactical benefits of Microsoft Business Central are well-documented. Lower total cost of ownership. Real-time inventory visibility. Stronger reporting. Native integration with Microsoft 365, Power BI, and Teams.
But the more important shift is operational.
When your ERP is updated twice a year by Microsoft, automatically, your team stops managing infrastructure and starts using the platform. When your financial data lives in the cloud with proper access controls, your team can work from anywhere without VPN gymnastics. When your ERP natively connects to Shopify, Magento, or WooCommerce, your integration maintenance burden drops significantly.
And when AI capabilities are embedded directly into your business process optimization workflows, decisions that used to take hours start taking minutes.
This is not a pitch for technology's own sake. It's an operational argument. Companies running fragmented, aging on-premise environments are carrying hidden costs in manual reconciliation, delayed decisions, and integration maintenance. Those costs don't show up cleanly in a budget line, but they show up in margin.
There is no perfect time to upgrade an ERP.
There is, however, a window during which an upgrade is manageable, and a point past it where the upgrade becomes more complex, more expensive, and more urgent because something has broken or a vendor has announced end-of-life.
For companies on NAV, that window is narrowing. For companies on GP, it is narrower still.
The businesses that plan their cloud transition on their terms, with adequate runway, data validation, and a clear cutover plan, are the ones that come out the other side with minimal disruption. The businesses that wait until a forced migration are the ones that end up in a recovery posture, trying to migrate under pressure while the business keeps running.
Get your ducks in a row before the clock runs out.
If you're running NAV or Great Plains and want an honest assessment of what a cloud transition would look like for your business, we should talk.
All Your Ducks is a company that helps retailers connect POS and ecommerce applications to Microsoft Dynamics Business Central. Our mission is always to remove friction and improve cashflow for businesses.
