In the near future my company plans on moving one Jira Cloud instance (2 projects) into another (currently under Enterprise so both are accessible in Atlassian administration but under separate names). We want our customers to be impacted as little as possible with the transition. Here are our plans with my questions:
1. We plan on recreating most of the custom fields. We have some cleanup to do and want to make sure the field names are distinct from the other projects within the combined instance.
2. I have several forms that were created and connected to custom fields. Can these forms be moved to the new instance and the connections to the custom fields be made after the new fields are created?
3. Although in Atlassian Admin I can see both sites, the instances are separate and we do not have SSO for login. Some users may have an account on both sites, some on only what will become the obsolete site. Is there a way to copy user data from one instance to another so they will not have to create a new login? Would I have to merge the portal accounts into an Atlassian account then move it to the other portal/instance?
4. What is the best way to redirect users to the new portal? Would this be done in the product URL to redirect or elsewhere? Can I redirect to another Jira instance currently in use? For instance, if our site is abc.atlassian.net and the other site is xyz.atlassian.net, can I redirect to the xyz.atlassian.net site or will it cause issues? Will users still using abc.atlassian.net or any current bookmarks they use still work and redirect to the new site?
5. Do automations need recreated or can they be moved over? I know since some are based on request types, user name, etc. I would have to recreate, but there are a few "legacy" automations that are not.
I should note that I am an Org admin if that makes a difference when merging.
Edited to add another question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.