The ERP Solution for the Year” 2025 in Agtech Breakthrough Awards 2025
The ERP Solution for the Year” 2025 in Agtech Breakthrough Awards 2025
Dynamics NAV helped you manage the past — and support for it ends in January 2028. AgriERP is built on Microsoft Dynamics 365 Business Central, NAV's direct successor. Which means this isn't a rip-and-replace: it's the upgrade Microsoft designed, plus the crop, grower, and harvest management NAV never had.
NAV earned its reputation. Solid financials, real dimensions, native lot tracking, dependable warehousing — for two decades it ran mid-size agribusiness better than almost anything else. If your operation still runs on it, that was a good decision when you made it.
But NAV's story has an ending, and Microsoft has published the date. The final version shipped in 2018. Mainstream support is already over. Extended support for NAV 2018 ends January 11, 2028 — after that, no security patches, no tax and regulatory updates, no Microsoft support. Meanwhile your customizations live in C/AL, a language Microsoft no longer trains partners on, and every year of enhancement fees buys maintenance on a product that will never gain another feature.
Here's the part that changes the math: Microsoft's designated successor to NAV is Dynamics 365 Business Central — and that's exactly what AgriERP is built on. Same lineage, same core business logic, same posting groups and dimensions you already know. You're not leaving the Microsoft ecosystem. You're completing the upgrade it designed — and gaining agriculture functionality NAV never had.
These are Microsoft's official milestones. Two have already passed. The one that matters most to payroll users is December 31, 2029 — the last tax and regulatory update GP will ever receive.
On GP 2015, 2016, or 2018? Those versions face their own earlier support cliffs under Microsoft's Fixed Lifecycle Policy — your real deadline may already be here.
NAV is a real ERP, and we'll say so. The gaps aren't in what it was — they're in what it can never become: cloud-native, agriculture-specific, and continuously updated.
Capability |
 |
 |
