Server to Cloud Migration with Access

[Keith Zenoz]

I migrated both our Jira and Confluence test environments (server) to a Cloud trial and also activated a trial for Access and things have gone pretty well (loving SSO). I migrated all users & groups from Jira, preserving group membership. For Confluence I did not since those users should already exist from the Jira migration. I bolted on Access for SSO and all usernames should be the same email from our server instance and Access anyways. My questions:

1. I want to preserve group membership, but I don't see the need to migrate users if I'll be bolting on Access anyways. But there's no choice to just migrate groups and group membership. Am I missing something?
2. When it comes time to migrate production, it would be nice to keep all of our Access cloud settings and just blow away the data like groups, projects/issues and do fresh migration from production. Is that possible?

Our environment -

Jira
Groups - 29
Users - 86
Projects - 220 (6245 issues - 224MB)
Apps - 10


Confluence
Groups - 69
Users - 204
Spaces - 48 (1950 pages - 839MB)
Apps- 4

Thanks

[Boris Berenberg - Atlas Authority]

Hi Keith,

You will want to involve Atlassian Support in the changes you're requesting. If you need help beyond what they can offer, you can contact us at https://atlasauthority.com/contact-us/

[SriKumar P]

Hi @Keith Zenoz ,

Just a few question from our end to understand how you are migrating Jira and Confluence:

Are you using the Migration assistance plugin to migrate or the Site import functionality?

If you are using Migration assistance, you can choose to migrate users and group however if the users and groups are already present on the cloud site then the assistance will not reimport it will skip them and only add missing users.

If you are using Site import function you can choose merger user option that will preserve users and group that is there on the cloud site.

One thing to note when you have Atlassian access enabled is during migration it is recommended to disable user provisioning during migration and re-enable it after migration as we have a known issue : [https://jira.atlassian.com/browse/ACCESS-653|https://jira.atlassian.com/browse/ACCESS-653] 

Kind Regards, 

Sri Kumar
Atlassian Support