Hi ! My app is currently up and running on v.13 of ERPNext and I am trying to update to ERPNext v.16. However when I try to migrate the database .sql files, it doesn’t want to update directly from the v.13 schema to the v.16 schema.
I read that I have to install each and every version between 13 and 16, migrate the data to it, then move on the following version till I reach v.16. Will that mean I will have to update my custom app for each and every version ?? because I was thinking of starting a clean new app in v.16 and update each module on its own without having to do the progressive changes version after version; as changes are too much to keep on changing and testing for each step.
Also in that case, will it be faster to use the data import tool to migrate data from v.13 to v.16 using xlsx files without having to deal with the restore and migrate series at all ??
Please help !! 
Direct migration from ERPNext v13 to v16 isn’t supported; sequential upgrades are required, and while custom apps may need minor fixes along the way, using Data Import is only suitable for limited master data,not a full safe upgrade.
Thank you for replying, one more thing what are the tables that I won’t be able to import using the data import … I mean why is it not safe what will be left behind ?? Maybe I can move it manually somehow …
No, you can just update your custom app for v16.
- Make sure your v16 is compatible with Frappe and ERPNext
version-16 code and data.
- If necessary, write some scripts to update your custom data to its new v16 schemas (assuming you had to modify them at all)
… what are the tables that I won’t be able to import using the data import … I mean why is it not safe what will be left behind ?? Maybe I can move it manually somehow …
Is it possible to use just Data Import scripts? Probably, with likely some exceptions (I suspect certain tables cannot be imported into). But it’s going to be complicated.
To understand what you’re up against, here are the Patch files for versions 14, 15, and 16:
* erpnext/erpnext/patches/v14_0 at version-14 · frappe/erpnext · GitHub
* erpnext/erpnext/patches/v15_0 at version-15 · frappe/erpnext · GitHub
* erpnext/erpnext/patches/v16_0 at version-16 · frappe/erpnext · GitHub
If you migrate data manually, you must ensure that all data alterations in applicable patches still happens during your process. (not every patch is applicable, but many are). That’s a ton of work.
Can it be done? Yes. I actually took this approach for a client once, moving them directly from Version 4 to 12. But it was a huge effort, and I definitely wouldn’t take the same approach again.
Will be much easier to just repeat the upgrade process 3 times.
2 Likes