I've ported sites from 5.6.x to 5.7.x as well as 5.6.x to 5.8.x and found the easier transition was to 5.8. The migration tool seems to work much more smoothly when porting to a 5.8 site vice a 5.7 site (why this is, I don't know).

Either way, you'll still run into most of the same porting issues (ex. page types are now page templates with page types being something different in 5.7/5.8, loss of page areas, loss of page history, rebuilding permissions, etc), but, again, for some reason the migration tool chokes less on 5.8 porting.

The one item to check in 5.8 over 5.7 is that 5.8 has a new form handling schema (Express Forms). While 5.8 does also have the capability to handle Legacy Forms, it might just be easier to hand re-build all your forms in Express. That's what I would up doing. Its one extra step in 5.8 over 5.7, but the smoother migration is worth it.

Plus, moving directly to 5.8 saves you the trouble of having to go 5.6->5.7->5.8.

I've ported sites from 5.6.x to 5.7.x as well as 5.6.x to 5.8.x and found the easier transition was to 5.8. The migration tool seems to work much more smoothly when porting to a 5.8 site vice a 5.7 site (why this is, I don't know).

Either way, you'll still run into most of the same porting issues (ex. page types are now page templates with page types being something different in 5.7/5.8, loss of page areas, loss of page history, rebuilding permissions, etc), but, again, for some reason the migration tool chokes less on 5.8 porting.

The one item to check in 5.8 over 5.7 is that 5.8 has a new form handling schema (Express Forms). While 5.8 does also have the capability to handle Legacy Forms, it might just be easier to hand re-build all your forms in Express. That's what I would up doing. Its one extra step in 5.8 over 5.7, but the smoother migration is worth it.

Plus, moving directly to 5.8 saves you the trouble of having to go 5.6->5.7->5.8.

Thanks, I was actually referring to v8, has anyone made that type of jump?

5.8 is the same as v8, just different ways of referencing the same thing.

Wow okay, a bit embarrassed. Any good tutorials to follow?

Its a big undertaking, less of an "upgrade" and more of a "migration to a new CMS".

You'll basically have to install a clean copy of v8 (or v7) and use the migration tool to move your content from the old system to the new system. You can read about, watch a video on, and download the migration tools from the links provided here:

https://www.concrete5.org/community/forums/customizing_c5/5.6-to-5.7...

If you have any marketplace add-ons or custom code, it will have to be replaced or updated for v7/v8. A good stating place for the process on how to do this can be found here:

http://www.codeblog.ch/2014/09/concrete5-7-upgrade-packages/...

Depending on how many add-ons you have and how many pages you have, it might just be worthwhile to hand replace this content with a new package or block rather than struggle with upgrading the code and migrating the content.

I just went through this process for a thousand+ page site with custom code everywhere, so let me know if you have any questions, since any issue that might crop up I probably already hit at some point...