For anyone who has handled a large Microsoft 365 tenant migration, how are you dealing with data that changes while the migration is already running?

Our concern is that users will continue working in the source tenant during the project. Moving everything once and then discovering that hundreds of new emails or files appeared afterward could make the final cutover messy.

I’ve been researching the DRS Softech Office 365 Tenant to Tenant Migration Tool because it has an incremental migration option called “Skip Previously Migrated.” The idea is that after an initial transfer, the tool identifies data that has already been migrated and processes only the newly added items during subsequent sessions.

It also provides date range, file size, file extension, content type, created/modified date, and duplicate-detection filters. That could be useful if an organization doesn't want to transfer every piece of historical data.

The Active Tasks dashboard provides real-time migration progress, while migration reports show transferred, skipped, failed, and completed items. For a large project, having that visibility seems important. How do you normally structure initial migration + delta migration before final cutover?
https://www.drssoftech.com/tenant-to-tenant-migration/