Who Keeps the Cloud Files When an Employee Leaves?

Start with a handoff plan

Assign one person to coordinate with the employee’s manager, IT administrator, and records or legal team. Agree on the departure date and identify urgent work before changing the account. If access must stop immediately, IT can secure the account first and arrange an administrative transfer.

Ask where work actually lives. A file shared with a team may still be in one person’s account. Also check shared workspaces, external services, and files shared by customers. A single transfer may not cover every location.

Find the files and their dependencies

Ask the manager which work must continue and which records must be preserved. Record the location, current owner, intended custodian, and required access for each important collection.

Separate items the team needs to edit from records it must preserve. Ask the records owner before deleting, moving, or changing material subject to a hold. A copy may not preserve every permission, link, version, or integration, so test the result.

Choose a custodian and a destination

For each collection, choose a responsible person and an approved destination. A team-managed location can reduce dependence on another individual account. The choice depends on your organization’s storage and retention policies.

1. 01

   Map the work

   List the folders, owners, collaborators, and links that matter. Note anything that must remain restricted.

2. 02

   Transfer or move with IT

   Use the provider’s supported method. Confirm the destination has enough space and appropriate permissions.

3. 03

   Test as the recipient

   Open representative files with the recipient’s account. Check editing, sharing, important links, and any connected workflow.

4. 04

   Record the result

   Record the new location, responsible person, exceptions, and review date. Resolve missing items before account cleanup.

For example, imagine that Maya leaves a small project team. Her manager lists a contract, a planning folder, and a client form. IT transfers the relevant files to an approved team location. A colleague opens the contract and submits a test form, then records the new links. This is a fictional workflow, not a claim that every service preserves those links.

Understand the OneDrive license timeline

For an unlicensed OneDrive linked to a user account that remains in Microsoft Entra ID, Microsoft documents default milestones. These rules do not apply to EDU, GCC, or DoD customers. Settings and account status matter. Read Microsoft’s account guidance.

For accounts already unlicensed and unpaid on July 1, 2026, the nonpayment clock began on that date. Microsoft gives July 1, 2027 as the earliest deletion-risk date for those accounts. For accounts that become unlicensed later, the clock begins on the relevant license removal or user deletion date. Paid storage options and customer exclusions matter. Do not assume a retention policy alone protects an unpaid account indefinitely. Check the current policy and exceptions.

Deleting the account starts a different process

Removing a license is not the same as deleting the user. Microsoft says the OneDrive cleanup retention period starts when the user account is deleted from Entra ID. Blocking sign-in or removing the license alone does not start that cleanup process. See OneDrive retention and deletion.

The default OneDrive retention period for a deleted user is 30 days, but an administrator can change it. After that period, the site normally moves to a recycle bin for 93 days. Retention policies, holds, and the unlicensed storage rules can change the result. The recycle bin is not ordinary access, so move needed files before cleanup.

Microsoft recommends preventing a former employee from signing in and arranging access to needed data as part of offboarding. Coordinate the order with IT and the records team. Do not share the departing employee’s password to make the handoff easier. See Microsoft’s offboarding overview.

Google Drive ownership needs its own checks

Google Workspace administrators can transfer eligible Drive files to another person in the organization. The recipient needs an active account, sufficient storage, and Drive enabled. Google does not support direct ownership transfer to or from an external account. See Google’s administrator instructions.

Google says files in Trash are not transferred in a bulk transfer. The administrator should check for files owned by other people and for unorganized files. Some files need separate treatment. A completed transfer does not automatically change who has access, and the previous owner can retain editing access unless permissions or the account change.

Verify the handoff before cleanup

The recipient should open representative files, search the destination, and test a critical link or workflow. Ask external collaborators to confirm access where appropriate. Review permissions for confidential material and remove access that is no longer authorized.

If the person already left, contact IT promptly. Give the administrator the account, departure date, file locations, and last known links. Recovery depends on the service, account state, retention settings, and time elapsed.

Sources and update

Checked November 2, 2026. Provider rules and settings can change. The examples describe work accounts and do not cover every provider or organization.

• Microsoft: Manage unlicensed OneDrive user accounts
• Microsoft: OneDrive retention and deletion
• Microsoft: Remove a former employee and secure data
• Google Workspace: Transfer Drive files to a new owner as an admin