Space migration issues on confluence

[SaravanaKumar]

We are planning to migrate to confluence server to cloud

We come across a situation where we already have a cloud site. Our users have different names and mail addresses in both the server and cloud due to the company merge. So we planned to migrate only the spaces and not the users to avoid user redundancy since our users are already configured with other names in the cloud. In that case, we have a few questions

1. When only spaces are migrated does it brings any space permission issues or the new spaces become open/public?

2.What happens to the personal spaces when migrated,do the personal spaces becomes public?

3.When a space with the same name exists in both in server and cloud do it adds the pages  or do it deletes all the pages in the cloud and adds only the server pages?

4.Do u have a better plan for migrating this kind of scenario where the same users have different name and email id in server and cloud?

[Kerli Loopman]

I am not 100% certain on my answer but I believe and remember from my migration that: 

1. Space permissions will be the same after migration. Private spaces will remain private and public will be public. You should check group and user permissions after migration.

2. I don't think personal spaces will become public. If you have a lot of important personal spaces, I think you can edit their permissions in cloud after migration so their owners old account would be replaced with new one or maybe it is possible to move articles from old users space to new user space as an administrator. 

3. I am not sure about that but maybe the migration tool asks you to change the name. I didn't have any name conflicts of projects and spaces at my migration but the migration tool said, that it checked the names. Maybe it prompts you to change something before migration. I don't think it overwrites. Some things (jira workflow statuses that had same name but different category for example) that names conflicted during migration, their names had "Migrated" added to their names after migration.

4. Not a better plan actually but my experience. Our employees had the same email addresses so I didn't have that problem but some partner accounts were in the old instance with their companies emails and in Cloud instance we created new emails with our domain for them so after I just checked and replaced all permissions from their old account to new account and Bulk edited all active tasks to their name and anything other related to their account. But in my case, this was mostly in Jira not that much in Confluence because in Confluence I think you can not change the name who created page. You just have to check they have all the certain permissions with new account.