• Products
  • Documentation
  • Resources

Determine your user migration strategy

This guide outlines the methods to migrate your users from Jira and Confluence Server or Data Center to Cloud.

The best way to import your users and groups will depend on:  

Before you begin

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

Changes to the Cloud organization

We’re continuing to roll out changes that may affect your migration experience. From your organization at admin.atlassian.com, if the Users list and Groups list are under the Directory tab, you have the improved user management experience. This means that the users and groups across sites will be merged under the organization. Read more about how groups and permissions are migrated. If you have any concerns, contact support.

A diagram of an new admin.atlassian.com view that shows a new Directory tab instead of Users and Groups

Jira user migration strategies

Your Jira user migration strategy depends on whether:

  • you are using the Jira Cloud Migration Assistant

  • you are using Site Import

Migrate Jira users with the Jira Cloud Migration Assistant

Using the Jira Cloud Migration Assistant, you can:

  • migrate users related to the projects you select to migrate, or

  • migrate all users from active internal and external directories without any project data

For Jira Service Management, the migration assistant can migrate customer accounts related to selected projects or migrate all customer accounts without any project data.

If you have external directory users, you must first sync external directory users to Jira before migrating.

Jira Cloud Migration Assistant migrates users from inactive directories if they’re referenced in projects. These users will be migrated without personal information and will appear as Former user.

Jira Cloud Migration Assistant creates a new Atlassian account for each user and associates them to 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. Learn more about migrating users and groups with the Jira Cloud Migration Assistant.

If you can't use the Jira Cloud Migration Assistant to migrate all data, consider using it to migrate 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. Learn how to use the Jira Cloud Migration Assistant

Migrate Jira users with Jira Cloud Site Import

Jira cloud Site Import migrates only users managed in Jira’s internal directory. If users are managed by external directories such as LDAP, ADFS, or Crowd, you’ll need to use the Jira Cloud Migration Assistant.

You can’t migrate a subset of users and groups using Site Import.

Learn how to use the Jira Cloud Site Import

Confluence user migration strategies

Using the Confluence Cloud Migration Assistant, you can:

  • migrate users related to the spaces you select to migrate, or

  • migrate all users from active internal and external directories without migrating any spaces

If you have external directory users, you must first sync the external users to Confluence’s internal active directory before migrating.

The Confluence Cloud Migration Assistant creates a new Atlassian account for each user and associates them to 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. See the Users and groups section in the Confluence Cloud Migration Assistant page to learn more about migrating users and groups.

Migrate both Jira and Confluence

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

Depending on the Jira products or external directories you have, you may need to use the Jira cloud Site Import. Check the Jira user migration strategies section above to see which method is suitable for you.

We recommend that you migrate all Jira users and data using the most suitable methods mentioned above, and then migrate your Confluence users and spaces.

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

Atlassian Access recommendations

If you're planning to subscribe to Atlassian Access for advanced user management features, including SAML single sign-on (SSO) and System for Cross-domain Identity Management (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

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.

If you're planning to migrate both Confluence and Jira and you need to connect SCIM, we recommend migrating Jira first, and 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.

To migrate you will need to:

  1. 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.

  2. Resolve group conflicts before syncing
    You may run into group conflicts when syncing your external identity provider with your Atlassian organization. When you sync, we’ll warn you about duplicate group names between your external identity provider and your Atlassian organization. You’ll be able to accept or reject changes to group members before you sync those groups. Learn more about resolving group conflicts before syncing.

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

More information and support

We have a number of channels available to help you with your migration.

Additional Help