Migrating an Umbraco project can be complex, requiring careful planning and execution. This guide provides a basic step-by-step approach to ensure a smooth migration from Umbraco 8 to Umbraco 10, and eventually to Umbraco 13.
So at Tres, we are actively migrating versions from Framework to Core. Previously we did migrations from 7 to 10 but now comes the big step from Umbraco 8 to 13.
Because Umbraco 13 sees Nested Content as legacy we also want to convert this data to the blocklist editor to be ready for 14 and higher.
While these steps offer a general framework, specific situations may require deviations. Always be prepared to adapt as needed. In the next few weeks, I will work on some specific steps for example, and provide you with some tips or steps.
All the posts regarding Migration are as is. So Always validate your work and see this as a tips blog post instead of the way to go.
In our solutions, we used to have a lot of surface controllers called by the HTML.RenderActions. This can be replaced by ViewComponents, but we had a lot of logic where we shared the same stuff. In some cases, a view component is more work than creating a service that you can inject when needed into your cshtml.
By following these basic steps and being prepared to adjust as necessary, you can effectively migrate your Umbraco project to newer versions, ensuring a smooth transition and minimizing downtime. Remember, each migration is unique, and flexibility is key to success.
In the next blog post I will explain usync migrations and tips and tricks.
And if you need some advice just contact me.