ERPNext v16 Migration and Upgrade Services
FinByz Tech upgrades ERPNext from v15, v14 or v13 to v16 on a staging copy first. We fix your custom apps for the v16 changes and your users test. Then we take a checked backup and upgrade in a planned window, on Frappe Cloud or your own servers.
What is an ERPNext v16 migration?
An ERPNext v16 migration moves a live ERPNext site, its apps and its data to version 16 of Frappe and ERPNext.
It needs a newer server stack (Python 3.14+ and Node.js 24+) and changes to custom code. FinByz Tech does it on a staging copy first, fixes the custom apps, then upgrades the live site in a planned window.
Version 16 brings a new desk, faster screens and many fixes. It also changes how permissions, sorting, print and some APIs work, so custom code written for v15 can fail quietly after the upgrade.
Read what is new in ERPNext version 16. This page is about getting there safely.
Should you upgrade ERPNext to v16 now?
Upgrade once every app you use has a v16 release and your custom code has been checked. If a key app is not ready, wait, and keep v15 updated in the meantime.
What does version 16 need on the server?
A newer Python and Node. Plan the server change before the app upgrade.
| Component | ERPNext v16 | Note |
|---|---|---|
| Python | 3.14 or newer | Bench must be pointed to the new Python |
| Node.js | 24 or newer | Needed to build the front-end assets |
| PDF engine | Chromium | Set up with bench setup-chrome; replaces wkhtmltopdf |
| Moved-out modules | Separate apps | Energy Points, Newsletter, Blog, Backup Integrations |
| Removed | GeoIP, Transaction Log | bleach replaced by nh3 |
Source: Frappe's Migrating to version 16 guide. Check it for the full list before you plan. Checked against Frappe's guide on 19 Nov 2026.
Which v16 changes break custom apps?
Permission hooks, commits and overrides, the default sort order, queries, POST-only endpoints and print and PDF. Each one is checked and fixed on staging.
Permission hooks
A has_permission hook must now return True explicitly to allow access. Hooks that returned nothing used to pass; now they deny.
Commits and overrides
frappe.db.commit() is not allowed inside document hooks, and override_doctype classes must inherit the original class.
Default sort order
Lists and get_all / get_list now sort by creation instead of modified. Reports and scripts that relied on the old order change.
Queries and values
get_list uses the query builder, and get_value on Single doctypes returns typed values instead of strings.
POST-only endpoints
logout, upload_file and send_login_link accept only POST. Integrations calling them with GET break.
Print and PDF
PDF generation moves to Chromium instead of wkhtmltopdf. Classic print formats are deprecated and stop working in v17.
Why upgrade ERPNext with FinByz?
An in-house Frappe team working on ERPNext upgrades since 2016.
Staging first, always
Every upgrade runs on a copy of your site before your live system is touched.
Custom apps fixed, not skipped
Your own apps are checked against the v16 changes and fixed before go-live.
Silver partner on frappe.io
Listed at PMM level 4 on frappe.io. Product issues go to Frappe directly.
Accounts checked after
Our accountants compare ledgers, stock and tax reports before and after.
Already running v16 for clients
We run v16 for clients, including a drag-and-drop production planner rebuilt on it.
Every hour visible
Your own Productify access: tasks, time logs and a daily report.
How does an ERPNext v15 to v16 upgrade work, step by step?
Eight steps. Your live system is untouched until step 7.
- 1AuditCurrent version, apps, custom code, server and integrations listed. Each app's v16 readiness checked.
- 2Staging copyYour site, apps and data copied to a staging server with Python 3.14 and Node 24.
- 3Upgrade stagingOne major version at a time, with patches run and errors noted.
- 4Fix custom appsPermission hooks, commits, overrides, sorting and print formats fixed for v16.
- 5User testingYour key users test their daily work on staging and sign off.
- 6BackupA full backup of the live site, checked, right before the upgrade window.
- 7Production upgradeThe tested upgrade applied in an agreed window, usually outside office hours.
- 8Check and supportAccounts and key flows checked live, then priority support in the first days.
Can you upgrade from v13 or v14 directly to v16?
ERPNext cannot jump from v13 to v16; each major version is upgraded in turn.
From v13, the path is v13 to v14, v14 to v15, then v15 to v16. Each step is run and tested on staging. Very old, heavily customised systems sometimes do better with a fresh v16 site and a data move.
Each major version brings its own patches and code changes. Skipping steps leaves data half-migrated, which is far harder to fix than a longer plan.
If a fresh site is the better route, see migrating data into ERPNext.
Are your third-party apps ready for v16?
The upgrade is only as ready as its slowest app. We check each one before planning the date.
- HRMS and payroll on its v16 branch.
- India Compliance or your country's compliance app.
- Payment, bank and e-commerce connectors.
- Apps from the Frappe marketplace you installed.
- Your own custom apps, checked against each breaking change.
- Moved-out modules you used: Energy Points, Newsletter, Blog or Backup Integrations, now separate apps.
How much downtime, and what is the rollback plan?
An upgrade to version 16 needs a planned downtime window.
The live site is offline while the upgrade runs, usually outside office hours. The length depends on data size and apps, and we measure it on staging first, so you know it before the day.
- A checked backup of database and files right before the window.
- A go or no-go check after the upgrade, against a list agreed with you.
- A rollback path: restore the backup on your current version if a check fails.
- Priority support in the first days after the upgrade.
What changes for users after the upgrade?
Most daily work looks the same. A few things move, and users should know before the day.
- A new address. The desk moves from /app to /desk; update saved bookmarks.
- A workspace sidebar. Navigation now lives in a persistent sidebar.
- Lost workspace edits. Changes to standard workspaces are reset; back them up first.
- New PDFs. Printouts render through Chromium; check every print format.
- Different list order. Lists sort by creation date by default.
- Faster screens. See our v16 performance guide.
Frappe Cloud or your own server: what changes for the upgrade?
| Task | Frappe Cloud | Your own server |
|---|---|---|
| Python, Node and Chromium | Provided on the v16 bench | Installed and set up by FinByz |
| Staging copy | A second site or bench | A staging server or site |
| Custom apps | Fixed by FinByz | Fixed by FinByz |
| Upgrade run | Scheduled from the dashboard | Run with bench by FinByz |
| Backups | Built in, checked by FinByz | Taken and checked by FinByz |
What decides the effort of an ERPNext upgrade?
Custom code, not data size. Five things set the hours.
Custom apps
The biggest driver. Each app is checked against the v16 changes and fixed.
Version gap
v15 to v16 is one step. From v13 or v14, each major version is its own tested step.
Third-party apps
An app not yet ready for v16 can hold the upgrade until it is.
Print formats and reports
Classic formats and custom reports are checked one by one.
Users to test
Key users need time to test their daily work on staging.
How is an ERPNext upgrade billed?
On time and material, from a monthly plan of hours, with every hour visible to you. Keep upgrades routine with a maintenance plan, so the next version is a small step.
Case study: ERPNext 30x faster at SMOOR Chocolates
SMOOR Chocolates ran ERPNext v13, heavily customised by its previous partner. Saving a purchase order with 30-35 lines took about 15 minutes. After a one-month optimisation by FinByz, it takes under 30 seconds.
What do clients say about working with FinByz?
“We've had an excellent experience working with this software service provider. Their innovative approach to solving complex technical challenges has significantly improved our product. The addition of a dedicated developer to our team ensured seamless communication and consistent progress.”
“I personally think they go far and beyond in their delivery and commitments. As well as insuring that their clients are happy and well informed with there needs.”
“Great and professional software solutions, with a team very focused on client satisfaction.”
What happens after you contact us?
A consultant asks for your version, apps and hosting, and looks at the custom code. You get a readiness note: what will break, which apps are ready, and the plan. FinByz Tech has worked on 200+ projects.
Readiness Check
Apps, custom code and server reviewed against the v16 changes.
Staging Upgrade
Your site upgraded on a copy, with the issues fixed and tested.
Production Window
The live upgrade in an agreed window, with a checked backup.
Ahmedabad, India
Head office and delivery centre. FinByz Tech Pvt Ltd, 504-Addor Ambition, Nr. Navrang Circle, Navrangpura, Ahmedabad, Gujarat 380009.
Dubai, UAE
UAE office. Finbyz Tech FZE, DWTC free zone, Dubai.





