Moving to Confluence Data Center

Still need help?

The Atlassian Community is here for you.

Ask the community

Below is the process for migrating from Confluence Server to Confluence Data Center, which is a clustered solution.

There's also a note on moving the other way, from Confluence Data Center to Server.

Your Confluence license will determine the type of Confluence you have: Server or Data Center. Confluence will auto-detect the license type when you enter your license key on the 'License Details' page in Confluence administration. If you've entered a different type of license, it'll automatically prompt you to begin the migration (from Confluence Server to Data Center, for example)

If you're installing Confluence for the first time (you don't have any existing Confluence data to migrate), see Installing Confluence Data Center

Not sure if you should upgrade from Confluence Server to Data Center? Learn more about the benefits of Confluence Data Center.

Moving from Server to Data Center

Clustering requirements and terminology

To run Confluence in a cluster, you must:

On this page:

  • Have a Data Center license (you can purchase a Data Center license or create an evaluation license at
  • Use an external database
  • Use a load balancer with session affinity in front of the cluster
  • Have a shared directory that's accessible by the same path to all cluster nodes (this will be your shared home directory)
  • Use OAuth authentication if you have application links to other Atlassian products (like JIRA applications). 

If you need a Confluence Data Center evaluation license, get in touch with us.  

In this guide we'll use the following terminology:
  • installation directory – The directory where Confluence is installed.
  • local home directory – The home or data directory on each node (in non-clustered Confluence this is simply known as the home directory).
  • shared home directory – The directory you created that is accessible to all nodes in the cluster via the same path.

At the end of the installation process you'll have an installation directory and local home directory on each node, and a single shared home directory (for example, in a two node cluster you'd have a total of 5 directories). 

1. Upgrade Confluence Server 

If you're switching to Confluence Data Center 5.9 or later follow the normal procedure for backing up and upgrading Confluence first. See upgrading Confluence for information on upgrading and choosing the best upgrade path.

If you're switching to Confluence Data Center 5.8 the process for upgrading is a little different.  Refer to our earlier documentation for more information. 

2. Apply your Data Center license 

