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!

[Kristian Klima · Accepted solution]

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]

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]

@chris sieverts 

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

[chris sieverts]

Thank you for chiming in again @Kristian Klima since you mentioned that again I did more digging (since I only saw under 'export' tab HTML & PDF) thinking that you would not have said that again if it wasn't possible so I did find exporting to XML under 'backup'. i will give this a whirl.

[Kristian Klima]

https://confluence.atlassian.com/doc/export-content-to-word-pdf-html-and-xml-139475.html

https://help.k15t.com/help/creating-a-xml-export-of-a-space#CreatingaXMLExportofaSpace-ConfluenceServer/DataCenter

[chris sieverts]

Thank you for the docs.

I was able to import it but as it has a fair amount of macros, the macro repair had a bit of work. We are evaluating how successful the repairs were as it seems like a mixed bag.

[Kristian Klima]

There's not 100% parity and some stuff just has no counterpart. The migration tool takes care of something (as far as I remember).

[chris sieverts]

yeah we had looked at the list of unsupported macros and fortunately none of them were in the space but there is something wonky going on with one macro. we will work it through though! thank you guys once again!

[Matt]

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.