When an employee leaves, their Drive files can become a quiet mess. One missed folder can delay a handoff, break access, or leave a manager hunting for a document that should already be safe.
I handle Google Drive ownership transfer before the account is removed, because timing matters more than cleanup later. In Google Workspace, the wrong order can leave files stranded, blocked by a hold, or stuck in a personal My Drive.
The good news is that the process is simple once I separate personal Drive files, shared drive content, and anything under retention. I follow a set sequence, then I verify the result before I touch suspension or deletion.
Table of contents
- Transfer ownership before the account is removed
- What transfers and what does not
- Shared drives need a different playbook
- If the normal transfer fails
- Conclusion
- FAQs
Transfer ownership before the account is removed
I start with the Admin console while the account is still active. That matters, because Google only allows direct ownership transfer inside the same organization, and the departing user can’t already be deleted.
Here’s the exact flow I use:
- I confirm the new owner is active, licensed, and inside my Google Workspace domain.
- I review the employee’s Drive content and move company files to shared drives when they belong to a team.
- In the Admin console, I go to Apps, then Google Workspace, then Drive and Docs, then Transfer ownership. Google’s admin transfer instructions follow this path.
- I enter the current owner’s email, then the new owner’s email.
- I start the transfer and wait for the confirmation email.
I do this early, because large transfers can take time. Google notes that long jobs can time out after 36 hours, so I never leave this for the last afternoon.
A transfer changes ownership, but it does not reset access. I still review sharing after the move.
What transfers and what does not
A lot of offboarding mistakes come from mixing up ownership and access. Google’s file ownership rules make the limit clear, but I still see teams assume everything moves together.
| Item | Can I transfer ownership? | What I do |
|---|---|---|
| Files in My Drive | Yes | Move them to the new owner before deletion. |
| Files in shared drives | No | Leave them in the shared drive or move them by policy. |
| Existing sharing permissions | No change | Review access after transfer, since permissions stay in place. |
| Files owned by external accounts | No | Use a shared drive handoff or export the content manually. |
The main takeaway is simple. My Drive files can move, shared drive files usually do not need a transfer, and access does not reset on its own.
When I know the employee handled client files, I run a quick Google Drive sharing audit after the transfer. If the files are records, I pair that with Google Vault retention rules setup so the business keeps the right history.
Shared drives need a different playbook
Shared drives change the whole offboarding picture. The files belong to the organization, not the person, so I do not treat them like personal property. That is why I keep Shared Drives roles and permissions in front of me when I prepare a departure.
When a team stores work in shared drives, offboarding gets easier. I check the member list, confirm the managers, and make sure the departing employee is not the only person who knows where critical folders live.
Google’s options to preserve former employee data page also makes this distinction clear. If content is already in a shared drive, the cleanup is usually about access and role changes, not ownership transfer.
I also keep storage cleanup in mind. If a team has built its filing habits around shared drive structure, I review Google Workspace backup best practices so recovery stays possible later.
If the normal transfer fails
Sometimes the clean path breaks. The account may already be deleted, the user may be under legal hold, or the files may sit outside my organization. In those cases, I stop trying to force a standard transfer.
My fallback is usually one of three moves. I restore or keep the account active long enough to finish the transfer. I move files into a shared drive when another manager or organizer can take control. Or I recover the data first, then sort ownership later with recovering deleted Drive files.
If the old owner is outside my domain, direct ownership transfer will not work. For that case, I use a shared drive handoff or a manual export path. That keeps the business in control without waiting on a feature Google does not allow.
Conclusion
When I transfer Drive ownership early, offboarding feels calm instead of rushed. The account can leave later, but the files are already safe, and the team knows where they live.
The key is to treat ownership, access, retention, and shared drives as separate steps. Once I do that, Google Drive offboarding stops being a scramble and becomes a routine admin task.
FAQs
Can I transfer Google Drive ownership to someone outside my company?
No. Direct ownership transfer works only inside the same Google Workspace organization. For outside cases, I use a shared drive or a manual export path.
What happens to files in a shared drive when an employee leaves?
They stay with the organization. I only update membership and roles, which is much easier than moving ownership file by file.
Can I transfer ownership after the employee account is deleted?
Usually not. I need the account active, or I need to restore it first. That is why I handle the transfer before deletion every time.
