Use cases → Admin and governance
Validate migrated data matches source after Workspace migration
After a domain migration, automatically compare source and target accounts to confirm files and emails arrived intact and accessible.
| Who it is for | Admins running Google Workspace tenant-to-tenant migrations. |
|---|---|
| APIs | Drive API, Gmail API |
| Typical scopes | drive.readonly, gmail.readonly |
The problem
Manual checks after a migration miss discrepancies and don't scale. Even major migration tools can silently skip files, lose labels, or botch sharing permissions without surfacing errors. A delegated service account can audit the actual user data, but only if you script it to check exhaustively.
How it works
- List all files and emails for each source user with the service account.
- List the corresponding data in the target account, matching by metadata and content hashes where possible.
- Flag any missing or mismatched items, including labels and sharing settings.
- Summarise discrepancies for admin review and possible remediation.
What changes
You know which users or objects failed to migrate correctly, and can take action before users discover missing data.
Questions people ask
Does this catch permission issues as well as missing files?
Yes, but only if you explicitly compare sharing settings and ACLs, not just file existence. Migrations often drop delegated access or group shares.
How soon after migration should I validate?
Wait at least 10–30 minutes for small accounts, and several hours for large tenants or shared drives, to avoid false negatives from API lag.
Want this built?
This is a pattern we run in production. We will set up the delegation and build this on top of it — $500 per hour, most of it working the same day.
Talk to us Or read the setup guideRelated use cases
Automate joiners, movers and leavers
Create accounts, set group membership, provision Drive and hand over mailboxes without a manual checklist.
Continuously verify your delegation still works
A scheduled probe that proves every API still answers under every tenant, before a customer finds out otherwise.
Reduce an over-broad delegation grant safely
Find out which scopes your automation genuinely uses, then cut the grant down to them.