Confluence Server から Cloud への移行計画

Confluence Server から Cloud への移行リソース



アトラシアン コミュニティをご利用ください。


description Use this guide to plan every step of your migration from Confluence Server or Data Center to Confluence Cloud. Find all the documentation and resources to help you make the move.

This guide provides a high-level plan for migrating a self-hosted Confluence Server or Data Center site to Confluence Cloud. Before getting started, learn more about migrating to Atlassian's cloud products and check out our Confluence migration FAQs

Here, we'll cover enlisting your project team, evaluating technology options, ensuring that your self-hosted environment is ready for migration, and executing the migration.

Some of the steps in this guide require advanced permissions. Before you begin, you may want to check that you:

  1. Confluence Server でシステム管理グローバル権限を保持していること。
  2. クラウド サイトsite-admins グループに所属していること。これによってすべてのアプリケーション (Confluence、Jira)、それらの管理機能、およびサイト管理機能へのアクセス権が付与されます。サイト管理機能にはユーザーや請求の管理機能が含まれます。


The first step to any migration is understanding your current landscape, and where you're headed.

  1. セキュリティとコンプライアンス要件の確認: 移行を成功させるためには、組織のセキュリティ要件を順守することが不可欠です。アトラシアンのセキュリティ、プライバシー、およびコンプライアンス ポリシーの詳細については、Trust at Atlassian をご確認ください。この時点で、Confluence Cloud が要件を満たしていること確認するために、調達チームやセキュリティ チームとの連携が必要となる場合があります。
  2. 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. To help you through this, we've put together some advice and best practices.

    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. 

    More on migrating apps to cloud

    App data is not included when migrating from Confluence Server to Confluence Cloud. This includes apps from Atlassian, like Team Calendars for Confluence and Questions for Confluence. Some apps do have the capability to export and import their data but you'll need to check with the app developers or their documentation to confirm if this is possible.

    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. 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 and the app stores data, you should still contact the vendor to see if there's a way to export the data. 

  3. 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. Atlassian offers extended cloud trials to self-hosted customers — at no cost — to help with your migration. This offer allows you to try cloud for an extended period, giving you the time you need to assess, plan, test, and migrate without paying twice for both cloud and server. 

    2. Unlike Confluence Server, Confluence Cloud is sold as a subscription, not a perpetual license. If you choose a Standard or Premium plan, you can opt to pay monthly or receive a discount for paying annually. Check out Confluence Licensing to decide which plan and billing cycle is best for your team.

    3. Note that you can’t roll an active Confluence Server license into a Confluence Cloud subscription. These are two separate products and are paid for separately.

    4. If you're planning on using Atlassian Marketplace apps in Confluence Cloud, remember to factor these into your cost considerations. To estimate your total cost — including which cloud products, plan, apps, and billing cycle you choose — try our cloud pricing calculator



  1. FAQ の確認: Atlassian Cloud 移行センター内に、Confluence の移行計画を支援する包括的な FAQ を作成しました。ここに含まれない質問がある場合、お知らせください。
  2. Compare plans: We offer multiple plans for Confluence Cloud: Free, Standard, and Premium. Free plans are limited to 10 users and 2 GB of storage. Standard plans include 250 GB of storage. Premium plans are designed to give teams the confidence to scale reliably with advanced features, plus a 99.9% uptime SLA, unlimited storage, and 24/7 Premium Support. Learn more about the plans and options available.

  3. Try out Confluence Cloud: Sign up for your extended cloud trial. (Or if the Free plan meets your needs, you can set up a site, directly.) While signing up, you’ll need to choose your Atlassian cloud site name (URL).

    Tips for choosing your site URL

    The format for your site name will be, where example is a unique character string that you specify.

    Site names are chosen for an entire Atlassian cloud site at the time you sign up for your first product — for example, when you first sign up for Jira Software Cloud or Confluence Cloud.

    There are a few things to be aware of when choosing your site name:

    • 3 文字以上の一意の文字列にする必要があります。

    • 英数字とハイフンのみを使用できます。

    • 1 文字目または最後の文字をハイフンにすることはできません。

    If you'd prefer a separate testing and staging environment, there are a few other ways to set this up which you can learn about here.

    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.

  4. チームを集める: Confluence Server から Cloud への移行は、ユーザーのエクスペリエンスやワークフロー、組織全体のさまざまなステークホルダーに影響する可能性があります。移行では、組織の規模とユーザー数に応じて、チームを横断してロールや責任が定義された、完全に独立したプロジェクトが必要となる場合があります。Confluence Cloud への移行に関心を持っていたり、移行の影響を受けたりする個人やステークホルダーに、できるだけ早い時期に連絡することをおすすめします。可能であれば、これらのスタッフをチームに加え、プロセスの一部として参加を依頼します。
  5. プロアクティブかつ頻繁に連絡する: 移行スケジュールについて組織に知らせる前に、チーム メンバーと移行計画を共有します。発生する問題やエラーについて、ユーザーにどのように警告するかを決定します。この段階では、移行のコミュニケーション計画に以下のような内容を含める必要があります。
    1. 移行のタイミング
    2. ユーザーが想定すべきダウンタイム
    3. 移行中はあらゆる変更を加えないよう、ユーザーに依頼する
    4. 移行後の古いサイトへの影響。アクセスまたは読み取りが引き続き可能かどうか
  6. Prepare your self-hosted site: Evaluate your current environment to determine if you need to make any changes before migrating your data.
    1. Check if you're on a supported server version. To use the Confluence Cloud Migration Assistant, you'll need to upgrade your Confluence Server to version 5.10 or later before migrating. 
    2. You may also want to take this opportunity to clean up or remove any unnecessary data. For guidance on what to clean up, refer to our migration testing guide.

  7. 匿名アクセス設定の確認: 
    1. Confluence Cloud サイトに未ログインの匿名ユーザーがアクセスすることを禁止したい場合、サーバー側で匿名アクセスが有効化されていないことを移行前に確認します。詳細については「パブリック アクセスのセットアップ」をご参照ください。
    2. 特定のスペースのみに匿名アクセスを許可する場合、Confluence Cloud のグローバル権限で匿名アクセスを許可してから、個々のスペースのスペース権限を確認して匿名アクセスを許可するかどうかを決定します。Confluence Cloud のグローバル権限で匿名アクセスを無効化すると、スペース レベルでも匿名アクセスが無効になります。
  8. データのバックアップ: Confluence Cloud へ移行する前に Confluence Server データをバックアップします。Confluence Cloud サイト内にデータが存在する場合、同様に安全のためにバックアップします。

