In ThemeBuilder the format of the skin data and backup files has changed so completely that it was not possible to make them backwards compatible. To reduce the work involved in porting the layout data to be compatible with the new skin format a layout exporter has been made available which generates a skin that replicates the original builder layout and converts much of the old menu markup to use ThemeBuilder compatible macros.
If you want to migrate a theme and retain all existing menu macros please follow these instructions and use the free Hmenu Legacy Plugin. Make sure to note the important information on that page as this is a free unsupported plugin, and is only supplied as an interim measure until your developers have migrated all menus over to the new Confluence 5 format.
You should follow all steps as described in Instructions.
Please follow the instructions for clearing ThemeBuilder data from a server before continuing.
You want to KEEP THIS THEME
Adaptavist do not recommend running multiple migrations on the same server but if you want to maintain the existing theme then be sure to check ‘Merge uploaded layout data with existing layouts' in steps 2 and 6.
To export your existing layouts as a skin-backup that can be uploaded into ThemeBuilder.
On your Confluence 5 server that has been upgraded from Confluence 4
Once the skin backup has been uploaded you may then use the Skin Editor to view the exported layout. If you are satisfied that your layouts have been migrated successfully to skins you may uninstall the exporter.
Exported layouts will consist of a 'main' panel that replicates the old Theme Builder theme structure. You should not need to edit this panel since it only exists to provide the framework for your panel content. The 'dashboard' panel will contain the contents of your dashboard.wiki resource, similarly the 'flaglogic' panel will contain the contents of the flaglogic.wiki resource.
You will notice that the storage format panels inherited from the root skin are disabled. This is intentional because they are no-longer used within an exported layout. Instead, panels have been created to match those used by the original layout, the wiki markup that they contained has been copied over, and the menu items translated into ThemeBuilder compatible macros where possible.
Out of the box, an exported layout will not be immediately usable since ThemeBuilder now uses the internal confluence menu functionality to generate the drop-down menu areas. This adds some complexity to the process of re-using an exported layout since the Atlassian menu code is not capable of generating nested menus, as such a review of the menu usage will be required. See the section on ThemeBuilder Menus for more help with this.