Can ERPNext with custom apps be upgraded? We did it in under an hour.
Can a customised ERPNext be upgraded? We moved a bench with six custom apps and five sites to ERPNext v16.60 the day after its release: under an hour, zero migration errors.
Kawader Technology · 18-11-2026 · 3 min read
"ERPNext with custom apps can't be upgraded." We hear it from companies comparing ERP systems, and from teams who were left with a customised system that could never be updated. We put the claim to the test.
A major ERPNext release, upgraded the next day
On 17 November 2026, Frappe released v16.60 of Frappe Framework, ERPNext and Frappe HR. It is not a small update: thousands of changed files, a rebuilt navigation, and Studio and an AI assistant now inside the framework itself.
On 18 November, the day after the release, we upgraded one of our benches to it. That bench runs five sites and six of our own custom apps on top of ERPNext, among them manufacturing, furniture, demand planning and our own user interface layer.
The ERPNext upgrade in numbers
- Under 30 minutes from stopping the servers to all five sites migrated and the servers back up on ERPNext 16.60.
- Under one hour in total, including testing, adding the Insights app and our own adjustments.
- Zero migration errors across the five sites.
- Five of the six custom apps needed no change at all.
- One app needed three small adjustments, because it sits directly on the desk navigation that Frappe redesigned.
Why a customised ERPNext upgrade breaks, and why ours did not
None of this is luck. Upgrades break when customisation is written inside the core. Ours lives in separate apps that talk to ERPNext through the hooks it provides, with every change under version control. When the core moves, the apps move with it.
What keeps ERPNext customisation safe to upgrade
- Separate apps. Every industry feature lives in an app of its own, never inside ERPNext's own files.
- Hooks, not edits. The apps connect through the extension points ERPNext provides, so a new version has nothing of ours to overwrite.
- Version control. Every change is recorded, so an adjustment after a new release is a small step that can be traced.
- A test after every upgrade. Each site is migrated and its screens are opened before anyone calls the upgrade done.
So the question is not whether a customised ERPNext can be upgraded. The question is how the customisation was built.
See how Kawader builds industry solutions on ERPNext, or book a demo and ask us about your own upgrade.