Upgrade 7.3.1 to 13.latest
# help-with-umbraco
d
Hi, I'm about to embark on an upgrade (/migration) of a relatively large v7.3.1 site to latest v13. The site uses doc type grid editor amongst other things, which I'd like to convert to grid. There's probably going to be a lot of wrangling along the way but I believe these are the main steps: 1. Upgrade site to latest v7 (so that 'uSync migrations packer' can be installed). Is this definitely necessary and should there be any intermediary v7 upgrade versions or should 7.3.1 - 7.15.11 work? 2. Install uSync 3. Install uSync.Migration.Packer for v7 4. Run usync/packer export? 5. Create brand new v13 project 6. Install uSync and uSync migrations on v13 project 7. Run migration and if successful do a uSync import 8. Deal with any legacy packages etc 9. Convert all template/C# stuff to new versions Is this vaguely right? Any gotchas to look out for? What about content/media?
l
Looks quite right. 🙂 If you have Forms you need to do some manual stuff. You will also have to pick and choose between pre-written migrators. There are good examples for DTGE, and a huge gotcha about an extra config file to include in your migration package. If you get stuck, I've got a fork where the migration handlers are public so it's easier to modify usync migrations behavior.
d
Great, thanks Lars 🙂
k
This has been asked many times, search and you will find valuable discussions on dos-and-don'ts. My short take: * Your steps themselves are the ones I've followed for legacy-to-13 upgrades. * Steps 8&9 will take 99% of the time and cause you 99% of the headaches, * steps 1-7 will be a smoof joyride. * To mitigate, do a minimal proof-of-concept of a v13 site without migrating anything. That will show you which packages (Umbraco and general) aren't available for net8, differences in Umbraco that need rethink, etc. * Expect 0% reusability on backend C# code and 50% on Razor. But you will be very happy after the upgrade is complete. 😎
11 Views