Plan your Confluence Server to Cloud migration


This guide provides an overview of recommended activities before, during, and after the migration process. It covers enlisting your project team, evaluating technology options, ensuring that the current Confluence Server site is ready for migration, and executing the migration. 

Not sure if you should migrate from Confluence Server to Cloud? Learn more about the benefits of Atlassian Cloud or check out our Confluence migration FAQs

Confluence Server to Cloud migration journey diagram


Use this guide when you need to migrate:



  1. Choose the right migration strategy: Determining the right migration plan and timeline is a key factor in migrating to the cloud successfully. To get you on the right path, take a few minutes to answer some questions that will analyze your server environment and recommend the best migration approach.
  2. Review your security requirements: Adhering to your organization's security requirements is critical to a successful migration. For more information about Atlassian's security, privacy, and compliance policies, check out Trust at Atlassian. At this point, you may need to engage with your procurement or security teams to ensure Atlassian Cloud meets your requirements.
  3. Evaluate apps: Before deciding to migrate, review any apps and custom integrations you may have to determine what you'll need for your Confluence Cloud site. The Atlassian Marketplace offers a large selection of apps and integrations that extend the functionality of Confluence Cloud. These include free integrations with leading SaaS productivity and collaboration products like Slack and Dropbox, and subscription-based licensing of some of your most beloved Server apps. Keep in mind while you're evaluating that while Atlassian’s cloud and server products provide the same benefits, they can differ in features and functionality. In some cases, you may discover that the cloud version of a product includes functionality that is fulfilled through an app on server. You may also have in-house or custom-built apps to consider. 
    1. If you do need to map third-party apps to Confluence Cloud, first check if there is a cloud equivalent of your server app in our Marketplace. 
    2. If there is a cloud equivalent, your next step would be to check with the app developer to see if it stores any data. Not all apps store data. If it does, you'll need to work with the app vendor to understand your data migration options. Atlassian doesn't directly handle migrating data generated from third-party server apps to cloud apps. If there's no equivalent, you should still contact the vendor to see if there's a way to export app data (if the app stores data). 
  4. Check costs: There's no cost to migrate to Confluence Cloud besides the cost of your Confluence Cloud subscription. However, you'll still want to assess your payment options and overall costs. A few things to keep in mind:
    1. Unlike Confluence Server, Confluence Cloud is sold as a subscription, not a perpetual license. You can pay either monthly or annually, with a discount for paying annually. Check out Confluence Licensing to decide which payment schedule is best for your team and estimate your baseline costs, or try our Atlassian Cloud pricing calculator
    2. If you're planning on using apps from the Atlassian Marketplace in Confluence Cloud, remember to factor these into your cost considerations. The Atlassian Cloud pricing calculator can help you calculate your total monthly or annual cost including apps.
    3. Note that your existing Confluence Server license and maintenance do not transfer to Confluence Cloud. These are two separate licenses, and are paid for separately.
  5. Review the FAQs: We've developed a comprehensive set of FAQs in the Atlassian Cloud Migration Center to assist you in planning your Confluence migration. If you have questions that we don't cover, let us know.
  6. Trial Confluence Cloud: Sign up for a free Confluence Cloud trial to give Confluence Cloud a spin. Keep in mind as you trial that the design and layout aren't the same across Confluence Server and Confluence Cloud, and you can't switch between the two. We recommend trialing Confluence Cloud before migrating to get comfortable with the differences and identify any communications or training needed to help onboard your users.



  1. Assemble your team: Migrating from Confluence Server to Cloud will have an impact on your users' experience and workflows, as well as various stakeholders throughout your organization. Depending on the size of your organization and number of users, a migration may require a fully fledged project with defined roles and responsibilities across teams. As early as possible, you should communicate with individuals and stakeholders who are interested and impacted by a move to Confluence Cloud. Where possible, recruit and enlist these people to be a part of the process.
  2. プロアクティブかつ頻繁に連絡する: 移行スケジュールについて組織に知らせる前に、チーム メンバーと移行計画を共有します。発生する問題やエラーについて、ユーザーにどのように警告するかを決定します。この段階では、移行のコミュニケーション計画に以下のような内容を含める必要があります。
    1. When will the migration occur?
    2. ユーザーが想定すべきダウンタイム
    3. 移行中はあらゆる変更を加えないよう、ユーザーに依頼する
    4. 移行後の古いサイトへの影響。アクセスまたは読み取りが引き続き可能かどうか
  3. Prepare your Confluence Server site: Evaluate your current environment to determine if you need to make any changes before migrating your data.
    1. If you're using the Cloud Migration Assistant for Confluence, you'll need to upgrade your Confluence Server to version 5.10 or later before migrating. The migration assistant is not available on versions earlier than 5.10.
    2. You may also want to take this opportunity to clean up or remove any unnecessary data.
  4. Back up your data: Back up your site data before migrating to Confluence Cloud. If data is present in your Confluence Cloud site, back it up for safekeeping as well.
  5. Create your Atlassian Cloud siteSign up for a free Confluence Cloud trial and choose a site domain name. Domain names are chosen for an entire Atlassian Cloud site at the time you sign up for your first Atlassian Cloud product – for example, when you first sign up for Jira Software Cloud or Confluence Cloud. The format for the domain name is, where example is a unique character string that you specify. There are a few things to be aware of when choosing your domain name:
    1. 6 文字以上の一意の文字列にする必要があります。
    2. 英数字のみを含めることができ、特殊文字は使用できません。
    3. We don't currently support changing or renaming your site URL after you've chosen. Once your cloud site is created, if you want to change the domain name you will need to migrate from one cloud instance to a new cloud instance with the new name you prefer.
  6. Move your users to Confluence Cloud: The Cloud Migration Assistant for Confluence only migrates spaces. It will not yet migrate your users or groups to Confluence Cloud. We recommend adding your users to Confluence Cloud before migrating spaces. If you have a large number of users, please contact support to help you move your users.
  7. Server plan: You'll also need to decide what to do with your Confluence Server site. Some common options include switching it off, backing it up and storing the data somewhere safe, or operating a hybrid (both server and cloud) environment. 
  8. Get Org-anized: An organization allows you to view all Atlassian Cloud users at your company in one place, manage your users' accounts, and set up security features like SAML SSO. Learn more in our Atlassian Cloud admin security guide. You can create an organization for your company in the Atlassian Admin Hub.
  9. Review your anonymous access settings: To ensure that every user must be logged in to Confluence Cloud and have access to your site, confirm that anonymous access is not allowed in your Confluence Server global permissions as described in Setting Up Public Access. If you want to allow anonymous access to certain spaces and not others, you need to allow anonymous access in the global permissions for Confluence Cloud, and then review the space permissions for each individual space to determine whether they allow anonymous access. Disabling anonymous access in the global permissions will disable anonymous access at the space level as well.


  1. Migrating Jira and Confluence: If you are migrating both Jira and Confluence, we recommend migrating Jira first in order to move your users to cloud. Migrating Confluence before Jira will result in your users being wiped from cloud once Jira is imported. Learn more about migrating Jira from server to cloud. After migrating Jira along with your users, you can use the Cloud Migration Assistant for Confluence to migrate your Confluence spaces from Confluence Server to Confluence Cloud.
  2. Partner network: If you need assistance with your migration, we have a wide network of partners globally that are very experienced in Atlassian migrations. Visit our Atlassian Partners page to find one who can help with your migration.



  1. Run a test migration: We recommend performing a trial run in a testing or staging site to ensure that your site's integrations, functionality, and performance are working as expected and the migration runs smoothly. You can do this using a free Confluence Cloud trial. The test migration will help you:
    1. Identify possible bugs and the steps needed to resolve before the actual migration.
    2. Establish a clearer timeline for your live migration, including any expected downtime.
    3. Validate the data before moving to Confluence Cloud.
  2. Build a timeline: Identifying an ideal migration window can mean the difference between happy and frustrated users. Determine how much time your migration will take, factoring in time for troubleshooting. Consider scheduling the migration for overnight, on a weekend, or when your team is less likely to need access to Confluence. This will reduce the risk of data discrepancies between server and cloud.
  3. Migrate to cloud: To perform the migration, use the Cloud Migration Assistant for Confluence. 
    When you migrate, the following data is imported:
    • Site data, including spaces, pages and attachments.


    • Users, groups, and permissions. These should be added to your Confluence Cloud site before you migrate.
    • Apps. You will need to work with vendors to migrate or re-install your apps in Confluence Cloud after migrating.
    • Application links. You will need to set these up in your Confluence Cloud site after migrating.



  • Merging server sites: If you need to merge multiple Confluence Server sites, just install the Cloud Migration Assistant for Confluence on all server instances and move them separately to the Confluence Cloud site. Keep in mind that every space in your Confluence Cloud site needs to have a unique space key. If a space key already exists in your Confluence Cloud site, trying to migrate a space with the same space key will cause that individual spaces' migration to fail.


