移行戦略の決定

descriptionDetermine how you want to migrate your users from server to cloud using this handy guide.


This guide outlines the best method to migrate your users from Jira or Confluence Server (or Data Center) to cloud.

The best way to import your users and groups will depend on a few variables: what products you’re migrating, what order you’re migrating in, which migration method you're using, how your users and groups are currently managed in server, and if you plan to use Atlassian Access for SCIM (user provisioning).

はじめる前に

Before you decide how to migrate your users, make sure you:

It is not currently possible to migrate a subset of users and groups using the Jira and Confluence Cloud Migration Assistants or Jira site import. If you use these methods you will need to import all users and groups. Read the information below for more details.

Confluence user migration strategies

We recommend using the Confluence Cloud Migration Assistant to migrate your Confluence users.

If your users are managed by, or synced to, Confluence’s internal directory (and the directory is active), your users will be imported when you migrate your spaces with the Confluence Cloud Migration Assistant. You can also choose to migrate users only, without any spaces.

External users that are not synced to the internal directory will not be migrated.


The migration assistant will create a new Atlassian account for each user and associate them with your cloud site. They will also be assigned a password, so your users will need to reset their password the first time they sign in.

All your users' history and content will be linked to their new Atlassian account, and space permissions will remain the same.

Jira user migration strategies

There are two main strategies for migrating Jira users depending on which Jira migration method you plan to use.

Migrating Jira users with Jira Cloud Migration Assistant

This advice applies when using Jira Cloud Migration Assistant as your migration method.

If your users are managed by, or synced to, Jira’s internal directory (and the directory is active), all your users will be imported when you migrate your projects with the Jira Cloud Migration Assistant. You can also choose to migrate all users only, without any project data.

External users that are not synced to the internal directory will not be migrated.


The Jira Cloud Migration Assistant will migrate users from inactive directories only if they are referenced in project data. In this case, they will be migrated without personal information and will appear as Former user.

Jira ユーザーを Jira Cloud のサイト インポートで移行する

This advice applies when using Jira Cloud Site Import as your migration method.

ユーザーが Jira の内部ディレクトリで管理されている場合、他のデータとともに Jira のサイト インポート プロセスでインポートされるので、追加の手順は不要です。

If your users are externally managed (e.g. through LDAP, ADFS, or Crowd), the external users will not be imported. In this case, you should migrate your users to Jira’s internal directory before migrating to cloud. To do this, follow the instructions outlined in migrate users between directories or migrate from an external directory to the Jira internal user directory.

Our technical support team can help bulk import your users and groups prior to migration if you’re unable to migrate your users to Jira’s internal user directory. For instructions on how to do this, see “How to bulk import your users before migrating” below.

If you plan to use SCIM follow the instructions below.

Jira と Confluence の両方を移行する場合

When migrating both Jira and Confluence, we recommend that you use both migration assistants to migrate your users either before, or along with, your data. 

If the Jira Cloud Migration Assistant is not an option for you, you can still use Jira Site import however, you will need to migrate Jira first. This is to avoid some known issues listed at the bottom of the page.

The Jira Cloud Migration Assistant allows you to migrate all users without any projects. If you can't use the migration assistant for your data, consider using it for your users only. For example, you can migrate all your Jira users with the migration assistant first and then import your projects through Jira Site import later. You can then use the migration assistant for Confluence once your Jira data in imported. 

If you plan to use an external identity provider for SCIM user provisioning, we also recommend migrating Jira first. See the information below about Atlassian Access for more details.

Atlassian Access の推奨事項

If you're planning to subscribe to Atlassian Access for advanced user management features, including SAML single sign-on (SSO) and user provisioning (SCIM) there are a few recommendations to be aware of.

SAML SSO

If you’re planning to use SAML SSO in cloud, set this up prior to migrating. That way, users won't have to switch login experiences.

SCIM user provisioning

The process for setting up SCIM user provisioning will depend on what you’re migrating and when.

Confluence only

If you’re migrating Confluence only (and you don’t have Jira at all), we recommend that you set up SCIM before migrating your data and users with the Confluence Cloud Migration Assistant.

Jira only / Jira and Confluence

If you’re migrating Jira only (and don’t have Confluence at all), we recommend setting up SCIM after manually importing your users and before migrating your data. This is to avoid some known issues (listed below).

If you're planning to migrate both Jira and Confluence and you need to connect SCIM, we recommend migrating Jira first or not connecting SCIM until after Jira is migrated. You may encounter issues if you migrate Confluence with SCIM first and then choose to migrate Jira later. Follow the instructions below.

You will need to:

  1. Manually import your users. To manually import your users, you will need to get in touch with our technical support team so they can do it for you. See the instructions on “How to bulk import your users before migrating” below.

  2. Set up SCIM. After all your users are successfully imported to cloud, you can start syncing via user provisioning. The existing users you've already imported can become managed by your external identity provider, and you’ll be able to activate and deactivate users and sync groups from your external identity provider.

  3. Migrate your data. You can then choose to migrate your data using either of the methods above.

移行前にユーザーを一括インポートする方法

If you need the technical support team to import your users through CSV, you can follow the instructions below.

First, run the following SQL queries from your Jira Server and/or Confluence database to create CSV files of your users and groups:


ユーザー


SELECT email_address AS "email", user_name AS "username", display_name AS "displayname", active AS "active" FROM cwd_user


グループ


SELECT DISTINCT parent_name AS group, child_name AS username FROM cwd_membership;



Then, provide Atlassian's migration support team with the two CSV files to have the users and groups imported into Jira 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 Jira migrations, including their status and suggested workarounds.

次のような既知の問題があります。

詳細情報とサポート

移行をサポートする多数のチャネルをご用意しています。


最終更新日 2020 年 3 月 12 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.