Yes, but it takes the right approach and the right tooling. The biggest mistake people make is treating tenant-to-tenant migration as a single "big bang" event where everyone loses access while data moves over. That approach almost always leads to frustrated users, missed deadlines, and support tickets piling up.

The key to a low-disruption migration is running incremental or delta syncs instead of one massive transfer. This means the bulk of the data gets copied over first while users continue working in their source tenant, and only the changes made since the last sync get picked up in subsequent passes. The final cutover then only needs to move a small delta of recent changes, which shrinks the actual "downtime window" to minutes or hours instead of days.

Communication also matters more than people expect. Even with zero technical downtime, users need to know when their sign-in credentials, file paths, or sharing links might change, so a short heads-up goes a long way in avoiding confusion post-migration.

For the technical side, we relied on the DRS Softech Tenant to Tenant Migration tool, which supports delta migrations specifically designed to minimize disruption. Permissions, versions, and metadata stayed intact throughout, and users barely noticed anything changing until the final cutover happened.

If you're planning something similar, prioritize a tool that supports incremental syncs over full-batch transfers, and don't skip the validation step before your final switch.