Can a CMS that was created in v7 - with all the "then" available blocks, such as Nested Content > which was then painfully upgraded to v8 - keeping all the content > be upgraded to v13 - keeping all their current content?
What about upgrading to 13? Is there a fundamental change in the code?
Would the path you mention above just be as simple as then going from 12 > 13?
As a different type of question.
As the site is on 8 and a lot of the code is bespoke would you attempt to go from 8 up to 13 or would it it be technically quicker to create a brand new CMS in 13 and manually add all the content back into the site?
Every newer version of Umbraco has had fewer and fewer breaking changes ^^ Upgrading has so far been not a terrible process overall... but I also have never worked in Umbraco older than mid-v8.
During a recent upgrade I did, the hardest bit was going from 9 > 10 since the project had been using SQLCE. v10 tossed that so new DB configurations needed to be done and I'm a frontend specialist so that was a stressful place for me to poke around xD There were some bumps and secret steps to do but Umbraco support helped me through it <3
Barring that hiccup, the upgrade process from 10 thru 12 went very smoothly. Only a couple minor things to update and change out.
However, it was a very small site not using deprecated data types, and with only 3 packages to worry about. So it was about as ideal as you could hope for.
As for upgrading vs fresh start... It depends on the case really. How big is it; how customized is it; how many deprecated things is it using; do you already have any automated tooling for migration, etc etc.
If there is a lot of code and customization that wouldn't carry through an upgrade, they would also have to be re-written if you started fresh anyways -- so not a lot of difference there.
Probably the biggest consideration would be around technical debt. A clean slate is easier to try new and better approaches, but that's not impossible to do during an upgrade either.
CMS upgrade question 7 > 8 > 13
Hi,
Can a CMS that was created in v7 - with all the "then" available blocks, such as Nested Content > which was then painfully upgraded to v8 - keeping all the content > be upgraded to v13 - keeping all their current content?
Thanks
Jon
Hi Jonathan,
You have to upgrade from v8 latest to v9 latest, then from v9 to v10-v11
Here are more details - https://docs.umbraco.com/umbraco-cms/fundamentals/setup/upgrading/version-specific
From 10 you can upgrade to v11 and make some changes, but it should be easier than from v8 to v9
Thanks,
Alex
Hi
What about upgrading to 13? Is there a fundamental change in the code?
Would the path you mention above just be as simple as then going from 12 > 13?
As a different type of question.
As the site is on 8 and a lot of the code is bespoke would you attempt to go from 8 up to 13 or would it it be technically quicker to create a brand new CMS in 13 and manually add all the content back into the site?
Every newer version of Umbraco has had fewer and fewer breaking changes ^^ Upgrading has so far been not a terrible process overall... but I also have never worked in Umbraco older than mid-v8.
During a recent upgrade I did, the hardest bit was going from 9 > 10 since the project had been using SQLCE. v10 tossed that so new DB configurations needed to be done and I'm a frontend specialist so that was a stressful place for me to poke around xD There were some bumps and secret steps to do but Umbraco support helped me through it <3
Barring that hiccup, the upgrade process from 10 thru 12 went very smoothly. Only a couple minor things to update and change out.
However, it was a very small site not using deprecated data types, and with only 3 packages to worry about. So it was about as ideal as you could hope for.
As for upgrading vs fresh start... It depends on the case really. How big is it; how customized is it; how many deprecated things is it using; do you already have any automated tooling for migration, etc etc.
If there is a lot of code and customization that wouldn't carry through an upgrade, they would also have to be re-written if you started fresh anyways -- so not a lot of difference there.
Probably the biggest consideration would be around technical debt. A clean slate is easier to try new and better approaches, but that's not impossible to do during an upgrade either.
is working on a reply...