Major version upgrades of ERPNext and its companion apps, with the breaking changes and app splits each step documents.
Getting off end-of-life ERPNext v14: installing the apps split out in v15 (Lending, Payments, E-commerce), replacing WooCommerce, moving to Serial and Batch Bundles, fixing print formats and reports, and a staged bench migrate with rollback.
Planning a multi-step upgrade from ERPNext v13 or earlier: one major version at a time, installing Frappe HR and other apps split out in v14, migrating Indian GST setups to India Compliance, retesting customizations at each hop and data checks between steps.
What the January 31, 2026 end of life for ERPNext and Frappe version 14 means for self-hosted sites, the choice between landing on version 15 or going to 16, and the support windows of each.
Making custom Frappe apps work on version 16: Python 3.14 and Node 24, the /desk route, workspace sidebar, has_permission hooks returning True, no commits from document hooks and removed whitelisted methods.
Keeping a version 15 or 16 site current with frequent minor releases: what bench update does, excluding apps, backups before patching and a test site before production.
Upgrading containerized ERPNext: rebuilding images with new app versions, why containers are not patched in place, running bench migrate or the migrator service, and cache invalidation in CI builds.
Rolling a new ERPNext version through the frappe/helm chart: bumping the image, running the migrate job per site, clearing cache and handling multiple sites on one release.
Keeping apps that split from ERPNext in step during a major upgrade: Frappe HR, Lending, Payments, India Compliance and Ecommerce Integrations, matching branches and installing them before migrating.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.