Consider, on the source domain there is a group named support@domainmigration.info having 6 members in it. 


Source Group : support@domainmigration.info

Members :

  1. adam@domainmigration.info

  2. kevin@domainmigration.info

  3. jake@domainmigration.info

  4. helen@domainmigration.info

  5. matt@netprem.com

  6. koushik@syscloud.com


Out of the 6 users 4 are from the source domain vopak.com & 2 are from an external domain. Out of the 4 VoPak users, only 2 users are in the migration list 

( adam@domainmigration.info => adamjohnson@securemigration.info),

( helen@domainmigration.info => helengeorge@securemigration.info ).


Now, when we migrate the group, a group named support@securemigration.info will be created at the destination domain with the following users.


Destination Group : support@securemigration.info

Members :

  1. adamjohnson@securemigration.info

  2. kevin@securemigration.info

  3. jake@securemigration.info

  4. helengeorge@securemigration.info

  5. matt@netprem.com

  6. koushik@syscloud.com


As you can see above, the users who are migrating have been mapped correctly into the group. The non-migrating users have just their domain replaced with their usernames. The external domain users are retained as same.



Case 1: What if a group named support@securemigration.info is already present with some users are present in the group?

Answer: The groups will be merged, the users will be merged into it.


Case 2: What if the email support@securemigration.info of the group is already assigned to a user at the destination?

Answer: In this case, we can't migrate the group. Because, when trying to migrate the group support@domainmigration.info, we try to create a group support@securemigration.info at the destination. Then, Google will provide a error that we can't create a group with that name since it has been already taken by a user in the destination domain.