Server から Cloud への移行のテスト

description Learn best practices for testing your migration from Jira or Confluence server to cloud.

A well-planned migration is a successful migration. Before starting your testing, take the time to review our planning guides for Confluence and Jira. They'll walk you through the key phases and consideration for each step, including what you need to know before you begin testing.

When you're planning a migration from server or Data Center to cloud, we strongly recommend performing a trial run before migrating. Testing your migration will help you:

  1. 予想されるダウンタイムも含めた、実際の移行のタイムラインの明確化。
  2. Validate the data and run User Acceptance Testing (UAT).
  3. Prepare for your launch and develop onboarding communications.
  4. Identify possible bugs and the steps needed to resolve them before the actual migration.

In this guide, we'll outline how to conduct a test migration for Jira or Confluence, including best practices and what to test for.


The same prerequisites apply for a test migration as for a production migration. For a full list of prerequisite, refer to the Confluence or Jira migration documentation. 


If you've completed your pre-migration checks, you're ready to go.

Here's an overview of the basic steps we recommend to test your migration and prepare for your production migration:

  1. Clean up your data
  2. Sign up for your cloud site
  3. (Optional) Set up Atlassian Access
  4. Perform the test migration
  5. Review your data and conduct User Acceptance Testing (UAT)
  6. (Optional) Reset your test site
  7. Create your migration runbook
  8. Develop your change-boarding and launch plan

Step 1: Clean up your data

The more data you migrate, the longer and more complex your migration is likely to be. Because of this, we recommend taking the time to clean house, so to speak, before running your test migration. This can result in a smoother migration, fewer performance issues, and even productivity gains once in cloud. 

Below are a few specific things to consider reviewing.

In general

  • Check that people are in the right groups, and fix any permissions that may be incorrect or need updating.
  • Review your apps and integrations to see which are being used, which aren't, and if there are cloud features or apps that can replace them. 

For Jira

  • Minimize customizations as much as possible. This could include:
    • Standardizing workflows. This can simplify things for teams wanting to start new projects. 
    • Reviewing groups and permission schemes to see which are being used, which aren't, and if there are opportunities to standardize or simplify them. 
    • Streamlining custom fields, schemes, issue types, statuses, resolutions, boards, filters, and screens.
  • Think carefully about what data you can clean up, This could include:
    • Checking for and removing any unused apps or trial data.
    • Think about what projects to migrate, and if there are any that you don't need that could be removed prior to migrating. In general, unused projects and issues are a great thing to clean up, since they impact performance as well as impact the time you need to spend managing them.
  • Some customers choose to delete all their data and migrate only configuration and empty project containers. This may be a good option for you if you're planning to start fresh in cloud but would like the same configuration you have in server.
  • Learn more great tips and tricks on cleaning up Jira from one of our Community leaders.
  • There are also some third-party apps you may want to use, like Optimizer for Jira, that can help you assess current usage and clean up your system.

For Confluence

  • Consider removing or leaving behind anything that hasn't been used recently. This could include specific pages, entire spaces, attachments, or apps.
  • If you're migrating from Confluence Data Center or a large server site, you may want to test your migration on some of your larger spaces that have lots of comments or attachments. 
  • You many want to search on Marketplace for third-party apps that can help you audit usage and identify what can be cleaned up. 

Step 2: Sign up for your cloud site

If you haven’t already, now’s the time to activate your free extended cloud trial and sign up for your cloud site.

Tips for choosing your cloud URL

The format for your site name (URL) 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 would prefer a separate testing and staging environment, there are a few other ways to set this up which you can learn about here.

(Optional) Step 3: Set up Atlassian Access

Atlassian Access offers cloud security and user management features including SAML SSO, user provisioning (SCIM), enforced two-factor authentication and audit logs. It works across all your Atlassian cloud products and domains so you can manage users and security policies in one simple place. 

If you're planning to use Atlassian Access in cloud, you can sign up for a 30-day free trial before beginning your test migration to get SSO set up for all users and test out user provisioning and audit logging. If you need more than 30 days, just let us know.

Step 4: Perform the test migration

Now, you're ready to migrate.

For Jira

  1. Follow the instructions outlined in Migrate from Jira Server to Jira Cloud to import your data.
  2. After migrating your data, migrate or install any apps you're planning to use in cloud. 

