There are a few breaking changes along the way. v7 has some gotchas for sure. I would use the list below and ensure that you do a smoke test of your site on each step. Stand the site up and check the key functionality locally.
Have you still got everything in XSLT views? I would do an offline test - go up to the latest v6 version you can. Then step something like (where x is the last minor version):
v7.15.5 <- here you want to review the use of any "legacy" data types.
The step to 8 - it's very important you go to v8.1.x FIRST. As the upgrader straight to the latest v8 fails with a known bug.
If the site is "shop front" i.e. doesn't have any members or store anything other than content see if your client will accept a content freeze. Then you can take a live copy of the DB - run through the upgrade and testing offline and then replace when you're done.
Obviously backup and backup along the way. Take careful note of the dlls to remove an any config changes. Especially if you're going to release to live after (don't just copy your test configs over the top without checking for live SMTP, API and DB settings!).
Also do an audit - check for the use of packages and custom code in the site.
No two Umbraco installs are the same. If there's heavy use of an obselete package you might be in for a ride (with a need to write some custom data import stuff).
Question related to Umbraco upgrade from V6 to v8.
HI,
I'm planning to upgrade Umbraco CMS from version 6 to version 8. Could you anyone please let me know if I can try directly upgrade my website to 8 ?
Or should I first upgrade to version 7.14 and then follow below link to upgrade to 8.
https://our.umbraco.com/documentation/Getting-Started/Setup/Upgrading/general
-thanks in Advance.
Hey Nagarjun,
Please see here is the clear documentation for upgrading to the version 8
https://our.umbraco.com/documentation/getting-started/setup/upgrading/migrating-to-v8#:~:text=Due%20to%20this%2C%20it%20will,been%20implemented%20in%20Umbraco%208.1.
FYI: Need to read the doc, because it's important to understand what are the changes in V8 and the steps need to follow for the upgrade task.
Regards Dhanesh :)
You should definitely do this in steps. Make sure you follow the steps along the way in https://our.umbraco.com/documentation/getting-started/setup/upgrading/version-specific
There are a few breaking changes along the way. v7 has some gotchas for sure. I would use the list below and ensure that you do a smoke test of your site on each step. Stand the site up and check the key functionality locally.
Have you still got everything in XSLT views? I would do an offline test - go up to the latest v6 version you can. Then step something like (where x is the last minor version):
The step to 8 - it's very important you go to v8.1.x FIRST. As the upgrader straight to the latest v8 fails with a known bug.
If the site is "shop front" i.e. doesn't have any members or store anything other than content see if your client will accept a content freeze. Then you can take a live copy of the DB - run through the upgrade and testing offline and then replace when you're done.
Obviously backup and backup along the way. Take careful note of the dlls to remove an any config changes. Especially if you're going to release to live after (don't just copy your test configs over the top without checking for live SMTP, API and DB settings!).
Also do an audit - check for the use of packages and custom code in the site.
No two Umbraco installs are the same. If there's heavy use of an obselete package you might be in for a ride (with a need to write some custom data import stuff).
Dhanesh and Steve,
Thanks for the suggestions. I'll follow these steps during upgrade. Apart from this,
Does Umbraco V8 supports Web Forms or should i use only MVC as razor view engine.
In version 6, Umbraco templates were designed using webforms. Can we retain them in V8 or should I refactor them to MVC templates.
As usual Marc has answered this before and better than I can!
https://our.umbraco.com/forum/umbraco-8/97030-umbraco-8-not-support-webforms
So - looks like you're going to have to refactor.
Steve
is working on a reply...