ERPNext v15 to v16: Should You Upgrade? (2026)

Every major ERPNext release brings the same tension. The new version has features you want, but it is also newer, less battle-tested, and your customisations and integrations were written for the old one. Upgrading a live business system is never just "click update" — it is a data, testing, and compatibility exercise.

The honest answer to "should I upgrade to v16" is: not immediately, unless you specifically need one of its new features. v15 is supported and stable; a new x.0 release always settles down over its first few point releases. I am Manoj, an ERPNext and Frappe implementation consultant at MithTech in Bengaluru, and this is how I advise clients on the v15-to-v16 decision.

Should I upgrade from ERPNext v15 to v16?

Upgrade from ERPNext v15 to v16 if you specifically need one of its new features — the MRP workflow, formula-driven financial reports, or inward subcontracting — and you can test the upgrade properly first. If v15 is running your business well, there is no urgent reason to move, because v15 is supported into 2027. The decision is about need and timing, not about being on the newest number.

The pattern I recommend to clients is simple. If a v16 feature solves a real, current problem, plan a tested upgrade. If not, stay on v15 and let v16 mature through its early point releases, then upgrade on your own schedule. Being one major version behind on a stable, supported release is a perfectly sound position for a production system.

Skimmable summary: Upgrade to v16 if you need a specific new feature and can test it first; otherwise stay on v15, which is supported into 2027. The choice is about need and timing, not chasing the newest version number.

What's new in ERPNext v16?

ERPNext v16 adds a dedicated Material Requirements Planning (MRP) workflow, formula-driven Financial Report Templates, Inward Subcontracting, a redesigned workspace, and roughly 2x faster performance. Released in early 2026 after almost two years of development, it bundles 50+ features and is positioned as the most stable and secure ERPNext release to date.

For manufacturers, the MRP and inward-subcontracting additions are the most compelling — they extend the shop-floor capabilities I cover in the ERPNext manufacturing guide. For finance teams, the Financial Report Templates are the standout. v16 also redesigned the interface — if you upgrade, read the ERPNext v16 workspace guide so your team is not lost in the new navigation.

Skimmable summary: v16 brings a dedicated MRP workflow, formula-driven financial reports, inward subcontracting, a redesigned workspace, and ~2x faster performance — 50+ features in the first major release in nearly two years.

Is ERPNext v16 stable enough for production?

ERPNext v16 is positioned as the most stable release yet, but like any major x.0 version it is still maturing through its early point releases, and some teams have reported bugs on the initial builds. For a business-critical production system, the cautious approach is to wait for a few point releases before upgrading, unless you need a v16 feature enough to justify thorough testing now.

This is not unique to ERPNext — every major software release settles over its first months as edge cases surface and get patched. The open GitHub issue tracker for a new version naturally fills with early reports. None of this makes v16 a bad release; it makes it a new one. If you upgrade early, budget for more testing and keep a tested rollback path.

Skimmable summary: v16 is a strong release but, like any x.0 version, is still settling through early point releases with some reported bugs. Risk-averse production systems should wait a few point releases; early adopters should budget extra testing and a rollback path.

How do I upgrade from ERPNext v15 to v16 safely?

You upgrade from ERPNext v15 to v16 safely by testing the entire process on a staging copy of your live site first — never on production directly. The upgrade itself runs through the Frappe bench tools, but the risk lives in your customisations, custom apps, and integrations, which must be checked against v16 before you commit.

Here is the process I follow for a client upgrade.

1. Clone production to staging. Take a full backup and restore it to a separate staging instance.
2. Upgrade the staging copy to v16 using bench, upgrading Frappe and all installed apps together.
3. Fix custom apps and customisations. Resolve any code that breaks against v16; upgrade-safe custom apps usually need little change.
4. Retest integrations and reports. Verify payment gateways, e-invoicing, custom reports, and print formats all still work.
5. Schedule a production cut-over. Once staging is clean, back up production, run the upgrade in a maintenance window, and validate before reopening.

Skimmable summary: Upgrade safely by cloning production to staging, upgrading and testing there first, fixing custom apps and integrations, then running a backed-up production cut-over in a maintenance window. Never upgrade production directly.

When should I stay on ERPNext v15?

You should stay on ERPNext v15 when it runs your business well, you do not need a specific v16 feature, and you value stability over being current. Because v15 receives support and security fixes into 2027, remaining on it is a safe, deliberate choice — not technical debt. Many well-run ERPNext deployments intentionally stay one major version behind the newest release.

Stay on v15 especially if you run heavy customisations or critical integrations, since those are exactly what a major upgrade puts at risk. Plan the move to v16 for a quieter business period, after the release has matured, with time budgeted for testing. There is no penalty for upgrading on your schedule rather than the release calendar's.

Skimmable summary: Stay on v15 if it works, you don't need a v16 feature, and you value stability — it's supported into 2027, so it's a safe choice, not technical debt. Heavily customised systems especially benefit from waiting for v16 to mature.

Frequently asked questions

Is ERPNext v16 released?

Yes. ERPNext v16 released in early 2026, following a beta in late 2025 — the first major ERPNext version in almost two years. It ships 50+ new features including a dedicated MRP workflow, formula-driven Financial Report Templates, inward subcontracting, a redesigned workspace, and roughly 2x faster performance. It is positioned as the most stable and secure ERPNext release to date.

Should I upgrade to ERPNext v16 now or wait?

Wait unless you specifically need a v16 feature. v15 is supported into 2027, so there is no forced upgrade, and any major x.0 release settles through its early point releases. If a v16 feature — MRP, financial report templates, inward subcontracting — solves a real current problem, plan a tested upgrade; otherwise let v16 mature and upgrade on your own schedule.

Will my customisations break when upgrading to v16?

They can, which is why you test on staging first. Customisations built as separate, upgrade-safe custom apps usually need little change, while customisations made by editing core files are the ones that break on a major upgrade. The safe path is to upgrade a staging copy, fix anything that breaks there, and only then cut over production.

How long does an ERPNext v15 to v16 upgrade take?

It depends far more on your customisations and integrations than on the core upgrade, which is relatively quick. A clean, lightly customised system upgrades and tests in a short window; a heavily customised, multi-integration system needs more time to verify custom apps, reports, and integrations on staging. Budget for testing time, not just the upgrade command.

Is it safe to stay on ERPNext v15?

Yes. ERPNext v15 receives support and security updates into 2027, so staying on it is a safe, deliberate choice rather than technical debt. Many production deployments intentionally remain one major version behind the newest release for stability. Plan your move to v16 when you need a feature or when the release has matured, with time set aside for testing.