Revert to Standalone Instance from Accidental Confluence Data Center Migration

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

If you’ve applied a Confluence Data Center license to an existing Server instance, but aren’t ready to set up your cluster, you can follow the workaround in this article to quickly revert back to a Server instance.


In Confluence Server 7.1 and earlier, moving to Confluence Data Center requires you to set up and configure a cluster.

When you apply a Data Center license, we prompt you to start the migration the next time you restart Confluence. At this point, Confluence won't be accessible to your users until you’ve successfully configured your cluster.

Some of the parameters found in your confluence.cfg.xml file will also change to the following:

<setupStep>setupstart</setupStep>
<setupType>standalone.to.cluster</setupType>


From Confluence 7.2 and later, you don't need to configure your cluster as part of the license upgrade. Learn how it works

Workaround

The Confluence Data Center migration process can be reversed by applying the necessary values to the respective parameters in your confluence.cfg.xml file, which is located in your Confluence home directory:

  1. Set complete for setupStep parameter.
  2. Set custom for setupType parameter
  3. Get a Confluence Server evaluation license from My Atlassian, then copy and paste the license key within the atlassian.license.message property.

  4. You should have the following values for the respective parameters:

    <setupStep>complete</setupStep>
    <setupType>custom</setupType>
    ...
    <property name="atlassian.license.message">license-key-here</property>
  5. Restart Confluence.


tip/resting Created with Sketch.

Confluence should now be back to normal, but now you're now running on an evaluation license, which expires after 30 days. This is the time to plan and prepare for your Data Center migration as described in Moving to Confluence Data Center.

If you don't want to migrate to a clustered installation, you can also upgrade to Confluence 7.2, then follow the steps outlined in this guide.

Need more help?

If you have any questions, feel free to reach out to an Atlassian Customer Success Manager. Learn more about the support options available with your Data Center license.


Last modified on Mar 11, 2020

Was this helpful?

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