Best practice for migrating Confluence 3.4.8 to 5.X


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?

4 answers

1 accepted

0 votes
Accepted answer

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.

  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 ...

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in New to Confluence

How to use Confluence Cloud for stakeholder management

Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...

1,205 views 4 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you