I’ve been looking into Microsoft 365 tenant-to-tenant migrations and one lesson is clear: the migration tool itself isn’t the only consideration. Microsoft lists prerequisites around licensing, identity mapping, permissions, tenant preparation, and workload-specific limitations.

For example, Microsoft’s current Exchange cross-tenant documentation notes that users have to be properly prepared in the target tenant, and certain mailbox conditions can prevent migration.

If using a third-party solution, I’d therefore want visibility rather than a simple “Start” button. DRS Softech’s tool provides real-time task monitoring and detailed reports so administrators can review successful transfers, skipped data, failures, timestamps, and completion status.

Security is another important part. The tool supports Modern Authentication, Azure App Registration/Admin Impersonation, MFA, and Microsoft Graph API permissions. Its Graph-based architecture is intended to access Exchange Online, SharePoint Online, and OneDrive directly while preserving folder hierarchy and relevant metadata.

There’s also a free demo that allows up to 500 emails per folder, 100 contacts, and 100 calendar items per selected user, while SharePoint and OneDrive can be previewed with demo limitations.

What checks do you consider mandatory before starting a production tenant-to-tenant migration?