Migration Services

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. Set up your organization: An organization allows you to view all of the Atlassian Cloud users at your company in one place, manage your users' accounts, and set up security features like SAML SSO. Organizations are particularly helpful if your company manages more than one cloud site and wants insight into all your sites, products, and the users who can access them. An organization is available for every site and can be accessed at Learn more about how to set up an Atlassian organization.
  2. Set up SSO: If you plan to use SSO in your cloud site, you should set this up in advance so that it will continue working seamlessly for your users when you migrate. Before setting up SSO, you'll need to verify a domain for your organization. Note that SSO requires a subscription to Atlassian Access, which you can trial free for 30 days. If you need more than 30 days to test, just reach out and we can extend your trial as needed.
  3. Run a test migration: We recommend performing a trial run to ensure that your site's integrations, functionality, and performance are working as expected and the migration runs smoothly. Learn more about how to do this in our migration testing guide.

    If you’re migrating from Confluence Data Center or have a large amount of data or attachments, we recommend breaking your migration into multiple smaller chunks. You can do this by selecting only some spaces at a time in the Confluence Cloud Migration Assistant

  4. Install or migrate apps: Install and trial any apps you're planning to use on your cloud site, or if you're planning to migrate apps, work with the app vendor to migrate the data.
  5. 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.



  1. Migrate to cloud: To perform the migration, use the Confluence Cloud Migration Assistant. When you migrate, the following data is imported:
    • サイト データ (スペース、ページ、および添付ファイルを含む)。
    • ユーザーとグループ。


    • グローバル設定と権限: これらはクラウド サイトで手動で設定する必要があります。
    • アプリ: 移行後に Confluence Cloud にアプリを移行または再インストールするには、ベンダーに支援を依頼する必要があります。Team Calendars for Confluence や Questions for Confluence などのアトラシアンのアプリは移行に含まれない点にご注意ください。
    • Application links: If you plan to use Atlassian server products in conjunction with your Confluence Cloud site, you can create two-way links between your cloud and server products. If this applies to you, you can set set these up after migrating.
    • User avatars: Users will need to update their avatars after migrating.
    • Passwords: Users will need to reset their passwords after migrating (unless you're using SSO).



サーバー サイトの統合

If you need to merge multiple Confluence Server sites, just install the Confluence Cloud Migration Assistant on all server instances and move them separately to the Confluence Cloud site.

Confluence Cloud サイトのすべてのスペースに一意のスペース キーが必要である点にご注意ください。Confluence Cloud サイトにすでにスペース キーが存在する場合、同じスペース キーでスペースを移行しようとすると、その個別のスペースの移行が失敗します。


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.


異なる問題が発生した場合や、移行に際して支援が必要な場合は、アトラシアンのテクニカル サポート チームや、アトラシアン コミュニティへのお問い合わせをご検討ください。


After you've successfully completed the migration, you'll need to go through a series of post-migration tasks to ensure that everything is functioning as smoothly and efficiently as possible before welcoming your team to cloud.

  1. Review your cloud site: When your migration is complete, you will need to review the new Confluence Cloud site to ensure your data and attachments have migrated successfully. Our testing guide outlines some recommended things to check for. 
  2. Install or migrate apps: If you've identified apps that should be installed, add them to your Confluence Cloud site. If you have apps to migrate, work with the individual app vendors to migrate those a well.
  3. Set your server to read-only: If you’re no longer planning to run your server instance, you can set it to read-only mode after migrating to help with the switchover. 
  4. Redirect users to the new cloud site URL: We recommend using site-wide banners both prior to your migration, to help alert users of your upcoming migration, as well as after migrating. This can help direct users still coming to server to your new cloud site URL.
  5. Welcome your team: Now that the migration is complete, make sure your organization is ready. Once migrated, you'll need to send an invitation or the link to your new site to your users so they can start using it. They will not be automatically invited. After you invite them, they'll also need to reset their passwords and avatars.

    We recommend developing a comprehensive launch communication plan based on your User Acceptance Testing findings to share the new Confluence Cloud site information with the team. This can cover topics like:

    1. Will users need to reset their passwords and avatars? Unless you’ve already set up SSO, they’ll need to reset both here after migrating.

    2. What URL will they use to access the new site? For Confluence Cloud, the format to go directly to the homepage will be, where yoursite is the unique character string of your cloud site URL. If you have both Jira and Confluence Cloud, users can also log in at to access both.

    3. Who can they contact with questions, and how? For example, can you provide a chat room or an issue tracker where people can raise any issues or feedback?

    4. Are there any notable changes they'll need to be aware of? For example, changes in functionality due to different apps, or tips on how to navigate the new UI?

    5. その他の資料や FAQ へのリンク

    6. Confluence Cloud モバイル アプリについてユーザーに共有する


  1. 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.
  2. Follow our cloud security best practices: Create a strong foundation for securing your company’s most important work. Learn more.
  3. Sit back and relax: 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.




最終更新日 2019 年 9 月 19 日


Powered by Confluence and Scroll Viewport.