Migration Planning

Plan licenses, domains, user mapping, timing and team roles before you migrate.

A little planning avoids the two most common surprises: running out of licenses at discovery, and groups arriving without their members because users weren't mapped.

1. Work out how many licenses you need

Each source group you migrate uses one license. Licenses come from the plan of the workspace owner, and are shared across every workspace that person owns.

A group uses its license the first time either of these happens:

  • At discovery: its owners and Exchange settings are read. With a plan, this happens automatically after discovery for as many groups as you have licenses free, in the order they were discovered.
  • At migration: it's migrated without having used a license yet. This includes an attempt that fails.

After that, the group never uses another license. You can rediscover it, rerun Pre-Stage and run Cutover for free.

Things that don't give licenses back:

  • Deleting a group from the discovered list
  • Deleting directory data

Deleting the whole workspace does give its licenses back.

Tip

If your source has more groups than your plan covers, don't tick every domain at discovery. Discover only the domains you're migrating, so licenses go to the groups you want.

Plans and limits are on Billing and Licenses.

2. Choose your domains

You choose two kinds of domain:

  • Source domains (at discovery). Only groups with an email address on a ticked domain are discovered.
  • Target domain (on the Configure tab). The domain groups get their address on during Pre-Stage. It must already be verified in the target tenant, so it's usually a domain the target organization already uses. The list hides .onmicrosoft.com domains unless one is the tenant's default.

At Cutover, groups switch back to their original source domain. You must have moved that domain to the target tenant and verified it there first. For Cutover, choose the same target domain you used for Pre-Stage, so Primera Labs can find the Pre-Staged groups.

3. Get the target users ready

Primera Labs adds members and owners as existing users in the target tenant. It doesn't create users. Before you migrate:

  • Create or migrate the user accounts in the target tenant.
  • Map every source member and owner to a target user. See User Mapping.

Important

Pay special attention to owners. A group whose owner isn't mapped is created without that owner. If your groups are owned by a service account you're not migrating, map it to the account that should own them in the target.

4. Plan the timeline

A typical timeline:

  1. Set up and test. Create the workspace, run Pre-Migration Checks, and migrate a few test groups with Pre-Stage.
  2. Pre-Stage everything. Run Pre-Stage for all groups. Rerun it closer to the cutover date to pick up new members.
  3. Move the email domain. Move the domain to the target tenant and verify it there. This happens in Microsoft 365, outside Primera Labs.
  4. Cutover. Run Cutover for the same groups to switch their primary addresses back to the original domain.
  5. Check. Review Completed with notes and Failed groups on the job, fix the causes, and rerun those groups.

The migration itself is quick: 250 groups take about 20 to 25 minutes. Including setup, discovery, user mapping and planning, the whole project typically takes less than 2 hours, plus the time it takes you to move your email domain.

Allow for these waits:

  • Directory role assignments can take up to an hour to take effect after setup.
  • The first job in a while can take a few minutes to start while the migration service starts up.

5. Decide who does what

Invite your project team to the workspace and give each person the lowest role that lets them do their part:

  • Admin: manages the workspace connection and the team
  • Operator: discovers groups, maps users and runs migrations
  • Reporter: read-only, for stakeholders who only need to follow progress

See Team and Roles.

6. Know what needs manual follow-up

Some things aren't copied and need a plan of their own:

  • Send As permissions
  • Nested groups and mail contacts as members
  • Membership rules of dynamic distribution lists
  • Members removed from a source group after Pre-Stage. Reruns add members but never remove them.

See the full list in Running a Migration.