nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Migrate Jira user from server to Jira cloud

Tran Tien dung

I'm preparing for migration Jira server to cloud. Currently, I'm using Crowd and have some "Microsoft Active Directory", "Delegated authentication directory" directories that I don't know how to migrate users from this directories to Jira cloud? Is it possible to migrate them to Jira internal user first, then migrate to cloud?

Accepted answers

Daniel Eads

Hi Tran,

If you:

Have exposed these users to Jira in Crowd
Have the Crowd directory set to Active in Jira

then the migration assistant will try to migrate active users during the process. Once the migration starts running, the assistant will provide a count of how many users it is attempting to import into Cloud.

Hope that helps, and happy to answer more questions.

Cheers,
Daniel | Atlassian Support

All comments

Daniel Eads

Hi Tran,

If you:

Have exposed these users to Jira in Crowd
Have the Crowd directory set to Active in Jira

Hope that helps, and happy to answer more questions.

Cheers,
Daniel | Atlassian Support

Tran Tien dung

Hi Daniel,

Yes, both the condition is fullfill. But the user is sync from on-premise Active Directory(AD) to Crowd, I can imagine that Jira cloud will have no connectivity to AD servers, so how the AD user can login to Jira cloud after migrated?

Daniel Eads

Hi Tran,

For clarity, the migration will import the user settings (Name, email address, Jira groups they're a member of, Jira permissions) to Cloud. When the import is complete, users will be sent an invitation email to the site. If they don't already have an Atlassian ID associated with that email address, the invite will create an Atlassian ID (Cloud) for them. They will use a separate password, or be asked to create a new one.

What it does not do is try to authenticate back to Active Directory. If you're looking to maintain authentication to local servers using passwords your users already have set up, you'll need to use SAML and Atlassian Access - our security & identity solution for Cloud. Your Active Directory farm will need to be exposed as a SAML provider - ADFS (Active Directory Federation Services) is the way to do this with an on-premise AD. You could also use something like Okta, or even go with Azure AD if you're migrating your Windows infrastructure into Azure. Alternatively, G Suite can be used for authentication with Atlassian Cloud. G Suite has an on-site AD sync tool and can also keep the G Suite account passwords in sync with your local AD passwords.

Atlassian Cloud can't connect AD directly as an LDAP service. It must use a SAML-enabled proxy (ADFS, Okta, Azure AD) via Atlassian Access, or you can opt to use G Suite authentication and have G Suite sync with your AD.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-cloud

jira-software-server

crowd

active-directory

atl-anon

migration-customer-care