If you've run into a problem during your migration, we're here to help. You can start by searching for known issues in our public issue tracker. There, you can find information about some of the common issues we see with Confluence migrations, including their status and suggested workarounds.


異なる問題が発生した場合、または移行を進めるのに支援が必要な場合は、テクニカル サポート チームにお問い合わせください。



  1. Review your cloud siteWhen your migration is complete, you will need to review the new Confluence Cloud site to ensure your data and attachments have migrated successfully. We recommend:
    1. Checking spaces for common things, e.g. comments, attachments, and permissions.
    2. Allowing time for different teams and users to test different functionality.
    3. アプリケーションの操作や機能をテストし、動作の違いが見られた場合はそれを特定して、必要に応じてユーザーに共有。 
  2. Install apps: If you've identified apps that should be installed, add them to your Confluence Cloud site.

  3. Get acquainted with cloud: To learn more about what's new in Confluence Cloud and how to get the most of it, check out the Confluence Cloud documentation. Consider sharing this resource with your users if this is their first introduction to Confluence Cloud. You may also find the Atlassian Cloud documentation a helpful resource as you get started as a Confluence Cloud admin.
  4. Welcome your team: Now that the migration is complete, make sure your organization is ready. We recommend developing a comprehensive launch communication plan to share the new Confluence Cloud site information with the team. This can cover topics like:
    1. 移行後に必要なアクション
    2. ユーザーがパスワードをリセットする必要があるかどうか 
    3. 新しいサイトへアクセスする際に使用する URL
    4. 質問の問い合わせ先および問い合わせ方法。たとえば、課題やフィードバックを送信できるチャット ルームや課題トラッカーがあるかどうか
    5. ユーザーが認識しておくべき重大な変更
    6. その他の資料や FAQ へのリンク
    7. Let people know about the Confluence Cloud mobile app.

Jira Cloud の利用を開始

Now that you're a cloud admin, you'll have immediate access to our latest features and bug fixes. Installs, upgrades, and patches are managed seamlessly by Atlassian, so you can relax on your weekends. 

To keep track of major changes that affect all users of the Confluence Cloud products, follow the Atlassian Cloud Documentation blog. This includes new features, bug fixes, and other changes across all Atlassian Cloud products, for example, updates to the meeting notes templates or the ability to drag and drop spaces for easy space reorganization in Confluence Cloud.


Need more support with strategy, best practices, or planning questions? Our migration planning specialists can help with planning your migration from Confluence Server to Confluence Cloud. 

技術的な質問がある場合や、問題が発生している場合は、テクニカル サポート チームにお問い合わせください。

For more Confluence migration planning information and FAQs, visit the Atlassian Cloud Migration Center.


最終更新日: 2019 年 2 月 16 日


Powered by Confluence and Scroll Viewport.