Your home directory (configured in confluence\WEB-INF\classes\ should still be pointing to your existing (local) home directory.

  1. Go to  > General administration.
  2. Choose License Details from the sidebar under the Administration heading.
  3. Enter your Confluence Data Center license key.
  4. Shut down Confluence.

3. Create a shared home directory 

  1. Create a directory that's accessible to all cluster nodes via the same path. This will be your shared home directory. 
  2. In your existing Confluence home directory, move the contents of <confluence home>/shared-home to the new shared home directory you just created.
    To prevent confusion, we recommend deleting the empty <confluence home>/shared-home directory once you've moved its contents.
  3. Move your attachments directory to the new shared home directory (skip this step if you currently store attachments in the database). 

4. Start Confluence

The setup wizard will prompt you to complete the migration, by entering:

  • A name for your cluster
  • The path to the shared home directory you created earlier
  • The network interface Confluence will use to communicate between nodes
  • A multicast address (automatically generated or enter your own) or the IP addresses of each cluster node
  • How you want Confluence to discover cluster nodes:

    • Multicast - enter your own multicast address or automatically generate one.
    • TCP/IP - enter the IP address of each cluster node
    • AWS - enter your IAM Role or secret key, and region.

      AWS node discovery...

      We recommend using our Quick Start or Cloud Formation Template to deploy Confluence Data Center in AWS, as it will automatically provision, configure and connect everything you need.

      If you do decide to do your own custom deployment, you can provide the following information to allow Confluence to auto-discover cluster nodes:

      Field Description
      IAM Role or
      Secret Key
      This is your authentication method. You can choose to authenticate by IAM Role or Secret Key.
      Region This is the region your cluster nodes (EC2 instances) will be running in.
      Host header Optional. This is the AWS endpoint for Confluence to use (the address where the EC2 API can be found, for example ''). Leave blank to use the default endpoint.
      Security group name Optional. Use to narrow the members of your cluster to only resources in a particular security group (specified in the EC2 console).
      Tag key and Tag value

      Optional. Use to narrow the members of your cluster to only resources with particular tags (specified in the EC2 console).

Your first node is now up and running.  

2. Set up Synchrony

Collaborative editing requires Synchrony, which runs as a separate process. You can deploy Synchrony on the same nodes as Confluence, or in its own cluster with as many nodes as you need.  You'll need to complete step one (including entering your Data Center license) before you start this step.

In this example, we assume you'll run Synchrony in its own cluster. When configuring your cluster nodes you can either supply the IP address of each Synchrony cluster node, or a multicast address.

  1. Create a Synchrony directory on your first node and copy synchrony-standalone.jar from your Confluence <home-directory> to this directory. 
  2. Copy your database driver from your Confluence <install-directory>/confluence/web-inf/lib to an appropriate location on your Synchrony node.
  3. Change to your Synchrony directory and start Synchrony using the following command.
    You need to pass all of the system properties listed, replacing the values where indicated.

    Start Synchrony command...

    In a terminal / command prompt, execute the following command, replacing <values> with appropriate values for your environment. Scroll down for more information on each of the values you will need to replace.

    # To set the classpath in Linux  
    # To set the classpath in Windows 
    # Remove this section if you don't want to discover nodes using TCP/IP
    # Remove this section if you don't want to discover nodes using multicast
    # Remove this section if you don't need to discover nodes in AWS
    # The following property must be passed, but its value does not matter

    (warning) Remember to remove all commented lines completley before you execute this command, and replace all new lines with white space. You may also need to change the name of the synchrony-standalone.jar if the file you copied is different to our example.


    Here's more information about each of the values you'll need to supply in the command above.

    Value Description
    This is the HTTP port that Synchrony runs on. We suggest port 8091, if available.
    This is Synchrony's Hazelcast port. We suggest port 5701, if available. As with Confluence's Hazelcast port (5801) you should ensure that only permitted cluster nodes are allowed to connect to this port, through the use of a firewall and or network segregation.
    This is the Aleph binding port. Synchrony uses Aleph  to communicate between nodes. We suggest port 25500, if available.
    <TCPIP_ MEMBERS> If you choose to discover nodes using TCP/IP, provide a comma separated list of IP addresses for each cluster node.
    <MULTICAST_GROUP> If you chose to discover nodes using multicast, specify an IP address for the multicast group.
    This is the public IP address or hostname of this Synchrony node. It could also be a private IP address - it should be configured to the address where Synchrony is reachable by the other nodes.
    <SYNCHRONY_URL> This is the URL that the browser uses to contact Synchrony. Generally this will be the full URL of the load balancer Synchrony will run behind plus the Synchrony context path, for example Note that it does not end with /v1, unlike the synchrony.service.url system property passed to Confluence. If this URL doesn't match the URL coming from a users' browser, Synchrony will fail.
    These keys are generated by Confluence. Copy each key from the <local-home>/confluence.cfg.xml file on your first Confluence node. The keys must be the same on all Confluence and Synchrony nodes.
    This is the URL for your Confluence database. For example jdbc:postgresql://localhost:5432/confluence. You can find this URL in <local-home>/confluence.cfg.xml.
     The username and password for your Confluence database user.
    This is the path to the synchrony_standalone.jar that you copied in step 1. For example <synchrony-directory>/synchrony_standalone.jar
    This is the path to your database driver. For example <synchrony-directory>/postgresql-9.2-1002.jdbc.jar.

    Sensitive information (like database credentials) may be provided using environmental variables, rather than via the command line. Any dots (".") in variable names (identifiers) will need to be replaced with underscores ("_"). 

    A few other properties can be modified to suit your environment. See Configuring Synchrony for Data Center for more information.

    (warning) You can use this info to create your own script to run Synchrony, or follow the steps in this guided example to create a service script - Run Synchrony-standalone as a service on Linux.


  4. To check that Synchrony is accessible, you can go to:
  5. Repeat this process to start Synchrony on each node of your Synchrony cluster.
    As each node joins you'll see something like this in your console.

    Members [2] {
    	Member []:5701
    	Member []:5701 
  6. Configure your load balancer for Synchrony.
    Your load balancer must support WebSockets (for example NGINX 1.3 or later, Apache httpd 2.4, IIS 8.0 or later) and session affinity. SSL connections must be terminated at your load balancer so that Synchrony can accept XHR requests from the web browser. 

3. Start Confluence on Node 1

  1. Start Confluence on node 1 and pass the following system property to Confluence to tell Confluence where to find your Synchrony cluster.


    For example You must include /v1 on the end of the URL.

    You may want to add this system property to your <install-directory>/bin/ or setenv.bat so it is automatically passed every time you start Confluence. See Configuring System Properties for more information on how to do this in your environment.

  2. Head to  > General Configuration > Collaborative editing to check that this Confluence node can connect to Synchrony. 

    Note: to test creating content you'll need to access Confluence via your load balancer.  You can't create or edit pages when accessing a node directly.

4. Copy Confluence to second node

To copy Confluence to the second node:

  1. Shut down Confluence on node 1
  2. Shut down your application server on node 2, or stop it automatically loading web applications
  3. Copy the installation directory from node 1 to node 2
  4. Copy the local home directory from node 1 to node 2
    If the file path of the local home directory is not the same on nodes 1 and 2 you'll need to update the <installation directory>/confluence/WEB-INF/classes/ file on node 2 to point to the correct location.

Copying the local home directory ensures the Confluence search index, the database and cluster configuration, and any other settings are copied to node 2.

5. Configure load balancer

Configure your load balancer for Confluence. You can use the load balancer of your choice, but it needs to support session affinity and WebSockets.

SSL connections must be terminated at your load balancer so that Synchrony can accept XHR requests from the web browser.

You can verify that your load balancer is sending requests correctly to your existing Confluence server by accessing Confluence through the load balancer and creating a page, then checking that this page can be viewed/edited by another machine through the load balancer.

6. Start Confluence on the first node, wait, then start Confluence on second node

You must only start Confluence one server at a time.

  1. Start Confluence on node 1
  2. Wait for Confluence to become available on node 1
  3. Start Confluence on node 2
  4. Wait for Confluence to become available on node 2.

The Cluster monitoring console ( > General Configuration > Clustering) includes information about the active cluster.

When the cluster is running properly, this page displays the details of each node, including system usage and uptime. Use the menu to see more information about each node in the cluster.

Screenshot: Cluster monitoring console

7. Test your Confluence cluster

Remember, to test creating content you'll need to access Confluence via your load balancer.  You can't create or edit pages when accessing a node directly.

A simple process to ensure your cluster is working correctly is:

  1. Access a node via your load balancer, and create a new document on this node
  2. Ensure the new document is visible by accessing it directly on a different node
  3. Search for the new document on the original node, and ensure it appears
  4. Search for the new document on another node, and ensure it appears

If Confluence detects more than one instance accessing the database but not in a working cluster, it will shut itself down in a cluster panic. This can be fixed by troubleshooting the network connectivity of the cluster.


Ensure that only permitted cluster nodes are allowed to connect to a Confluence Data Center instance's Hazelcast port (which defaults to 5801) or Synchrony's Hazelcast port (which defaults to 5701) through the use of a firewall and or network segregation.


If you have problems with the above procedure, please see our Cluster Troubleshooting guide.

If you're testing Confluence Data Center by running the cluster on a single machine, please refer to our developer instructions on Starting a Confluence cluster on a single machine.

Moving from Data Center to Server

If you need to move from Data Center (clustered) to Server (non-clustered), read on. In these instructions we'll assume that you'll use one of your existing cluster nodes as your new, non-clustered installation. 

You'll need a Confluence Server license to switch back to Server.

Before you complete this process

As a precaution, we recommend shutting down all nodes except one, and running Confluence on a single node.

1. Enter your Confluence server license

Your home directory (configured in confluence\WEB-INF\classes\ should point to your local home directory.

  1. Go to  > General administration
  2. Choose License Details from the sidebar under the Administration heading
  3. Enter your Confluence Server license key

2. Shut down Confluence

Stop any cluster nodes that are still running before proceeding. We also recommend configuring your load balancer to redirect traffic away from Confluence.

3. Move items in the cluster shared home back to local home

  1. Create a directory called /shared-home in the <local home> directory on one node (if you removed this directory when installing Data Center)
  2. Move the entire config directory from your <shared home> directory to the <local home>/shared-home directory
  3. Move the remaining contents of your <shared home> directory to the root of your <local home> directory

Your cluster's shared home directory should now be empty. 

4. Start Confluence

The setup wizard will guide you through the migration process.

tip/resting Created with Sketch.

To confirm you're now running the non-clustered edition, go to  > General Configuration. The 'Cluster Configuration' page should not appear. Instead you'll see information about Confluence Data Center.

Last modified on Aug 15, 2018

Was this helpful?

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