|---|---|---|
Core Financials |
Strong, mature GL and posting-group architecture |
Full Business Central financials plus agricultural cost structures |
Dimensions |
Strong — global and shortcut dimensions |
Inherited from BC, plus ag dimensions: field, crop, season, lot |
Lot & Serial Tracking |
Native |
Native, extended to harvest lots, bins, and field-level trace |
Microsoft Support |
Ends January 11, 2028 (NAV 2018); earlier versions already unsupported |
Continuous updates under Microsoft's Modern Lifecycle Policy |
Deployment |
On-premise; remote access via VPN |
Cloud SaaS with mobile field and warehouse access |
Farm & Crop Management |
Not native — custom C/AL development only |
Native crop, field, block, and season management |
Grower Accounting |
Not native |
Grower settlements and grower portal built in |
Harvest & Yield |
Not native |
Harvest management and per-acre / per-head costing |
Analytics & AI |
RDLC-era reporting; no native Power BI or Copilot |
Power BI dashboards and Microsoft Copilot on your farm data |
Customizations |
C/AL — deprecated; upgrades break them |
AL extensions that survive every update |
Food-Safety Traceability |
Lot data exists, but no modern trace reporting workflows |
FSMA-ready lot traceability with rapid recall reporting |
Upgrade Model |
Each major upgrade is a re-implementation project |
Automatic, non-breaking cloud updates |
NAV capabilities vary by version and customization. We'll assess your specific environment — objects, add-ons, and integrations — during discovery.
The same assistant, applied to four places a fast answer helps: the field, the inputs, the back office, and the season ahead.
Most ERP migrations mean abandoning everything your team knows. This one doesn't. Business Central is NAV's direct successor — the same Navision lineage, the same core business logic. AgriERP builds on that foundation.
A NAV-to-Business-Central migration is the path Microsoft built tooling for. AgriERP just makes sure you land on a platform that speaks agriculture when you arrive.
Every ag capability your NAV system has today was custom-built — grower settlements coded by a consultant, harvest tracking bolted on, field costing living half in NAV and half in spreadsheets. That code is written in a deprecated language, and the developers who understand it are retiring faster than they're being replaced.
Keep the functionality. Retire the legacy code that delivers it.
NAV lives on a server your IT team maintains, patched by hand, reached from the field through VPN gymnastics — when it can be reached at all. Your operation doesn't work in one building anymore. Your ERP still does.
Approve a purchase from the pickup. Check inventory from the packhouse. Close the month from anywhere.
NAV's feature set froze the year it stopped shipping. Everything Microsoft has built since — native Power BI, Copilot, AI-driven forecasting — landed in Business Central, not NAV. Your reporting is stuck in the RDLC era while your competitors ask their ERP questions in plain English.
The platform keeps improving every release cycle — automatically, without breaking anything.
Staying on NAV isn't free. Enhancement fees rise every year on a product that will never gain a feature. Servers age. C/AL developers get scarcer and pricier. Auditors start asking why core systems run unsupported software — and food-safety rules like FSMA's traceability requirements demand reporting speed NAV's structures weren't designed for.
Every dollar currently maintaining the past can fund the platform that moves you forward.
API-first on Business Central, AgriERP connects with the machinery, weather, commerce, and logistics tools that legacy web services couldn't reach.
Can’t find your desired integration? Just let us know, and we’ll build one for you!
You didn't outgrow good bookkeeping. You outgrew what accounting software alone can do. Take the leap forward with AgriERP and run your entire operation from one platform.
Keep your farms and facilities audit-ready with automated documentation, real-time logs, and built-in controls for FDA, USDA, and FSMA compliance — including the traceability reporting modern food-safety rules demand.
Your NAV system holds a decade or more of customizations and clean history. We migrate it as a guided, phased process — mapped object by object, scheduled around your seasonal calendar, and never live during harvest.
Solution Discovery We inventory your NAV version, C/AL customizations, ISV add-ons, integrations, and data — then decide, object by object, what maps to Business Central, what AgriERP's ag modules replace, and what retires.
Project Planning We build an implementation plan around your goals, business cycles, and seasonal calendar — reducing disruption and keeping your team in control throughout.
ERP Implementation We configure AgriERP on Business Central, rebuild retained logic as clean AL extensions, and wire your integrations API-first.
Data Migration from NAV Master data, dimensions, open transactions, and inventory with lot and serial history migrate via Microsoft's proven NAV-to-BC tooling; a defined window of posted history comes across, with the rest archived and accessible.
Go Live & Onboarding After comprehensive UAT — balances reconciled to NAV, trace tests passed — we go live and train your team for a smooth transition.
Ongoing Support Our dedicated support team assists you around the clock under our SLA agreement — and from here, updates arrive automatically instead of as upgrade projects.
Mainstream support has ended for every NAV version. Extended support for NAV 2016 ended April 14, 2026; NAV 2017 ends January 11, 2027; and NAV 2018 — the final version — ends January 11, 2028. After that: no security patches, no regulatory updates, no Microsoft support.
Business Central is NAV's direct successor, built on the same core business logic from the Navision lineage. Posting groups, dimensions, journals, and item ledger concepts carry over — which is why migrating to AgriERP on Business Central is an upgrade path, not a rip-and-replace.
Customizations worth keeping are rebuilt as clean AL extensions, since C/AL is deprecated. Many NAV customizations — grower settlements, lot handling, harvest workflows — are replaced outright by AgriERP's native agriculture modules, so you keep the functionality without the legacy code.
Master data (customers, vendors, items, GL, dimensions), open transactions, and a defined window of posted history migrate into AgriERP. Older history can be archived and kept accessible for reporting. The exact scope is confirmed during discovery.
Core financials plus one operational area typically takes three to four months; larger multi-site implementations run six to twelve months. Milestones are scheduled around your seasonal calendar — never a go-live during harvest.
You gain more of it. AgriERP on Business Central brings native Power BI, Microsoft Copilot, Microsoft 365 and Teams integration, Azure infrastructure, and continuous updates under Microsoft's Modern Lifecycle Policy — no more re-implementation-grade upgrades.
