If your ERPNext is still on version 13, you're running software that no longer gets security fixes, and you're missing several years of improvements. Many organisations stay put because changing versions looks risky. Done properly, it doesn't have to be.
Here's how a safe move between ERPNext versions works, whether you're going up from version 13 to 15, or need to step back to an earlier version.
Why Upgrade at All
- Security. Older versions stop receiving security patches. For a system holding your finances and staff data, that's a real risk.
- Performance and usability. Newer versions are faster and easier to use, with a cleaner interface and better reporting.
- New features. Each version adds improvements across accounting, stock, manufacturing and HR.
- Support. It gets harder over time to find help, apps and integrations for an outdated version.
You Can't Jump Straight to 15
ERPNext upgrades go one major version at a time: 13 to 14, then 14 to 15. Each step runs its own data changes, and skipping one risks corrupting data. The server software underneath also has to be brought up to date for newer versions.
The Safe Way to Do It
1. Full backup first. A complete backup of the database and all attached files is taken and kept safe before anything changes.
2. Upgrade a copy, not your live system. The upgrade is rehearsed on a separate copy of your system. Your team keeps working normally while we test.
3. Check the customisations. This is where most upgrades go wrong. Custom fields, scripts, reports, print formats and custom apps written for version 13 may need changes for version 15. Each one is tested and fixed on the copy.
4. Verify with your team. Key users check the upgraded copy against the live system: account balances, stock levels, open invoices, payroll and their everyday tasks.
5. Plan the cut-over. Once everything checks out, the live upgrade is scheduled for a quiet window, usually outside working hours, with a rollback plan ready if anything unexpected happens.
6. Follow up. After the upgrade, we stay close while your team gets used to the changes.
What About Downgrading?
Sometimes an organisation needs to go back to an earlier version, for example when a custom app or integration it depends on doesn't yet support the new one. ERPNext has no "downgrade" button: each upgrade changes the database in ways that can't simply be reversed. A safe downgrade takes one of two routes:
- Restore the pre-upgrade backup on the earlier version, then re-enter or re-import anything recorded since the upgrade
- Move the data into a fresh system on the earlier version, carefully mapping records that changed shape between versions
Either way, the same rules apply as for an upgrade: a full backup first, a rehearsal on a copy, and checks with your team before the switch. It's also why we keep the pre-upgrade backup until you've signed off.
Moving Provider at the Same Time
An upgrade is a good moment to rethink hosting. If your system is run by a provider you're unhappy with, the move and the upgrade can happen together. We recently took over three live ERPNext systems from a previous vendor and upgraded all three from version 13 to version 15 in a single project. See the project
Signs It's Time
- Your ERPNext is on version 13 or older
- Nobody is sure who maintains your customisations
- Updates are avoided because "something might break"
- Your provider is slow to respond, or has stopped responding
Ultrasoft upgrades, downgrades and takes over ERPNext systems, with a free assessment first. Book a discovery call and we'll tell you exactly what your move involves.