If you need to re-test your migration, a Jira site import will wipe all existing content, including any previously imported Jira data or data that exists on your cloud site. This means that data from any prior test migrations will be wiped automatically, so if you're testing multiple times, you won't need to delete data first.

For Confluence

  1. Follow the instructions outlined in Confluence Cloud Migration Assistant to import your data. 
  2. After migrating your data, migrate or install any apps you're planning to use in cloud. 

If you need to test your migration multiple times, you'll need to manually delete any data you're planning to re-import. This is because the migration assistant does not currently overwrite data that already exists in your cloud site. There are two ways to delete your data:

  1. Delete all data from your Confluence Cloud site
  2. Delete an individual space.

After deleting the data, you can re-run your test migration.

Step 5: Review your data and conduct User Acceptance Testing (UAT)

After migrating, review your cloud site to validate that everything is working as expected. 

In general

  • Check that your links to other content are working, for example, Confluence pages linked to Jira issues.
  • Application links to other server products may need to be reconfigured. If this is the case, after re-configuring them, re-test the functionality to ensure the integration works as expected. 
  • Check that any apps or app data you've migrated is working as expected.
  • Test integrations with other products, like Jira, Confluence, or Bitbucket.
  • Take screenshots and document changes between your server and cloud sites for any training or communications you plan to deliver during the migration and post-launch.

For Jira

  • Check that your workflows are working as expected. You may, for example, have post functions that rely on third-party apps that aren't migrated. You may find they aren't working in cloud but continue to work on your server site. 
  • Try using the product and creating test data. Test things like creating a new project, creating and editing issues, and uploading attachments.
  • Run the Jira macro repair and verify whether it fixed any broken macros.

For Confluence

  • Check that your attachments have imported correctly.
  • Check that any apps or app data you've migrated is working as expected. Any macros that rely on third-party apps may be broken, for example, Gliffy Diagrams. If this is the case, check with the app vendor if it's possible to fix them.

UAT and change management best practices

Why conduct User Acceptance Testing?

We also advise conducting UAT, or having some end users replicate common day to day tasks using the test site. This will not only help you catch any unexpected issues but can help your organization prepare for change.

Who should you involve?

This varies for every organization, but a few options to consider include testing with include:

  • Members of a specific team
  • A combination of power-users and less frequent users
  • An appointed member of each team that will be moving to your cloud site

Consider as well who has the bandwidth and ability to provide clear and constructive feedback. Generally speaking, you want to ensure that every major user type or role that will be using your cloud site is invited to provide input.

What should you test for?

Take note of any issues usershave as they get used to the things that may change as a result of your migration, including:

  • 新機能
  • A new user interface
  • Different apps
  • New URLs and changing bookmarks
  • Differences in user administration

Product-specific recommendations:

  • For Jira Software and Jira Core: Test things like creating sprints, adding issues to backlogs, and viewing boards.
  • For Jira Service Desk: Ask agents to view queues, check their portal view, and any other common activities.
  • For Confluence: Have users try creating a new space, creating and editing pages, and uploading attachments.

Record any areas of confusion or changes to functionality, since you may want to include these in any pre-launch or onboarding communications and training you provide. 

(Optional) Step 6: Reset your test site

In some cases, you may need to delete the data from your cloud site and start again – for example, if you used your production instance to test, or need to re-run your tests.

To delete all of the data from your cloud site and reset it to the default settings, you can follow the instructions here

Step 7: Create your migration runbook

Migration runbooks are a step-by-step procedural guide for what you need to do to complete your migration. Creating one can help your production migration run smoothly and according to plan.

Your runbook should include things like each step in the process, any instructions needed for those steps, who will complete them, and how long they’re expected to take.

Step 8: Develop your change-boarding and launch plan

After testing, you should have a good idea of what major changes your users can expect as a result of your move. Now's the time to prepare any training, documentation or communications your users will need to get back to work quickly. 

Keep in mind as you put this together you'll want to highlight not only what's changing, but why – as well as how your users will benefit from the move.

Some common benefits for users include:

  • Access to free cloud mobile apps
  • No more VPN! Take work anywhere, and access it quickly and securely
  • Better integration with other SaaS tools and cloud apps



最終更新日 2019 年 9 月 13 日


Powered by Confluence and Scroll Viewport.