Skip to the cards
Filed
Loans
389

Microsoft Entra ID Tenant Migration: Plan User, Group and Sign-In Readiness

Plan identity matching, group access, licenses and sign-in activation before moving Entra ID users between tenants.

Microsoft Entra ID Tenant Migration: Plan User, Group and Sign-In Readiness

A destination account can exist while its owner still lacks the access needed to work. In a Microsoft Entra ID tenant-to-tenant migration, readiness depends on more than creating or matching users: group membership, licenses, roles, guest invitations and sign-in activation each need their own decision and validation.

Bill d 150x150

AvePoint Fly provides a workflow for migrating Microsoft Entra ID users, guest users and non-mail-enabled security groups. It supports source-to-destination mappings, selected properties and assignments, and follow-up actions. The administrator’s job is to make sure the mapped identity is the right person, that the planned access reaches the destination, and that sign-in is enabled at the right point in the migration.

Those decisions also affect dependent Microsoft 365 workloads. Group and license assignments help determine what Microsoft 365 applications—and connected AI tools such as Copilot—can access for a signed-in user. A completed migration job is useful evidence of processing, but it doesn’t by itself establish that the destination account reflects the approved access design.

Define the identity migration scope

“Entra ID migration” can refer to several kinds of work. The Fly workflow discussed here covers cloud identities and selected security groups. Other Microsoft 365 objects use different workflows, so inventory them before building the project.

Objects to moveRelevant Fly workflow
Microsoft 365 users and guest usersMicrosoft Entra ID Migration
Non-mail-enabled security groupsMicrosoft Entra ID Migration
Teams and Microsoft 365 groupsMicrosoft Teams or Microsoft 365 Groups migration
Distribution lists, shared mailboxes and mail-enabled security groupsExchange Online migration

For users, supported properties include display name, user principal name (UPN), department, job title and usage location. For security groups, support includes owners, members, membership type, dynamic membership rules and supported roles. User extension attributes aren’t supported in this workflow, so identify any processes or applications that depend on them during scoping.

Build the inventory around the access and identity state the destination needs. Reproducing every source value or assignment without review can carry over choices that no longer fit the destination.

Prepare tenant connections and destination accounts

Fly connects to the source and destination Entra tenants through app profiles. Administrators can use the applicable Fly app profiles or custom profiles with the permissions required for the migration functions in scope. Connect the tenants in AvePoint Online Services, prepare those profiles, then create the source and destination Entra ID Users and Groups connections in Fly. Check the permissions against the actions the project will run.

Before mapping, decide which destination identities already exist, which need to be created, what domains will be used for matching, and whether the required Microsoft licenses are available in the destination. Create an Entra ID migration project using the prepared connections and a migration policy, then add its mappings.

If the project uses Auto map, first configure Scan Profiles and scan the source objects in AvePoint Online Services. Select the relevant source and destination domains when generating mappings. When a supported destination object is missing, Auto map presents an alert that lets the administrator approve creation or return to choose a different destination. Review this decision before building dependent migration work on the new identity.

Match identities deliberately

Imagine a fictional migration involving three employees. Alex Chen already has the intended destination account, Dana Patel needs a new destination account, and Morgan Lee’s configured attribute rule matches two destination candidates. Each case calls for a different mapping decision:

  • Map Alex’s source identity to the existing account that has been verified as Alex’s.
  • Define Dana’s intended destination identity and approve its creation through the supported workflow.
  • Resolve Morgan’s ambiguous match before migration, using an explicit mapping to the verified account where appropriate.

Fly can evaluate attribute-matching rules in order. If one rule finds no match, it tries the next. Explicit user mappings take precedence over attribute-based mappings. If the configured rules match a source object to more than one destination object, Fly fails that migration instead of choosing a candidate arbitrarily.

That failure identifies an ambiguity, but a single match isn’t proof that the business decision is correct. A rule can return one account that belongs to the wrong person. Review the identity behind each result, especially where names, domains or existing records could lead to confusion. Rerunning an unchanged ambiguous rule won’t settle which destination account is intended.

Mappings can be added manually, imported from Excel or generated through Auto map. Each method can save setup time, but the administrator still needs to review where each identity will land.

Reconcile existing accounts and group relationships

An existing destination account may already have a department, group memberships, licenses or administrative access. Decide which source properties should update it and which destination values should remain. The acceptance question is whether the resulting destination reflects the access the organization approved—not simply whether source data was copied.

Verify each security group property

A group name in the destination doesn’t confirm that the group is ready. Check membership type, dynamic membership rules, the role-assignable setting, owners and members as separate properties. For groups with static membership, confirm that the intended users exist and are mapped in the destination.

