HELP with unmigrated wiki markup

Question

We're upgrading our Confluence from 3.5x to 4.3.2.

In our Dev environment, it says:

Confluence has detected that there are 464 pages with macros that are not yet Confluence 4+ compatible."

but

Update not required 
You have not installed any new plugins since your last content upgrade. You do not need to run this upgrade unless you have been advised to by Atlassian Support staff.

Running the wiki migration task takes 7 seconds and doesn't update any pages.

If I look at page sources, all the unmigrated markup comes from plugins which ARE installed.

So how do I get all these pages to migrate? Do I have to install some other plugin so the system will actually LOOK at these pages?

AlysonA · Answer

Hi Lis, First of all, can you confirm you're experiencing issues when viewing any of the pages that Confluence reported to be using incompatible macros?. For now, I'd suggest wipping out all of your plugins by removing the content from the following directories: * The _/bundled-plugins_ folder * The _/plugin-cache_ folder * The _/plugins-osgi-cache_ folder * The _/plugins-temp_ folder * The _/bundled-plugins_language_ folder This will remove all plugins from your instance, they will be generated again once you restart Confluence. This way we can rule out any broken plugins that might have failed to migrate its content. Hope it helps.

Lis Riba · Answer

The "Manage Add-ons" page doesn't list any plugins as needing updates.

(No "Available Updates" section, only "User-installed" and "System" sections.

JohnA_xb3t2l · Answer

Hi Lis,

You may have the plugins installed but have you upgraded them to be compatible with the new version of Confluence you are running? This is the most likely cause because any content stored in incompatible plugins will be stored unmigrated in the macros you are seeing. So, please ensure that all your plugins are upto date and compatible with the version of Confluence you are running, then re-run the migration task again and it should resolve this issue for you.

All the best,
John