Many businesses still running Dynamics NAV or GP aren’t in crisis mode.
Operations are stable. Teams know the system. It gets the job done.
But somewhere between year 3 and year 8, something shifts. Not a breaking pointโsomething quieter and more expensive: friction that compounds.
A Shopify integration that should take weeks takes months. A reporting request gets pushed because it requires custom development. A simple process changes needs external support. Your team spends more time managing integrations than running the business.
That’s usually where the real question emerges: not whether the system works today, but whether it supports what comes next.
What’s Actually Changing in ERP
Platforms like Microsoft Dynamics 365 Business Central aren’t just “newer versions” of NAV or GP.
They’re built on a fundamentally different assumption: that your ERP is a hub, not an island.
Modern ERP is expected to integrate with:
- Ecommerce platforms (Shopify, WooCommerce, custom)
- Reporting and analytics tools (Power BI, Tableau)
- Automation layers (RPA, Power Automate)
- AI and business intelligence tools
- Hundreds of third-party SaaS applications
The shift isn’t “optional features.” It’s foundational architecture.
NAV and GP were designed when integration meant custom code. Today, that custom code is becoming a liability, not a feature.
With Business Central’s native integrations to Power BI, Power Apps, and the broader Microsoft ecosystem, you’re not building bridges between systems. You’re connecting pre-built ones.
There’s also growing momentum around AI-driven workflows and Microsoft agentsโbut the important part? These capabilities are being developed for modern platforms first, then retrofitted onto older systems, if at all.
Why Companies Are Moving to Business Central
The decision rarely comes from a single problem. It’s usually the accumulated weight of small ones:
Ease of Access
- Browser-based vs. desktop-dependent
- Remote work flexibility vs. VPN + local client setup
- Faster onboarding for new users
Integration-First Architecture
- Native connectors to Shopify, Stripe, payment gateways (hours vs. weeks to implement)
- Cleaner APIs that developers actually want to use
- Third-party apps integrating with you, not the reverse
Customization That Scales
- Extension-based model (add new functionality without modifying core)
- vs. NAV/GP model (modify the system directly, then maintain those changes forever)
- Over time, this compounds: A client we worked with had 240+ custom modifications in NAV. Upgrading took 6 months.
The Real Cost Multiplier: Every integration, upgrade, and new requirement becomes increasingly expensive on NAV/GP. By year 5-7, many teams find themselves rebuilding integrations every time Microsoft releases a NAV/GP update.
A Real Example: When Staying Backfired
A mid-sized manufacturing company had been on NAV for 9 years. Operations were smooth. Finance was happy.
But they wanted to automate supplier communications and add predictive inventory forecasting.
Here’s what we found:
Integrating AI-powered workflows required significant custom development ($50K+) to bridge NAV’s API limitations. Some capabilities weren’t feasible without a major system overhaul. The timeline kept slipping, internal IT was stretched thin maintaining existing customizations.
The conversation shifted. It wasn’t “Can we do this?” anymore. It was “What’s this actually going to cost, and is it worth it?”
As we evaluated a potential move, the math became clearer:
- Staying on NAV: $50K for custom AI integration + $30K/year for ongoing maintenance + 18-month project timeline
- Moving to Business Central: $80K migration cost + 6-month timeline + $15K/year ongoing + native AI/Power Platform support included
The decision wasn’t automatic either way. But it became clear: on NAV, they were paying to maintain the system. On Business Central, they’d be paying to grow.
They chose to migrate. Now in month 4, parallel-running both systems, and the AI implementation timeline dropped to 4 months (vs. 18 on NAV).
NAV vs GP vs Business Central: The Real Comparison
| Factor | Dynamics NAV | Dynamics GP | Business Central | What This Means |
| Deployment | Primarily on-premises | Mostly on-premises | Cloud-first, browser-based | Remote teams, multiple locations, disaster recovery |
| User Access | Limited remote flexibility | Desktop-focused | Accessible anywhere, any device | Distributed workforce, field operations |
| Integration Setup | Custom development (weeks-months) | Complex, high effort | Native integrations and APIs (days-weeks) | Ecommerce, reporting, third-party tools |
| Ecommerce | Custom builds required | Limited capability | Native Shopify, modern connectors | Omnichannel sales, B2C operations |
| Customization Model | Modify core system | Custom dev heavy | Extension-based | Process changes, evolution, maintenance cost |
| Reporting | Manual effort, custom queries | Limited flexibility | Power BI integration | Data-driven decisions, self-service analytics |
| Automation & AI | Complex custom development | Limited feasibility | Built for modern workflows, Power Automate | Automation-heavy operations |
| Upgrade Cycle | Disruptive, months-long | Often delayed | Continuous, non-disruptive | Staying current, security patches |
| Scalability | Infrastructure dependent | Slower to adapt | Designed to scale | Growth, new business units |
| Maintenance Effort | Increasing over time | High dependency on partners | Structured, predictable, declining | Year 5+ of ownership |
What This Table Really Shows
It’s not “NAV bad, Business Central good.” Its effort required to achieve outcomes.
NAV and GP can do most of what Business Central does. But:
- What takes 2 weeks on Business Central might take 8 weeks on NAV
- What’s $5K on Business Central might cost $40K on NAV
- What’s built-in on Business Central might need 18 months of custom development on NAV
The Honest Truth: When You Should Stay on NAV or GP
Let’s be directโmigration isn’t always the answer.
You might be fine staying on NAV/GP if:
- Your integrations are stable. You’re not adding new tools every year. Your ecosystem is locked in and working.
- Your customization is frozen. You made your changes 5+ years ago and haven’t needed major updates since.
- Your team is specialized. You have in-house NAV/GP experts who understand the system deeply.
- Your operations don’t demand speed. Manual processes are acceptable. You’re not in a fast-moving industry.
- Your compliance is simple. Basic GL reporting, not financial services with complex regulatory requirements.
- Your budget is constrained. Migration costs $100K-$300K. You genuinely can’t afford it right now.
This is 100% valid. Not every business needs to migrate. We’ve recommended staying just as often as moving.
The Hidden Cost of Staying
This is where the numbers get real.
It’s not a single project expense. It compounds gradually:
Annual costs that add up:
- Custom development for new integrations: $20K-$80K/year
- Ongoing support and maintenance: $15K-$50K/year
- IT staff time managing customizations: $30K-$100K/year (opportunity cost)
- Delayed initiatives because “NAV can’t do that natively”
- Workarounds that become permanent processes: inefficiencies, training burden, data quality issues
Over 3-5 years, these add up dramatically.
A business we worked with spent $150K on custom integrations and support on NAV over 5 years. After Business Central implementation, that dropped to $25K/year. Payback period: 18 months.
Cost of Staying vs. Cost of Moving
What It Costs to Keep Running NAV or GP:
- Custom development for each new integration: $15K-$60K per project
- Ongoing annual support and maintenance: $20K-$60K/year
- Delayed implementation of new capabilities
- IT team overhead managing technical debt
- Risk: Each upgrade becomes more expensive
5-year total: $150K-$400K+ in direct and indirect costs
What It Costs to Migrate to Business Central:
- Implementation and migration: $80K-$300K (depends on complexity, customization debt)
- Data cleansing and verification: $10K-$40K
- Process alignment and training: $5K-$30K
- Temporary parallel operation period (2-4 weeks)
Upfront cost: $100K-$370K
However, the Long-Term Picture Changes:
- Reduced dependency on custom development
- Faster integrations (native connectors, cleaner APIs)
- Predictable, non-disruptive updates (continuous, not quarterly panics)
- Easier adoption of new technologies (Power BI, AI, automation)
- Lower annual support costs: $15K-$30K/year vs. $40K-$80K/year on NAV/GP
Payback period: Usually 18-36 months if you actively reduce custom development.
Who Should Migrate? A Clear Framework
โ Migrate if you check 2+ boxes:
- Growing ecommerce or omnichannel sales
- Adding new integrations or tools frequently
- Struggling with NAV/GP customization debt
- Planning major process changes in next 2-3 years
- High priority on automation or AI experimentation
- Multi-location or remote-heavy operations
- Natural system refresh cycle (replacing hardware, licenses expiring)
โ Pilot First if you check 1-2 boxes:
- Uncertain about integration roadmap
- Want to test migration process with low risk
- Significant customization but not sure if you need it all
- Budget is tight but future needs are clear
โ Stay if you check 2+ boxes:
- Customizations are stable and proven
- Integrations are working and rarely change
- Operations don’t demand speed
- Budget doesn’t allow $100K+ investment right now
- In-house expertise is strong and satisfied
- Compliance needs are complex (financial services, healthcare with strict data residency)
Why AI Matters (But Isn’t the Only Reason to Move)
AI is everywhere right now. And yes, it’s easier to implement on modern platforms.
The honest version:
AI-powered forecasting, customer intelligence, or automating routine tasks? These can work on NAV or GP. But you’ll build custom bridges, which costs money and time.
On Business Central, Power BI and Power Automate are built in. Microsoft agents are coming. Experimentation is cheap.
The real question isn’t “Can we do AI on NAV?” It’s “How much do we pay for each experiment?”
- Experiment on Business Central: $5K-$15K, 2-4 weeks
- Experiment on NAV: $25K-$50K, 6-10 weeks
If you’re planning to explore automation heavily, that compounds fast.
The Real Decision
The question isn’t “What does it cost to move?”
It’s “What does it cost to stay the same for the next 5 years?”
For many businesses, the answer becomes clear when you look at:
- How often you’re adding integrations
- How much custom development you’re doing annually
- How frustrating upgrades and maintenance have become
- Whether your team is growing or whether IT is stretched thin
That’s where most businesses find clarity. Not because moving is automatic, but because staying becomes visibly expensive.
A Final Thought
Dynamics NAV and GP have supported thousands of businesses for decades. They’re reliable systems built by engineers who knew operations.
But business requirements are changing faster than these platforms can adapt.
The decision isn’t about replacing what works. It’s about reducing the effort required to grow, integrate, and adapt.
Some businesses don’t need that. Some do. Which are you?
What’s Next?
If you’re evaluating whether to stay on NAV/GP or explore Business Central implementation, the best starting point isn’t a demo, it’s understanding your actual costs and priorities.
We work with ERP consulting clients across the US (including Los Angeles and surrounding areas) to evaluate exactly this scenario. We’ve helped manufacturers, distributors, and B2C companies determine whether Business Central implementation makes financial sense for their specific situation.
The question we answer: What will it cost over 5 years to stay vs. move?
We’ll help you understand whether a Business Central migration aligns with your growth timeline and budget, or confirm that staying and optimizing NAV/GP is the right move for your business.
We’re an ERP consulting firm working with companies across the United States Based out in Los Angeles. We’ve helped 40+ businesses make this exact decision. We’ve recommended staying just as often as migrating. We’ll give you the same honest assessment.
