Best practice for migrating Confluence 3.4.8 to 5.X

Dirk Brutscher

Hi,

I'm currently evaluating the process of migrating our productive instance of Confluence 3.4.8 to a current 5.X version.

Is there a kind of "best practice" for migrating our content to the new version of Confluence?

Whats about attachments and ContentProperties written to pages by used plugins?

Dirk Brutscher

I figured out something like this...

1. Provide a clone of the production environment for migration issues (with the current data).
   
   
2. Check licence to be able to upgrade.
   
   
3. Upgrade 3.4.8 -> 4.3.7.
   
   
4. Identify unmigrated / masked content by enabling logging for "com.atlassian.confluence.content.render.xhtml.migration".
   
   
5. Restart ./admin/unmigratedwikicontent.action (only available in Confluence 4.x) to see which macros have migration issues.
   (c.f. https://confluence.atlassian.com/x/N4s4Dw)
   
   
6. Fix all problems by removing macros or upgrading. Error example: com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'sql' is unknown.
   
   
7. Redo 5. until no errors will be logged.
   
8. Upgrade to 5.x ...