Employee Offboarding File Transfer: Keep Customer Work Moving

Imagine a service business in Albany has a customer job ready to start. The office can find last month's estimate but the current quote lives in a departing contractor's cloud account. Someone posted a link in the team chat, so everyone assumed the folder was safe.

That is an illustrative situation, not a client case. It shows why I treat employee offboarding file transfer as a continuity job, not just account cleanup. The next authorized worker needs the right files in a location the business controls. Meanwhile, the departing person's access needs to end under the business's policy.

My order is simple: identify the essential work, preserve authorized data, block access at the appropriate time, transfer carefully and verify the handover before destructive deletion. This runbook is for owners and authorized administrators using Google Workspace or Microsoft 365. It is not permission to enter someone's personal account.

Before departure: make a map of the work, not just the folders

Start with what another person must be able to finish tomorrow. That might be an accepted quote, a drawing awaiting approval or the spreadsheet used to schedule crews. Ask the worker and supervisor to identify the current source of truth while both are available.

For each essential item, record its location, actual owner, replacement business steward and required collaborators. Include the customer or vendor who legitimately needs access. Also record links used in recurring emails or job-management software. A folder transfer can appear successful while the office keeps opening an outdated shortcut.

Choose the destination before moving anything. Give the successor appropriate access and check storage capacity. Keep personnel records separate from routine customer work. Do not grant everyone access merely to make the handover easier.

Have the authorized administrator check retention requirements, holds and licensing before deletion or license removal. If a dispute or regulated record is involved, bring in the business's qualified adviser. I would not use a general blog checklist to decide how long legally required records must remain.

A shared link is not organizational ownership

In Google Workspace, a shared My Drive folder is not the same thing as a shared drive. Files in My Drive have individual owners. Files in a shared drive belong to the organization and remain when a member leaves. Access levels and subscription capabilities still matter. See Google's shared-drive ownership guidance.

Microsoft makes a similar practical distinction: individual OneDrive suits drafts and work shared with specific people, while a SharePoint team library suits ongoing team content. Seeing a OneDrive link in Teams does not prove it moved. Check the storage location using Microsoft's collaboration guidance.

Departure day: stop access without rushing into deletion

Coordinate the cutoff with the owner or designated decision-maker. Have the administrator block access promptly under your policy and follow the platform's supported session-revocation procedure. Do not leave a departing person's login active just because the file review is unfinished.

But do not confuse blocking access with deleting the account. Google lists suspension and archiving among its former-employee preservation options. Microsoft's deleted-user OneDrive cleanup clock starts at account deletion, not when sign-in is blocked. License removal creates separate consequences.

Keep the successor on their own authorized account. Borrowing the former worker's password makes accountability worse and does not solve ownership. Our business passkeys and password-manager guide is a companion for access planning, not a replacement for this handover.

Google Workspace branch: transfer owned files, then check the destination

For organization-owned accounts, an authorized administrator can transfer a user's Drive ownership to another active user in the same organization. The recipient needs Drive enabled and enough storage. Google's administrator transfer instructions require the relevant administrator privilege and list holds among the prerequisites that need attention.

That Admin console route is a whole-user transfer, not a tool for selecting three sample files. Before departure, an active owner can transfer selected individual files through an approved route. Where a permitted shared-drive move is appropriate, start with a small set and verify it before scaling up. If only bulk transfer is available, prepare the inventory and destination first.

Google recommends suspending the source account during bulk transfer. Items in Trash are excluded, so review authorized items that need preservation beforehand. Files owned by other people within the same folder hierarchy need separate attention. Wait for completion rather than assuming a new transfer folder means everything arrived.

Ownership transfer does not automatically remove the previous owner's permissions. Moving content into a shared drive can also change access inherited from its former folder. Keep the account blocked and check both the intended collaborators and the sensitive folders afterward.

Contractor using an outside Google account? The ordinary administrator transfer cannot directly transfer ownership from that external account. Arrange a supported handover with the owner, such as an allowed shared-drive move. Copying can change URLs and require resharing. If authority or cooperation is missing, escalate rather than seeking a password or bypass.

Microsoft 365 branch: move needed OneDrive content to team storage

Have an authorized administrator establish successor access before deletion. Do not delete an account just to trigger an access email. Automatic manager or secondary-owner delegation and notifications depend on configuration, so confirm who will receive access.

Microsoft's departing-employee transfer guidance describes a Shared filter for prioritizing collaborative files. Also review All: an unshared draft may be tomorrow's essential quote. Select an approved pilot set, choose Move to and, where available, select Keep sharing with the same people. For ongoing team work, use the approved SharePoint library rather than another temporary personal repository.

The documented operation is a real move, not merely a copy. Review destination permissions and test collaborator access before moving the rest. Keep sharing is useful but it is not an invitation to preserve an inappropriate external permission indefinitely.

Microsoft's OneDrive retention guidance gives a default deleted-user period of 30 days, which administrators can change. Record your actual setting and deadline. The later recycle-bin period does not keep shared customer files accessible to the team.

Do not remove a license and assume the account becomes a free archive. Current commercial unlicensed OneDrive rules include read-only and archival stages. Microsoft's retention page also warns that prolonged unpaid archive storage can lead to deletion despite holds. Confirm the licensed or paid preservation arrangement with your administrator rather than relying on an old checklist.

Verified handover: rehearse the next person's actual task

I would ask the successor to sign in normally and complete a short acceptance check:

• Open the current essential document and confirm its contents, not just its filename.
• Make an approved small edit where editing is required.
• Follow the link staff actually use from their workflow.
• Check access with an authorized customer or vendor when external collaboration matters.
• Confirm restricted records remain restricted.

Record the destination, responsible steward, date and unresolved exceptions. Update old shortcuts and workflow links where necessary. File count alone is not proof of a usable handover.

For future jobs, choose the team storage location when work begins and name a backup business steward. That way, an unexpected absence does not require rebuilding the same inventory. The goal is not to make the replacement employee the next single point of failure.

Only after that review should the authorized administrator consider account deletion or other destructive cleanup under the approved preservation plan. Keep customer messages moving separately through a shared-inbox workflow; transferring a quote does not assign the email asking about it.

If the exit is abrupt or another app holds the work

The person has already left: block access through authorized administration, preserve the account's data and prioritize today's customer-critical files. Do not ask coworkers to rummage through personal accounts. If someone already deleted a Google Workspace user, Google's preservation page specifies a 20-day restoration window before transfer. Contact the administrator immediately rather than assuming recovery is possible.

Does this include Forms or Lists? No. Microsoft says these are not traditional OneDrive files and are excluded from its transfer mechanism. Give them a separate app-specific handover. Calendar ownership, meeting recordings and automations also deserve their own review. A copied document does not prove the connected process still has an active authorized owner.

References

• Google: shared drives and ownership
• Google: administrator Drive transfers
• Google: former-employee preservation options
• Microsoft: team and individual storage
• Microsoft: departing-employee file transfer
• Microsoft: OneDrive retention and deletion
• Microsoft: unlicensed OneDrive accounts

Need an authorized handover plan?

I can help your Long Island or Capital Region business organize a cloud-file continuity plan. Call FleckTech Solutions at (631) 319-8324 or (518) 318-8324, or book a consultation.

For more practical business and home technology guidance, subscribe to the FleckTech Solutions newsletter.