Consultants quoted 45 to 60 days for this migration. At Arsenal IT Consultants, we delivered it in 18 working hours.
The brief was demanding: take a client’s ERPNext platform from V13 to V16 — a four-version jump, with every schema change, deprecated app and custom build that comes with it. Roughly 20% of the system was custom code. Every line of it was migrated, along with all of the data, with nothing lost.
Why a four-version jump is hard
Anyone who has worked with ERPNext knows what a multi-version upgrade involves: schema changes between releases, apps that have been deprecated along the way, and custom code that has to survive the jump intact. Most teams move one version at a time and still hold their breath. Going from V13 straight to V16 multiplies every one of those risks.
How we did it
The difference was preparation. Because we knew exactly what needed to be done, we made sure our AI tools knew it too — prompting them with the current content and full context at each stage, so the guesswork that derails these projects never got a foothold.
Security came first
Just as importantly, none of the client’s data ever left their environment. The entire migration ran without sharing a single record externally. For us, speed and security are not a trade-off — they are both requirements.
The result
A migration that was scoped in months became a smooth transition measured in hours. All custom code preserved. All data intact. No disruption to the business relying on it.
That is what a four-version ERPNext migration looks like when the preparation, the tooling and the safeguards are all in place. If a major ERP upgrade is on your roadmap, the preparation is where it is won — and it is exactly the kind of work the team at Arsenal IT Consultants is built for.