Home > Microsoft Entra ID Migration
Export to PDFMicrosoft Entra ID migration supports migrating from/to the following tenants:
Refer to the table below to view the supported object types in Microsoft Entra ID migrations:
√ – Supported; × – Unsupported.
| Object Type | Support Status | Comment |
|---|---|---|
| Microsoft 365 user | √ | |
| Guest user | √ | |
| Shared mailbox user | Partially supported | New shared mailbox users cannot be created in the destination during migration. However, shared mailbox users can be migrated if they already exist in the destination. |
| Security group | √ | |
| Teams & Microsoft 365 groups | × | Microsoft Entra ID does not support the migration of Teams & Microsoft 365 groups for the time being. It is recommended to use the migration of Microsoft Teams or Microsoft 365 Groups. |
| Distribution list | × | Microsoft Entra ID does not support the migration of Distribution list for the time being. It is recommended to use the migration of Exchange Online. |
| Mail-enabled security group | × | Microsoft Entra ID does not support the migration of Mail-enabled security group for the time being. It is recommended to use the migration of Exchange Online. |
Refer to the table below to view the supported and unsupported object types for users:
√ – Supported; × – Unsupported.
| Object Type | Support Status | Comment |
|---|---|---|
| Display name | √ | |
| Photo | Partially supported | User photo migration is not supported for newly created users during migration. After a user is created, you need to wait for approximately 30 minutes before running a full migration job to migrate the user photo. |
| First name | √ | |
| Last name | √ | |
| User principal name | √ | |
| User type | √ | |
| Authorization info | √ | |
| Job title | √ | |
| Company name | √ | |
| Department | √ | |
| Employee ID | √ | |
| Employee type | √ | |
| Employee hire date | √ | |
| Office location | √ | |
| Manager | √ | |
| Sponsors | √ | |
| Street address | √ | |
| City | √ | |
| State or province | √ | |
| ZIP or postal code | √ | |
| Country or region | √ | |
| Business phone | √ | |
| Mobile phone | √ | |
| √ | ||
| Other emails | √ | |
| Fax number | √ | |
| Mail nickname | √ | |
| Age group | √ | |
| Consent provided for minor | √ | |
| Account enabled | √ | |
| Usage location | √ | |
| Manage groups | × | |
| Build in roles | Partially Supported | Start time and End time are not supported for Build in roles. |
| Custom roles | Partially Supported | Custom roles with Directory, Group, User type can be migrated. Start time and End time are not supported for Build in roles. |
| Product license | √ | |
| Apps | √ | |
| Password | × | User migration does not synchronize end-user passwords as part of the data migration process. The migration administrator will need to reset or synchronize end-user passwords from the source tenant to the target tenant using native Microsoft 365 tools or third-party Single Sign-On tools. |
Refer to the table below to view the supported and unsupported object types for security groups:
√ – Supported; × – Unsupported.
| Object Type | Support Status | Comment |
|---|---|---|
| Name | √ | |
| Description | √ | |
| Group type | √ | |
| Membership type | √ | |
| Microsoft Entra roles can be assigned to the group | √ | |
| Dynamic membership rules | √ | |
| Build in roles | √ | |
| Custom roles | √ | |
| Owners | √ | |
| Members | √ |