A shared file ownership transfer checklist prevents a familiar offboarding failure: the team can still see a folder, but the documents inside remain owned by the departing person. The safe approach is to inventory files, name a durable owner, transfer what the platform permits, and test access before removing the old account.
Define the transfer scope
Start with the person's work account, shared drives, personally owned folders, forms, spreadsheets, reports, and automation files. Record the current owner, intended owner, business purpose, sensitivity, and whether an outside collaborator relies on the link. Include items reached through bookmarks or embedded in project tools, not only files visible in the top-level folder.
Google explains that transferring a folder does not transfer ownership of every file inside it. It also limits work or school ownership transfers to accounts in the same organization. That makes a file-level inventory important even when the folder appears to have moved successfully (Google Drive Help).
Choose a durable destination
Prefer an organization-managed shared location or role account over another employee's personal workspace when policy allows. Confirm that the successor has the right license, storage, and permissions. For a temporary handoff, document when access should be reviewed or removed.
Before making changes, save an inventory that includes:
- file and folder name;
- current and proposed owner;
- canonical link;
- sharing scope and external guests;
- retention or legal-hold requirements;
- workflow, form, script, or integration dependencies.
Transfer and preserve evidence
Use the platform's supported ownership or administrative transfer controls. Avoid downloading and re-uploading as a default because that can change links, ownership history, comments, or versions. Microsoft notes that an administrator can grant another employee access to a former employee's OneDrive, and warns that some move or copy methods preserve only the latest version rather than the full version history (Microsoft Learn).
For each important item, record the action taken, the operator, the time, and any exception. If a native transfer is unavailable, decide explicitly whether the approved fallback is to copy, export, archive, or keep the source account under retention controls.
Test before account removal
Sign in as the successor or use a controlled test account. Open representative documents, follow old shared links, edit a noncritical test file, submit a form, and verify that connected reports still refresh. Check an external collaborator's access separately; internal success does not prove that a guest link still works.
Do not treat a successful folder open as completion. Sample files owned by the former employee, files owned by other teammates, and content stored in shared spaces. Review automations that run under the old identity, because ownership and execution credentials are separate concerns.
Close the handoff
Remove temporary administrator access, update the ownership register, notify the new owner, and schedule a follow-up review. Keep the former account until retention, email, and access requirements are satisfied under your organization's policy. The final record should show what moved, what stayed, what was copied, and who accepted responsibility.
Quick completion test
The handoff is ready to close when the named owner can open and edit the required files, important old links still resolve, guest access matches policy, workflows no longer depend on the departing identity, and exceptions have an owner plus a due date.