Looking for some advice and/or hearing from people who have
upgraded existing sites from 4 to 7.
Background: because we a rebuilding the website, our
implementation plan is to develop the new site using a fresh Umbraco 7 install,
and when it comes to the production deploy/upgrade, change the umbracoConfigurationStatusvalue from 7 back to the current
version 4.9.1 so that on start-up sequence the Umbraco database upgrade path is
followed. Is this suitable? i.e. we shouldn’t need to follow http://our.umbraco.org/documentation/Installation/Upgrading/v7-upgrade
because we’re not upgrading the existing website code, we’re completely
rebuilding that, so its only the backoffice that needs migrating and upgrading
at production go-live so that existing content is retained.
looking forward to hearing your recent experiences/thinking.
It's a good plan, but you need to check for all your v4 property editors have replacements and for some like MNTP or DAMP that were storing XML, these need to be converted to CSV. There is a project called Imulus Phoenix Converters to help with this.
Yeah, the upgrade wizard produced a report for me of the data types that need replacing, 15 in total.
My thinking was that during the development of the rebuild we could replace and integrate the data types appropriately, and then when I comes to go-live we could content-freeze the production environment for a period of time, upgrade the site and apply the necessary datatype changes against the migrated content, regression test and then make live.
In case you want to try Migrating you could check out CMSImport V3 beta which has a provider to import from an old Umbraco installation http://soetemansoftware.nl/news/cmsimport-v3-beta-released I love to help you with this to remove the Beta from CMSImport V3 :)
migrating/rebuilding from 4 to 7
Hello
Looking for some advice and/or hearing from people who have upgraded existing sites from 4 to 7.
Background: because we a rebuilding the website, our implementation plan is to develop the new site using a fresh Umbraco 7 install, and when it comes to the production deploy/upgrade, change the umbracoConfigurationStatus value from 7 back to the current version 4.9.1 so that on start-up sequence the Umbraco database upgrade path is followed. Is this suitable? i.e. we shouldn’t need to follow http://our.umbraco.org/documentation/Installation/Upgrading/v7-upgrade because we’re not upgrading the existing website code, we’re completely rebuilding that, so its only the backoffice that needs migrating and upgrading at production go-live so that existing content is retained.
looking forward to hearing your recent experiences/thinking.
thanks
Hi Andrew,
It's a good plan, but you need to check for all your v4 property editors have replacements and for some like MNTP or DAMP that were storing XML, these need to be converted to CSV. There is a project called Imulus Phoenix Converters to help with this.
Hope that's helpful,
Jeavon
Thanks.
Yeah, the upgrade wizard produced a report for me of the data types that need replacing, 15 in total.
My thinking was that during the development of the rebuild we could replace and integrate the data types appropriately, and then when I comes to go-live we could content-freeze the production environment for a period of time, upgrade the site and apply the necessary datatype changes against the migrated content, regression test and then make live.
Yes, that will be fine, converting the XML to CSV data should be the only real complication and the Phoenix Converters will help with that.
Hi Andrew,
In case you want to try Migrating you could check out CMSImport V3 beta which has a provider to import from an old Umbraco installation http://soetemansoftware.nl/news/cmsimport-v3-beta-released I love to help you with this to remove the Beta from CMSImport V3 :)
Best,
Richard
is working on a reply...