ERPNext version migration and upgrades
Compatibility audits of your custom apps, rehearsed migrations on a copy of production, data validation and a tested rollback plan.
What this covers
- Compatibility audit of custom apps
- Rehearsed migration on a copy of production
- Data validation
- Tested rollback plan
- Odoo v13 to v19 migrations too
How an engagement runs
- 01
A first conversation
You describe what is slow, manual or fragile. I ask questions, not for a budget, and say plainly whether it is work I should do.
- 02
Scope in writing
What changes, what does not, how we will know it worked, and what I need from you: access, a copy of the site, a person who knows the process.
- 03
Build on a copy
Work happens on a staging copy of your site. You review it there before anything touches production.
- 04
Go-live with a gate
Releases and migrations follow a rehearsed plan with a tested rollback. Nothing writes to production without approval.
- 05
After go-live
Fixes, monitoring and upgrades under support and maintenance, if you want them.
Related work
Questions I get asked
- Will our custom apps break?
- The compatibility audit comes first: every custom app is checked against the target version and fixed or replaced before the migration is rehearsed.
- How much downtime should we expect?
- The migration is rehearsed on a copy of production until it is uneventful; the real run follows that rehearsed plan, with a tested rollback if anything differs.
- Can you move the hosting at the same time?
- Yes. A migration is often the moment to move to two application servers with a primary and replica database, Docker, CI/CD and Grafana alerting.
