Create a small website that is a representative sample of all your templates.
Creating a migration website
We recommend creating a small migration website where you have only one page for each page template and one component for each component template. That is, assign each template only once. This makes it easier to test the integrity of the migration rather than test on a large quantity of live content. Work on Magnolia version 4.4.6 or higher up to 4.4.9.
Exporting the website into HTML
Export the small migration website into static HTML. This gives you a baseline to compare with. After the migration you do another export and compare it to the baseline. This way you can see diffirences in HTML output, layout, look & feel etc.
The outputs will not be an exact match. This is OK. Several things changed in STK 2.0. For example, the video player is not HTML5 compliant and it won't look exactly like the earlier player. Such differences are to be expected and they don't mean that your migration was not successful. Look out for errors and significant differences.
Estimating the effort
Analyze the Migration Website and group the templates per difficulty in order to have an estimate of the migration time and effort. For example, in your migration website you can see that you have 10 components. Three of them are complex and difficult to migrate. You think you need to spend half a day per component. The remaining seven components are easier. They take only one hour each. You can create a table to visualize the effort.
|Page or component template||Difficulty||Time estimate|
|Page 1||Easy||1 h|
|Page 2||Medium||3 h|
|Component 1||Hard||6 h|
|Component 2||Hard||6 h|
|Component 3||Easy||1 h|
As a result you should have:
- A repository that contains the small migration website content. Keep this repository in a safe place as you will perform the migration in a development environment on it.
- An estimate of the migration effort.
- An HTML export of the website.