When associated users already exist in the destination, group membership can be included through the migration policy. If those identities aren’t ready yet, run the Migrate group membership post-migration action after they are available. Dynamic groups need a review of both the destination rule and the resulting membership; transferring a rule doesn’t establish that the expected people receive access.

Sequence guest invitations

Fly supports guest-user migration and an Invite guest user option with configurable invitation content and a redirect URL. Creating a guest object and sending its invitation are distinct milestones. A guest that was migrated earlier without an invitation can receive one in a later job with invitations enabled, using the existing destination account rather than creating a duplicate.

Plan when guests should be created and when they should be contacted. This lets the migration team coordinate access and communication instead of treating an invitation as proof that every account dependency is complete.

Check roles, licenses and application assignments

Fly can migrate supported directory-role assignments and assign Microsoft licenses based on a source user’s assignments. The corresponding license must exist in the destination and have available capacity. This is an assignment of destination licenses; it doesn’t transfer licenses purchased for the source tenant.

Role coverage has limits. The supported user list excludes built-in role start and end times, and lists Directory, Group and User as supported custom-role types. Check the roles in the project against those supported options rather than assuming that every privileged-access setting will be recreated.

The policy also supports enterprise-application single sign-on (SSO) assignments. Keep the scope clear: migrating an assignment doesn’t migrate the application’s configuration or validate that a user can sign in to it.

Fly has an option to assign custom security attributes to destination users based on source-user assignments. These attributes differ from the user extension attributes that aren’t supported in this workflow. Before using the option, confirm that the destination attribute definitions and required permissions are in place; don’t assume the assignment job creates those definitions. Microsoft provides an overview of custom security attributes.

Pilot the configured workflow

Once connections, policy and mappings are ready, review the project scope before execution. On the project’s mappings page, Pre-migration → Verify mapping checks whether the source and destination objects in the mappings are available for migration. Fly makes this check optional, but it is recommended before a production run. It doesn’t replace confirming the identity match or testing access.

A useful pilot can cover a new user, an existing destination user, a guest and a security group with the relationships relevant to the project. Include a supported role or application assignment if it is part of the production scope. This is a suggested set of cases, not a required Fly template.

For initial execution, use Migration → Full migration. Depending on the configured options, the job can migrate properties, group memberships, supported roles and license assignments.

ComplexityExample casePlanning work
Tier 1 – Lower complexityA new user with no existing destination account, such as DanaCreate the account with policy-defined properties and standard group membership.
Tier 2 – Moderate complexityAn existing account needing reconciliation, such as Alex, or a group with static membershipDecide which source values should update the account and confirm membership prerequisites.
Tier 3 – Higher complexityAn ambiguous match, guest invitation, dynamic group, or role, license or SSO assignmentConfirm matches, sequence invitations, review dynamic rules and check destination capacity.

Some relationships and actions need separate post-migration work:

  • Managers and sponsors: These aren’t included in the full migration job. Run Migrate object managers to migrate those relationships.
  • Group membership: Run the separate membership action if membership was deferred or must wait until destination identities exist.
  • Microsoft licenses: Use Assign Microsoft license where needed, then address any destination availability or capacity errors reported by the job.
  • Sign-in activation: Use Unblock user sign-in for mapped users whose activation is approved for that stage.

Post-migration jobs can run independently of the full migration. Review the objects selected for each action; don’t assume selections in the full-migration policy also control these jobs. The group membership action uses the attribute-mapping rules defined in the policy, so identity matching remains relevant after account creation.

Coordinate account creation with first sign-in

AvePoint Fly can block sign-in for newly created destination users, then unblock mapped users through a post-migration action. This allows teams to prepare accounts before activating them. Unblocking an account doesn’t provide credentials or complete every access requirement.

Plan activation alongside the workloads that depend on each identity. Fly’s Teams membership support notes state that a source member can’t be migrated when the corresponding destination user is blocked from signing in. For those migrations, the team needs to sequence unblocking before the dependent membership action.

The right order depends on the workload and migration wave: establish when each destination identity needs to exist, when dependent memberships can run, and when the employee should start using the destination. Coordinate the timing with the content-migration team. User communications should explain which account to use, when to switch, how destination credentials will be provided and where to ask for help.

Validate the destination, not just the job status

Fly provides mapping-level history and reports for property updates, user metadata, role assignments, memberships and licenses. Property reports can show old and new values; exceptions and comments can point to items that need attention. Use those records to investigate specific outcomes, then check the destination itself.

