Running a Migration
Discover distribution groups, configure the migration, run Pre-Stage and Cutover jobs, and read the results.
You run migrations from the Distribution Groups page. It has three tabs: Select Groups, Configure and Migrate.
Before you start, make sure your workspace is set up and selected in the header. See Workspace Setup and Pre-Migration Checks.
Select Groups: discover your groups
- Click Discover Groups. Primera Labs lists the verified domains in the source tenant.
- Under Select Domains to Discover, tick the domains whose groups you want. A group is found if its primary address or any of its other email addresses is on a ticked domain.
- Click Discover Groups.
Primera Labs reads each group's members and owners from Microsoft Graph. It also adds every member and owner to User Mapping so you can match them to target users.
Discovering again replaces the earlier results for the domains you tick.
Owners and Exchange settings
After discovery, a background job reads each group's owners and Exchange settings from the source tenant. A progress panel shows how far it has got, and you can keep working while it runs.
This step needs a plan. Each group read this way uses one license, so discovering 300 groups on a 50-group plan uses all 50 licenses straight away. Groups without a license show License required to read Exchange settings. Their settings are read when you migrate them instead, if you have licenses free by then. See Migration Planning.
Click a group to see what was read: owners, hidden from the address list, internal senders only, accept messages only from, send on behalf, moderation, and join and leave approval.
Managing the list
- Use the search box to filter the list.
- Select All selects every group currently shown.
- Delete Selected removes groups from this list only. It doesn't touch the source tenant, and it doesn't give back the licenses those groups used.
When you've selected the groups to migrate, click Continue to Configure.
Configure: choose how to migrate
- Target Domain. The domain the groups get their email address on in the target tenant. The list shows the target tenant's verified domains.
- Job Name (Optional). If you leave it blank, the job is named after the current UTC time.
- Migration Type. Pre-Stage Migration or Cutover Migration. See below.
- Preserve Owners. Copy owners to the new groups. On by default.
- Preserve Members. Copy members to the new groups. On by default.
Click Save Configuration. The settings are saved to the workspace and the Migrate tab opens.
Pre-Stage Migration
Use Pre-Stage before you move your email domain. For each group:
- If the group doesn't exist in the target yet, Primera Labs creates a distribution group with the same display name, alias and description, and the address
alias@target-domain. It then adds owners and members and applies the Exchange settings. - If the group already exists (from an earlier Pre-Stage run), Primera Labs adds any mapped members who aren't in it yet, sets the mapped owners, and applies the Exchange settings again.
So you can rerun Pre-Stage as often as you need to pick up changes in the source.
Important
A rerun only adds members: anyone removed from the source group is not removed from the target group.
Cutover Migration
Use Cutover after your email domain has moved to the target tenant and is verified there. Choose the same Target Domain you used for Pre-Stage.
For each group, Primera Labs finds the Pre-Staged group and:
- Changes its primary address to the group's original address on the source domain
- Keeps the Pre-Stage address as an alias
- Adds the source group's other email addresses as aliases
Warning
Cutover fails for a group if the original domain isn't verified in the target tenant yet.
Migrate: start the job
The Migration Summary shows the job name, how many groups and members are included, the target domain and the migration type. Click Start Migration.
Before the job is queued, Primera Labs checks that the workspace owner has an active plan with enough licenses, and that it can sign in to the target tenant.
While the job runs
The job runs in the background, so you can leave the page. It goes through these steps:
- Queued
- Discovering Exchange properties: only for groups whose owners and settings weren't read at discovery
- Migrating groups
- Cleaning up
Each job starts its own migration service to run Exchange Online commands. On a first run this can take a few minutes, and the job shows Waiting for the migration service to start. It continues automatically. If the service hasn't started after 60 minutes, the remaining groups fail and you can run them again.
Cancelling
Click Cancel on the job. It stops before the next group. Groups that were already migrated stay migrated.
Reading the results
When the job finishes, it shows Migration completed, Migration completed with errors, Migration failed or Migration cancelled, plus how many groups succeeded, failed or were skipped. A job only counts as failed if every group in it failed.
Groups are listed under:
- Migrated: done, with the group's new address.
- Completed with notes: done, but something was skipped. For example:
Group already exists - 5/7 members synced; 2 unmapped. - Failed: not migrated, with the error. See Troubleshooting.
To see a job later, go to Migration Jobs and click Details. The page has All Jobs, Active, Completed and Failed tabs, and updates while jobs are running. Migration History lists finished jobs with search and filters.
On those pages, a Pre-Stage job is labelled Incremental and a Cutover job is labelled Full Migration.
What is and isn't copied
Copied:
- Display name, alias and description
- Members and owners, through user mappings
- Hidden from the global address list
- Internal senders only, and accept messages only from
- Send on behalf
- Moderation: on or off, moderators, who bypasses moderation, and moderation notifications
- Join and leave approval
- At Cutover: the source group's email addresses, as aliases
People named in owners, send on behalf, accept-from or moderation settings are matched to target users by UPN, email or display name. Anyone who can't be matched is left out and listed in the group's note. If Exchange rejects one setting, that setting is skipped and the rest are still applied.
Not copied:
- Members who aren't mapped to a target user. They're skipped and counted in the note.
- Nested groups and mail contacts as members
- Send As permissions
- Membership rules of dynamic distribution lists
Primera Labs never deletes groups and never removes members, in either tenant.
Other group types
- Dynamic DLs. The group is created in the target with its name, alias and address, but without its membership rule, owners or members. Recreate the rule in the target tenant after migrating.
- Security Groups. This page doesn't currently migrate groups reliably. Please email support@primeralabs.tech before planning a security group migration.
- Microsoft 365 groups and mail-enabled security groups are not supported.
Was this page helpful?
Something wrong or out of date?