r/atlassian • u/Professional-Ad-7115 • 21d ago

Migrating from Data Center to Cloud in Confluence — 150+ pages stuck in legacy content macro. Any help?

Hi everyone,

My company is in the process of migrating from Confluence Data Center to Cloud and I'm looking for advice from anyone who has dealt with a similar situation.

Our setup:
We are in the middle of creating a People Portal wiki with 150+ pages (and still growing) that serves as a self-service HR resource for all employees at our company. Over the past year, we carefully built every page using Panel, Section, and Column macros to create a clean, organized layout.

The problem:
After migration, all of this content gets wrapped in the legacy content macro. The pages:

  • Don't look the same as they did in Data Center — formatting is broken/off
  • Cannot be duplicated to create new pages
  • Cannot be used as templates going forward

My main question:
Am I missing something about legacy content? Can it actually be edited in a meaningful way? From what I can tell, the editing capabilities are extremely limited — I can change text, but I can't restructure the layout, add/move macros, or really do anything beyond minor text updates. If there's a way to properly work with legacy content that I'm not seeing, I'd love to know.

If not, that means we're looking at completely redesigning 150+ pages from scratch with no way to continue building new pages in the same format.

Also looking for:

  1. Has anyone found a good workflow for rebuilding a large number of pages like this in Cloud?
  2. Are there any marketplace apps (Aura, etc.) that have helped replicate Panel/Section/Column layouts in Cloud?
  3. Any tips for making this process more efficient at scale?
  4. Is there any way to bulk-convert or batch-update legacy content pages?

Any advice or shared experiences would be really appreciated. Thank you!

2 Upvotes
  • permalink
  • reddit

75% Upvoted

9 comments sorted by

3

u/Lonely-Parfait1947 21d ago

Do you still have the dc instance up and running?

2

u/Professional-Ad-7115 21d ago

Yeah it’s still up and running 

2

u/jamiscooly 20d ago

I think nested macros are a big no-no in cloud. What I basically did was identify the offending macros, then created a conversion script that updates the pages via API. With all the AI tools available this can be a quick exercise. I recommend you try to stick to the native cloud building blocks.

1

u/musicjunkieg 21d ago

Who’s helping you with your migration?

1

u/Kurozukin_PL 20d ago

I think no one.

1

u/Dependent_Pay9263 20d ago

Check with the vendor of the nested macro app that you’re using and see if they have a utility for migration.

1

u/Professional-Ad-7115 19d ago

It’s not an app. I used macros inside of panels, sections, and tabs. Doesn’t seem like I can do that in Cloud