6500 pages unmigrated content after release update - how to proceed?

Stefan Baader

We are preparing the update of our large wiki from 2.8. to 5.5

On the test system we have this hint on the unmigratedcontent.action pag:

Update content with legacy macro format:

Confluence has detected that there are 6.509 pages with macros that are not yet using the current storage format.

How to proceed now? How to find and clear all those pages? Is it recommended to continue updating with such a lot of unmigrated content?

Dave Theodore [Coyote Creek Consulting]

Oh boy. These are fun. First off, don't do anything in Prod until you can get this to work in Dev! You'll have a big mess on your hands if you don't get this figured out in Dev.

I've had the best success by upgrading to 4.0, sorting out the XHTML migration issues, and from there, go to the latest version. Unless you have a really good understanding of how the XHTML migration process works, you might want to get some help on this. Basically, the problem is that you have wiki markup on those 6500 pages that the migration tool can't migrate (and isn't nice enough to tell you exactly why.) There can be a variety of causes for this, but it generally has to do with a plugin that either isn't available on Confluence 4.0 and later or with a plugin that has some functionality that changes drastically with versions <4.0 or with User Macros that are written with wiki markup. If you can identify which plugin(s) are causing the issues, there may be a specific upgrade procedure for the plugin(s.) You'll need to rewrite User Macros, and there will be an error icon next to the ones that were not able to be upgraded. It could also be that you have broken wiki markup that was tolerated in 2.8 that is no longer tolerated in later versions. We've done a lot of these migrations over the years, so we should be able to help you get Confluence upgraded quickly if you decide you need some help with it.