Identify the approved recipient for each data type and check retention requirements. Include customer correspondence, owned files, shared-drive roles, meetings organised by the user and business services using their Google sign-in. Limit access to the people authorised to receive the information.

1. Secure the account according to the departure plan, using suspension and session controls where appropriate.
2. Review Google's supported preservation options, such as continued suspension or an eligible archived-user arrangement. Check licence and plan availability with the service owner.
3. For Drive ownership transfer, confirm the destination is an eligible user in the same organisation with sufficient storage and Drive access.
4. Use the Admin console's supported data-transfer workflow for the relevant service and review its completion report.
5. Handle email preservation or transfer through a supported method, separately from Drive. Review calendars and other application ownership individually.
6. Give the replacement person an authorised way to receive future business correspondence, then test it.

Ask the receiving owner to open representative files and records. Check folders, shared access and important event ownership. A successful transfer status does not prove that every business application has moved or that all data types were included.

For a reviewed transfer from [email protected] to [email protected], first confirm both users are in the same organisation and the destination is active, has Drive enabled and has enough space. Check the source's eligibility, including any hold, and move required items out of Trash because Trash items are excluded from this transfer.

1. Prepare the accounts to prevent concurrent file changes during the handover.
2. With the Drive and Docs administrator privilege, open Apps > Google Workspace > Drive and Docs > Transfer ownership.
3. Select Ada under From user and the approved manager under To user.
4. Choose Transfer Files, then wait for completion and inspect representative files.

Ownership transfer does not itself remove existing access. Review the former user's permissions and the separate mail, calendar and application handovers before deleting the account.

Retention and legal-hold features depend on edition and configuration. Do not assume that deleting a user leaves their data indefinitely available in Google Vault. Review the specific preservation option before changing the licence or deleting the account.

Record the decisions, transfer reports and final access review. Only complete deletion after the authorised owner confirms the necessary records and services have been preserved. If an account was deleted prematurely, start the supported recovery process promptly.

• Suspending a Google Workspace user while preserving business data
• Restoring an accidentally deleted Google Workspace user
• Keeping team files in an eligible Google shared drive
• Planning a staff departure across email and shared files

• Google Workspace former-employee data options
• Google Workspace Drive ownership transfer
• Google Vault questions and answers