Few things: 1. Check for duplicates - check if any issues in cloud already exist in server 2. Migrate and merge - if there are some duplicates, migrate server issues and do the merging 3. Consider renaming the projects 4. Inform users - your users should know about this
You can do several things: 1. Identify duplicate emails - you can use the migration assessment in server to see if there are duplicates 2. Update email addresses - before migration make sure to update the email addresses to avoid the conflicts 3. Merge users - you can merge the migrated user with the existing user Disadvantages: - Migrated user loses their independent login for cloud -Possible manual update for user groups or permissions
Would it be the same or similar with DC -> Cloud migration?
No changes at all as far as I know.
what if we have the same project created in the cloud with some issues in it. what is the best practice in this scenario?
Few things:
1. Check for duplicates - check if any issues in cloud already exist in server
2. Migrate and merge - if there are some duplicates, migrate server issues and do the merging
3. Consider renaming the projects
4. Inform users - your users should know about this
what if we have same user with same unique email address existed in cloud before the migration?
You can do several things:
1. Identify duplicate emails - you can use the migration assessment in server to see if there are duplicates
2. Update email addresses - before migration make sure to update the email addresses to avoid the conflicts
3. Merge users - you can merge the migrated user with the existing user
Disadvantages:
- Migrated user loses their independent login for cloud
-Possible manual update for user groups or permissions