Esssentially Umbraco has provided a database migration script which will migrate the data format of the V7 into the V8 format... so all your content and document type design should be safe!
There is a healthcheck you can install, which will detect some of the common issues that might occur in the migration process, before you attempt it:
However if you've used a custom property editor in V7 that isn't available in V8, eg StackedContent, then then that data won't be editable, until you can identify a corresponding property type that works for V8 and can transform the data into the new property editors format if necessary.
Once you have your data migrated, and all editable with new V8 property editors, then next you turn your attention to your templates...
... depending how you wrote out property values in your templates, you may need to update these one by one to be into the new V8 syntax, eg
instead of Model.Content.GetPropertyValue<string>("someAlias") the V8 syntax would be Model.Value<string>("someAlias") - Umbraco.Field has been removed etc - but if you've used ModelsBuilder you may get lucky as the changes will be inside Modelsbuilder and not the templates.
If you have any custom code firing on ApplicationEventHandler, this will need to be rewritten to use Composition and Composers, similarly any routehijacking the signature of the RenderMvcController has slightly changed...
Easiest Way to upgrade from Umbraco 7.15 to Umbraco 8.5.4
Hi,
If I upgrade from 7.15 to umbraco 8, will I have to remake document types, templates, etc.?
What will happen to the custom design of the website? i.e.
The website also has custom changes using articulate to parse the blog titles on the home page, etc.
Is there any easy way to go about this?
Hi Bobi
It's a migration rather than an upgrade, so depending on your site it might be complex or reasonably straightforward.
There is a guide here:
https://our.umbraco.com/documentation/getting-started/setup/upgrading/migrating-to-v8
Esssentially Umbraco has provided a database migration script which will migrate the data format of the V7 into the V8 format... so all your content and document type design should be safe!
There is a healthcheck you can install, which will detect some of the common issues that might occur in the migration process, before you attempt it:
https://our.umbraco.com/packages/developer-tools/pre-migration-health-checks/
However if you've used a custom property editor in V7 that isn't available in V8, eg StackedContent, then then that data won't be editable, until you can identify a corresponding property type that works for V8 and can transform the data into the new property editors format if necessary.
Once you have your data migrated, and all editable with new V8 property editors, then next you turn your attention to your templates...
... depending how you wrote out property values in your templates, you may need to update these one by one to be into the new V8 syntax, eg
instead of
Model.Content.GetPropertyValue<string>("someAlias")the V8 syntax would beModel.Value<string>("someAlias")- Umbraco.Field has been removed etc - but if you've used ModelsBuilder you may get lucky as the changes will be inside Modelsbuilder and not the templates.https://our.umbraco.com/documentation/Getting-Started/Design/Rendering-Content/
If you have any custom code firing on ApplicationEventHandler, this will need to be rewritten to use Composition and Composers, similarly any routehijacking the signature of the RenderMvcController has slightly changed...
https://our.umbraco.com/Documentation/Implementation/Composing/
The custom design of the site, your html and css will stay the same, it's just the Umbraco syntax that has changed.
There is some info here on what's new in Umbraco V8 https://our.umbraco.com/documentation/Getting-Started/New-in-V8
So difficulty level of a migration will depend entirely on your current site implementation! good luck!
regards
Marc
is working on a reply...