nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to migrate a sub-set of pages from DC to cloud?

chris sieverts

I see that migrating spaces is straight forward but what if you don't want to migrate an entire space but just some of the pages within a space?

There was one question about this a couple years ago here and yes, someone mentions the single page option but I have multiple sub-pages which I don't think will work. Plus there are the limitations such as what will end up being dead hyperlinks.

Am I going to have to import the space & then delete what we don't want?

Thank you!

Accepted answers

Kristian Klima_gtcuat

Hi @chris sieverts

I'd say you have two options:

Do a proper space migration from DC to Cloud, then delete stuff that you don't want. Just as you suggested. This way, you end up with the entire content and relationship among its components. When conducting the post migration sanity check, and deleting obsolete items, you will be to fix links and/or update content to reflect content deletion.
Full migration is officially supported with migration tools.
Export just the selected pages from DC as a space XML export (Settings, export, choose what to export). Then you should be able to import it to Cloud. But to me it sounds like more and more complex/error prone work.

All comments

Matt_ogf1oa

In my mind, the best option would be to do the clean-up and arrangement while on DC.

Copy the space, remove anything you don't want in the cloud, rearrange as needed, and then perform the migration on the ready-for-cloud space.

Kristian Klima_gtcuat

Hi @chris sieverts

I'd say you have two options:

Do a proper space migration from DC to Cloud, then delete stuff that you don't want. Just as you suggested. This way, you end up with the entire content and relationship among its components. When conducting the post migration sanity check, and deleting obsolete items, you will be to fix links and/or update content to reflect content deletion.
Full migration is officially supported with migration tools.
Export just the selected pages from DC as a space XML export (Settings, export, choose what to export). Then you should be able to import it to Cloud. But to me it sounds like more and more complex/error prone work.

chris sieverts

Thank you @Kristian Klima and @Matt all good thoughts. a little more background is that were are testing migrating stuff as we are not moving our users for a bit. I was hoping to move a subset which our DC is still our prod environment and now I'm seeing the users have to come too which I don't want them to and don't want them to know about this. ugh. I was hopeful when I saw the export to HTML but I see now that the cloud doesn't allow for an import of HTML

Matt_ogf1oa

Importing HTML is on the horizon, I got notified it's coming to our tenant next month. If your cloud instance is on continuous release, it may already be there.

This may work for simple pages but retaining valid complex macro syntax will likely be a bit troublesome.

Import data from HTML to Confluence | Confluence Cloud | Atlassian Support

Here's an FAQ related to HTML elements and how they're handled during the import: FAQ import data from HTML to Confluence | Confluence Cloud | Atlassian Support

chris sieverts

thank you @Matt I just saw that email this morning! I'll read through the links you sent. I do suspect that this will be useful for pages without macros but with is likely a different story.

Kristian Klima_gtcuat

@chris sieverts

XML will work. You can export XML from DC and import it to Cloud.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud