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; } } }

Migrate spaces from Confluence download to OnDemand

Neil Wheeler

When I go to import a space into Confluence OnDemand it tells me;

Atlassian OnDemand can only import Confluence space backups from the same major version of Confluence. The current Confluence OnDemand version is 4.3, so backups can only be imported from Confluence 4.3.x.

Our download install of Confluence is on the latest production release 4.2. Does this mean I need to upgrade to 4.3 RC1 before I can export the space for importing into Confluence OnDemand?

Accepted answers

Bob Swift

For my migration, I did the following:

installed a local installation of Confluence at the same level as the production instance
saved the spaces from production
restored them on the the local installation
upgraded the local installation to match the level of onDemand instance
saved the spaces from local installation
restored the spaces onto onDemand

In my case, I had over 30 spaces to move over, so most of the steps were automated with exportSpace and restoreExport from Confluence Command Line Interface

All comments

JustinA

Hi Neil,

Yea, that's absolutely right, mate.

Cheers,

Justin.

Neil Wheeler

So I'm forced to install a RC on Prod to facilitate a migration to OnDemand. Not a practice I'm comfortable with.

Why is 3.4 still RC for download if its the current version on OnDemand? Is the version on OnDemand also RC?

JustinA

Hi Neil,

Yes, I would have to say that the Confluence OnDemand version is indeed on RC. The reason why we release 4.3 in OnDemand is to allow our customers to have the latest release for general usage before the general release. Rest assure that the RC release is more stable than the EAP one.

The 4.3 for general public download is on EAP release, and is definitely not recommended for production use just yet. What I would recommend is to clone your production, and then upgrade the clone to 4.3 EAP for the export of spaces.

Cheers,

Justin.

Bob Swift

For my migration, I did the following:

installed a local installation of Confluence at the same level as the production instance
saved the spaces from production
restored them on the the local installation
upgraded the local installation to match the level of onDemand instance
saved the spaces from local installation
restored the spaces onto onDemand

In my case, I had over 30 spaces to move over, so most of the steps were automated with exportSpace and restoreExport from Confluence Command Line Interface

Welcome!

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

Quick Links

Find more posts tagged with

cloud

confluence-cloud