Macro content not rendering after Confluence Data Center 10.2.7 → Cloud migration

[Prolaborate]

Hi Team,

We migrated from Confluence Data Center 10.2.7 to Confluence Cloud. The migration completed successfully, and the Prolaborate macro content was migrated, but the data is not rendering as expected.

We verified the same scenario with Confluence Data Center 9.5.4 → Cloud, and in that case the macro content renders correctly after migration.

After migrating from 10.2.7, we checked using the following Cloud APIs through Postman:

1. https://6thforceteam.atlassian.net/wiki/rest/api/search?cql=space='OTG' and macro='prolaborate'&limit=250

2. https://6thforceteam.atlassian.net/wiki/rest/api/content/50004002?expand=body.storage

We observed that sometimes the macro content is not available even though the migration completed successfully. The macro renders only after editing and saving it again. The issue is intermittent — sometimes the macro works, and sometimes it does not.

Could you please help us understand:

• Is this a known issue with Confluence Cloud migration?

• Could this be a bug related to migration from version 10.2.7?

• Are there any additional post-migration steps or fixes required?

This issue is currently affecting our production environment, so your guidance would be greatly appreciated.

[Kris Klima _K15t_]

Hi @Prolaborate 

Migration support for 3rd party macros is on the macro's actual vendor. 

Generally speaking, vendors may take four options, depending on the complexity of their app.

• full and seamless transition
• set-up alternation requirements prior to migration
• an in-between app (migrating DC App 1 to DC App 2)
• no transition - content is transfered but you have to rebuild it manually for a Cloud solution 

As @Himanshu Tiwary suggested, contact the app/macro vendor and see if there's a smooth options.

[Himanshu Tiwary]

Hi @Prolaborate ,

This does not look like expected behavior after migration. If the Prolaborate macro only renders after edit/save, it usually means the macro data was migrated but is not being fully reprocessed/rendered in Cloud consistently.

Since the same macro works after 9.5.4 → Cloud but is intermittent after 10.2.7 → Cloud, this strongly suggests a migration or compatibility issue specific to 10.2.7, not a normal Cloud limitation.

So the practical answer is:

No, this should not be considered expected behavior.

Yes, this could be a bug or compatibility issue related to migration from 10.2.7.

There should be no manual post-migration step like editing and saving each macro to make it render.

Because this is affecting production, I recommend raising it with Atlassian support and the Prolaborate vendor with:

source version 10.2.7

working comparison from 9.5.4

affected page IDs

body.storage output for working vs non-working pages

The key point is that requiring edit/save to render indicates the migration completed, but the macro content is not being consistently initialized in Cloud.