AvePoint’s State of AI Report 2026 says that 62% of organizations reporting the highest confidence in preventing unauthorized data access had still experienced at least one AI-related unauthorized-access incident. That finding is a reminder that confidence in a control doesn’t establish that it is working as intended; migration teams need to inspect the resulting access.

If a destination object is missing, review its mapping and provisioning configuration. If a license is unavailable, check the destination license type and remaining capacity. Rerunning a job without fixing the cause won’t resolve either problem.

For the pilot, compare reports with the approved design. Confirm that Alex maps to the intended account, Dana’s new account has the expected properties, and Morgan’s ambiguity has been resolved. Check the selected groups and assignments, then verify manager and sponsor relationships after their separate job. When activation is approved, test destination sign-in and access to the resources included in the pilot. These are recommended acceptance checks; Fly doesn’t automatically test the entire employee experience.

Export final reports and retain the mappings with the project handoff. For migrations running in several waves, review mappings before each wave. The pre-migration verification can identify source or destination objects that aren’t available, while conditions such as newly created accounts or license availability may have changed since an earlier run.

Carry identity decisions into Microsoft 365 workloads

Destination identities and mappings support dependent content work, including Teams and Microsoft 365 group memberships, file attribution, task assignments and permissions. That makes identity planning part of the broader Microsoft 365 migration. Carry approved mappings into the relevant content projects and validate them in those workloads; completing an Entra job doesn’t configure every mailbox, collaboration service or device migration that follows.

The same principle applies to Microsoft Copilot and other AI agents connected to Microsoft 365: they use the permissions and group memberships available to the signed-in identity. Missing group membership, license or role assignments can affect what the user—and connected agents acting with that user’s access—can see. Check those assignments as part of access validation.

The practical target is a set of verified destination accounts, supported properties and assignments that match the approved plan, and a clear activation sequence for each wave. That gives dependent migration work a usable identity foundation and tells the team what must be ready before people switch accounts.

https://assets.avepoint.com/upload/images/icons/Migrate-Your-Data-Confidently-with-AvePoint-Fly.jpg

Frequently asked questions

How does user migration differ from security-group migration?

User migration creates or matches a destination identity and migrates supported properties such as display name, UPN, department, job title and usage location. Security-group migration covers group properties such as membership type, dynamic rules, the role-assignable setting, owners and members. Group completeness depends on the relevant users existing and being correctly matched in the destination.

Does this workflow include mail flow, shared mailboxes or distribution lists?

No. The Entra ID workflow covers Microsoft 365 users, guest users and non-mail-enabled security groups. Distribution lists, shared mailboxes and mail-enabled security groups use the Exchange Online migration workflow. Teams and Microsoft 365 groups use the Microsoft Teams or Microsoft 365 Groups migration workflow.

How much downtime should organizations expect?

The workflow supports staged account preparation: newly created destination users can remain blocked and mapped users can be unblocked when their dependencies are ready. That can support migration waves, but the workflow doesn’t specify a fixed downtime duration. Any interruption depends on how the organization sequences its workloads and account activation.

Does the process apply to a rebrand or divestiture?

The matching, mapping and validation decisions apply whenever identities move between Entra ID tenants. The project scope may vary with the organization’s needs, but the workflow still requires teams to identify destination accounts, resolve ambiguous matches and verify access.

What happens to Teams and SharePoint after identity migration?

Destination identities and mappings underpin memberships, file attribution, task assignments and permissions in dependent workloads. Completing an Entra ID job doesn’t configure those workloads automatically. Carry mapping decisions into each relevant content project and validate them there.

How can migration affect Copilot access?

Microsoft Copilot and other AI agents connected to Microsoft 365 use the permissions and group memberships available to the signed-in user. If a destination account has an incomplete group, license or role assignment, that can affect the information available to the user and connected tools. Validate those assignments as part of the access review.

How often should mappings be checked during a multi-wave project?

Review mappings before each wave’s production run. Pre-migration → Verify mapping checks whether mapped source and destination objects are available. Destination conditions, including account creation and license capacity, can change between waves.

Can a blocked destination user be added to a migrated team?

Fly’s Teams membership support notes state that a source member can’t be migrated when the corresponding destination user is blocked from signing in. For that dependent membership work, sequence the unblock action before the membership migration.

Does SID history apply to an Entra ID tenant migration?

SID history is an Active Directory concept used to preserve old security identifiers for access to resources that still check against a previous domain. Entra ID tenant-to-tenant migration uses cloud identity matching and explicit mappings instead. Organizations moving an on-premises Active Directory domain alongside an Entra ID tenant need to plan that domain work separately.

Filed alongside