Migrate from Confluence Cloud to Server

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

This page is for people who are currently using Confluence Cloud, and wish to move to Confluence Server (a Confluence installation hosted on your own servers).

For migrating from Confluence Server to Confluence Cloud, see Importing wiki data.

On this page:

You can migrate from your Confluence Cloud to Confluence Server 5.10 or later only. You can't import Cloud data (whole site or individual space exports) into any earlier versions of Confluence.  We recommend installing the latest version. 

Confluence Cloud is typically ahead of Confluence Server, which means that some features may not be available after you've moved to Confluence Server.  


As of 8 June 2016 you do not need to download a special Cloud installable release. You can import your content directly into Confluence 5.10 or later.

You can't import from Cloud into Confluence 5.9.

Migration steps

To migrate from Confluence Cloud to Confluence Server:

  1. Export the data from your Confluence Cloud site, using the Confluence backup manager. 
    • For detailed instructions, see Exporting wiki data.
    • You now have an XML export of your Confluence data.
  2. Download the latest Confluence Server release.
    You will only be able to import your Cloud backup into Confluence 5.10 or later. We recommend always installing the latest release.
  3. Follow the Confluence Installation Guide for your platform to install Confluence.
  4. Import the data from your backup file (XML export) into your new Confluence installation - see Restoring a Site.
  5. Log in to your new Confluence site, using the following credentials: 
    • Username: sysadmin
    • Password: sysadmin
  6. Change the password immediately after logging in. This will be your system administrator account. 

Support, limitations, and recommendations

Please note the following about your new Confluence Server site.

  • If you're unable to remove the JIRA cloud application link from your Confluence after the import, you'll need to remove those references directly from the Confluence database as per this guide.
  • The User Management section might be missing due to CONF-35177 - Getting issue details... STATUS
    Follow the workaround notes on the issue to enable the feature again.

  • If your Confluence Cloud instance has macros that depend on the Application Links back to a JIRA Cloud instance, and you are migrating JIRA as well, these references will need to be updated to work properly as per APL-1144 - Getting issue details... STATUS
    You can address that by either editing the XML prior to import, or by bulk editing those references in Confluence database as per this guide .

  • If you experience problems loading pages after the import, head to  > General Configuration to check your base URL as the port may have changed. 


After migrating your data you will need to install any compatible add-ons, such as Questions and Team Calendars. 

Some third party add-ons are only available for Cloud, and will no longer be available after you migrate.  You can check whether your essential add-ons are available for Confluence Server, Cloud or both on Atlassian Marketplace. 

Database considerations 

If you are uncertain about which database to choose for your new Confluence installation, we recommend PostgreSQL - see Database Setup for PostgreSQL. The Confluence Cloud site runs on PostgreSQL, so there should be no compatibility issues.

If you choose another supported database, Contact Support if you encounter any compatibility issues with other supported databases.

Confluence license

You will need a new license to migrate to Confluence Server. Your existing Cloud license cannot be used.  You can get a new license at https://my.atlassian.com.  You may also need new licenses for any paid add-ons. 

Last modified on Jun 23, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.