Manual migration path for User Profiles for Jira Server/Data Center to Jira Cloud
Our app User Profiles for Jira Data Center and the one for Jira Cloud have differing conceptual ideas for addressing some of the use cases. Furthermore there are technical constraints in Cloud that impede automatic migration. Therefore, we do not provide an automated migration path.
Instead, we can in all conscience recommend starting from scratch in Jira Cloud, as this can be configured very easily and quickly.
In more detail, the profile elements that a custom field shows can be grouped into two kinds, and each group can be handled differently for migration purposes:
-
Profile elements synced automatically with data coming from LDAP, configured via “Mapping for LDAP Attribute(s)”
-
Profile elements filled manually in Jira, by each user for themselves
Fields synced with user data coming from LDAP / Entra ID
The 1st kind of custom fields (using Profile elements synced automatically with data coming from LDAP) can be migrated to Cloud by manually creating an appropriate custom field in Cloud, see docu Custom field configuration | Create custom field.
Example 📝
-
Old (Data Center):
-
Field “Assignee’s Manager”
-
for reference user field: Assignee
-
using a profile element: “Manager”
-
mapped to LDAP attribute via:
%%manager%%
-
-
→ New (Cloud):
-
Create field “Assignee’s Manager”
-
for reference user field: Assignee
-
using Microsoft user attribute: “Manager”
-
Fields filled manually in Jira Data Center
For the 2nd kind of custom fields (using Profile elements filled manually in Jira), first it must be decided if their values can be moved to attributes in Microsoft Entra ID:
Yes, data can be moved to Entra ID 
Those custom fields can be migrated, like so:
-
Move data to Entra ID (out-of-scope of our app; must be done by customer)
-
Create custom field normally, as described on Custom field configuration | Create custom field
No, data cannot be moved to Entra ID 
Those custom fields cannot be migrated to User Profiles for Jira Cloud.
Differences between User Profiles for Jira Server/Data Center and Jira Cloud
Our User Profiles for Jira cloud app is still in its early stage of development. We are working on adding new features to the app. For further details regarding our plan and progress please refer to our public roadmap.
The following table gives you an overview of the current functional differences between our Server and Cloud apps.
|
Feature |
Cloud |
Server/DC |
|---|---|---|
|
Synchronize user profile elements from user directory to Jira |
|
|
|
Add user profile information manually |
|
|
|
Display profile information in Jira tickets |
|
|
|
Support of custom fields with type "User Picker" |
|
|
|
Compatible with Jira standard functions (use profile information for e. g. search, reporting, queues, automation) |
|
|
|
Integration with User Sync and SAML SSO from resolution |
|
|
|
Add user profile details for JSM customers as agent |
|
|
So, why should you go Cloud?
-
Atlassian’s end of support for Server, as of
-
Atlassian’s end of support for Data Center, see https://www.atlassian.com/licensing/data-center-end-of-life
-
The Cloud version offers easier configuration for the admins.
-
With the Cloud version, you get instant access to new feature releases and automatic upgrades, alleviating the need for manual work.
If you need more information to help you decide if moving from Server or Data Center to Cloud is a good option for you for the entire Atlassian suite, check out Atlassian Cloud Migration Center.
If you have further questions and want to get in touch with us, please Raise a support request!