domainwidedelegation.comStart free

Use cases → Admin and governance

Migrate user data during employee role changes

Automate Drive, mail, and calendar data migration when users change teams or roles, ensuring business continuity and proper access.

Who it is forIT administrators and internal support teams managing user lifecycle events.
APIsDrive API, Gmail API, Calendar API
Typical scopesdrive, gmail.readonly, calendar

The problem

When employees change roles, their data — files, mail, calendar events — often needs to move to new owners or shared spaces. Manual handover is error-prone, slow, and often misses items, especially with hidden or delegated content.

How it works

  1. Identify the user account changing roles and the destination account, group, or shared drive.
  2. Enumerate files, mail, and calendar items using the delegated service account.
  3. Transfer or share ownership of files; forward or label critical mail; copy or reassign calendar events as required.
  4. Log every action and surface any items that cannot be migrated due to API or sharing restrictions.

What changes

The user’s business data follows them or their replacement, reducing disruption and avoiding orphaned content.

The trap in this one. Drive file ownership transfer to another user in a different organisational unit or outside the primary domain will silently fail for some file types, especially Google Photos or files owned by deleted users. The Drive API will report success for the batch, but skip these files without error unless you check the per-file response — always inspect the response for each item, not just aggregate status.

Questions people ask

Does this cover delegated access and hidden mail?

Delegated access can be enumerated, but mail in delegated or hidden labels may not be visible to the service account unless explicitly shared. Test visibility with a sample account before bulk migration.

How do you handle calendar event ownership?

Calendar events can be transferred by copying and re-assigning organiser or attendee fields, but recurring meetings will generate new IDs, so participants may see duplicate invites.

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 guide

Related use cases

Continuously verify your delegation still works

A scheduled probe that proves every API still answers under every tenant, before a customer finds out otherwise.

Automate onboarding task creation across new hires

Automatically generate Drive folders, assign Calendar events, and send welcome emails for each new user as they join the organisation.

Automate joiners, movers and leavers

Create accounts, set group membership, provision Drive and hand over mailboxes without a manual checklist.