Skip to main content
Question

Office 365 Tenant Migration - Reconfigure Office Suite

  • August 7, 2023
  • 4 replies
  • 241 views

amorrisuk
Forum|alt.badge.img+3

We are currently moving Microsoft 365 Tenants as part of a merger, which means one half of the new business needs the Microsoft 365 Apps to move to the new tenant. 

These devices are AD Joined but not Azure AD Joined. 

Has anyone come across a way to do this without resorting to deleting key chains, and asking users to reconfigure the Apps. 

Thanks

4 replies

AJPinto
Forum|alt.badge.img+26
  • Legendary Contributor
  • August 8, 2023

Microsoft does provide a license removal tool, users would need to log back in to office when its used as you seem to have noticed. I suggest bringing this up on your next TUB. Microsoft will need to provide guidance but I don't think there is another way.

 

macadmins.software/tools/


Forum|alt.badge.img
  • New Contributor
  • January 29, 2025


A while ago, our IT team had to move an employee’s Office 365 account to a new tenant after a company restructuring. We needed a secure and easy way to do it manually without third-party tools. After searching online, I found the Office365Solutions.org website, and to my surprise, they had a step-by-step guide on how to perform Office365 Tenant-To-Tenant Migration. The guide explained how to transfer emails, calendars, contacts, and OneDrive files using Microsoft’s built-in tools like PowerShell. The key steps included setting up both tenants, updating permissions, modifying DNS records, and verifying data after the move. By following the guide, we successfully migrated the employee’s data with minimum time and it is totally worth it.


Forum|alt.badge.img+1
  • New Contributor
  • March 27, 2025

Migrating from one Office 365 tenant to another can be tricky, but you can do it manually by following these steps:

  1. Plan & Prepare – First, check your domain settings, create a list of users, and ensure both old and new tenants are ready.

  2. Backup Important Data – Before starting, save emails, contacts, and files to avoid losing any information.

  3. Set Up Migration – Use Microsoft’s Exchange Admin Center (EAC) or PowerShell to move mailboxes between tenants.

  4. Transfer the Domain – Remove your domain from the old tenant and set it up in the new one. Don’t forget to update DNS records.

  5. Verify Everything – After migration, check if emails, contacts, and OneDrive files are working properly in the new tenant.

This manual method works, but it requires technical skills and can take a lot of time. If you want an easier and faster way, try the DRS Softech Microsoft 365 Migration Tool. It automates the process, ensuring a smooth and secure transfer of emails, contacts, and calendars. No need for complex setups or scripts—just a few clicks and your data is migrated effortlessly.


sophiamitchell

We went through a similar Microsoft 365 tenant-to-tenant migration recently. One thing to keep in mind is that Office apps are associated with the user's Microsoft 365 account. After users are moved to the new tenant, they typically need to sign out of Office applications, remove the old work account if it's still present, and sign in with their new Microsoft 365 credentials. In some cases, the Office license also needs to be reactivated under the new tenant.

Before migrating users, it's worth planning the cutover carefully, especially if you're moving mailboxes, OneDrive, and other Microsoft 365 workloads. Running a pilot migration with a small group of users can help identify any issues before the full migration.

For the mailbox migration itself, we had a good experience using the EdbMails Office 365 Migration Tool. It supports direct tenant-to-tenant mailbox migration, preserves the mailbox structure and permissions, and supports incremental migration, which is useful if new emails arrive during the migration window.

Once the migration is complete, verify that Outlook profiles, Office activation, OneDrive sync, Teams sign-in, and Autodiscover are all pointing to the new tenant before decommissioning the old one. That extra validation helps avoid post-migration support issues.