Things to You Need to Know About Tenant to Tenant Migration

Advertisement

Migration projects often result from mergers, acquisitions, or sales. If you’re considering starting a migration, or are in the process of migrating from Office 365 to Office 365, you might not know where to start. Fortunately, such a transition is not as complicated as it looks.

Migrating from Office 365 to Office 365 differs from migrating from another platform to Office 365 in several key ways, so you need to understand the process before you begin your migration project.

Advertisement

Why migrate from one O365 tenant to another?

Office 365 is now very mature on the market and has been used by many companies for a long time. In a natural business cycle, companies merge or acquire other companies or sell start-up companies. That way we see a lot of Migration from tenant to tenant projects.

For example, company X (on O365) wants to acquire company Y (also on O365) and integrate all IT systems. Alternatively, Company M (on O365) would have to sell the business entity that would be Company N (set up on O365) and move Company N’s users, data and domains to their own tenant.

Advertisement

Since both entities are on the same platform, so O365-just switch to background and everything will be migrated. Unfortunately this is not the case. Migrating from one O365 tenant to another is a complete migration project, similar to migrating domains, users, mailboxes and file content from your on-premises system to O365.

The more services you use with O365 like SharePoint, the more complicated it gets. Because of this, companies need some expertise to work with them to provide services such as Migrate SharePoint from one tenant to another tenant for the smooth running of the migration without complications.

Advertisement

Complications of Office 365 to Office 365 migrations

Additionally, there are very important aspects that make Office 365 to Office 365 migration more difficult than on-premises to Office 365 migration. The domain you are migrating must only exist on one O365 client.

If you are currently using a domain with O365 Tenant X and want to migrate that domain, mailbox or user to O365 Tenant Y, delete or rename all objects before adding the domain to Tenant Y. You need to remove the domain for tenant X (e.g. mailboxes, user accounts, O365 groups using this domain from tenant X, etc.) and let the O365 platform recognize that the domain is not associated with any tenant. You can wait and then add them to Tenant Y to create an object in that domain.

Advertisement

For mailbox and user migration, use wildcard names to create users and mailboxes in the target tenant (that is, without the domain to be migrated) while the users continue to work. Use the tool to copy the contents of the mailbox to the source tenant. During the transition, all objects on the source tenant are renamed and no longer point to the domain to be migrated, the domain is removed and then added to the target tenant. At this point, objects with placeholder names (users, mailboxes, etc.) are renamed to the same names used by the source tenant.

Conclusion:

If you don’t have sufficient knowledge about migration and don’t have a dedicated IT team to support you in the migration process, let Apps4Rent do it for you. They are experts in providing various services such as Windows 10 Azure virtual desktop and also make sure your O365 migration is complete.

Advertisement