Create your own extra migration tasks that do all the delta change that the initial migration did not cover. Keep editing and running these extra tasks until you get rid of the delta.
This is the most time-consuming part of the migration. You need to go through the page and component templates you found in your earlier estimation. If the initial migration tasks manage to migrate much of your configuration and content then you have less work to do here. Note that if substantial areas of configuration fail to transform, you may have to create extra migration tasks.
Add extra tasks to your version handler
The migration report contains information about changes you still must be done in configuration and content. Create extra update tasks for these changes in your version handler.
Example: Creating new areas
The migration report says you need to create two new areas.
The migration tool may generate code that you can use in your update task. You can find such code in the report. Here is an example what the tool suggests you add to your update task to create the new areas.
Read the code generated by the tool and see if it makes sense. Integrate it into your own update tasks. Based on the code above, your update task could look like this.
Working on the delta
The delta is the remaining changes that the module did not do automatically. Do multiple iterations running and editing the tasks in the version handler until the delta is also covered. This is the most important part of the migration effort. Expect to spend most of your time here.
Iterate through every page on the site. One iteration covers one page:
- Open the page
- Identify what is broken.
- If something needs to be changed in the template script, change the template script.
- If something needs to be changed in the configuration, update the configuration manually (.pdf) and check the result. Add a task that reflects this change in the version handler.
- If something needs to be changed in the content, change the content manually and check the results. Add a task that reflects this change in the version handler.
- If something needs to be changed in the Java code, update the Java code.
- Proceed to the next page. Keep iterating until you have gone through all the pages on the website.
If you have an STK-based theme, you need to migrate it. See How to migrate your STK theme.
- Your extra migration tasks are done. They contain all the changes in the delta which the initial tasks did not complete.
- Changes to template scripts and Java code are stored directly in your project.
- Migrating template scripts explains what changed in template scripts.
- Template Migration Reference (.pdf) summarizes the most important configuration and template script changes.
- Pages reference lists configuration properties you can use in a page template definition
- Areas reference lists configuration properties you can use in an area definition
- Components reference lists configuration properties you can use in an area definition