File server decommission checklist: what to check before years of shared drives are deleted

Why does a file server decommission need an assess-before-delete gate?

A file server retirement has a built-in cleanup step, and that is where a company's proposals, SOPs, project folders and signed contracts get deleted for good. This checklist adds one gate to the usual project plan: nobody deletes the old shares until the owner has seen what is on them and decided what to keep.

For an MSP, the gate is cheap. It adds an inventory and one conversation to a project you are already running, and it protects the client from an irreversible mistake. Retired servers also tend to hold the longest histories a small company has, which is why some clients later ask whether those documents have value beyond the archive.

Use this list with the client's project lead. It assumes a move to SharePoint, OneDrive, Google Drive or another cloud store, but works for plain retirement too.

Before you touch the server

Scope and ownership

• Named client contact with authority to approve deletion
• Written list of every share, drive letter and mapped path
• Retirement date, support-contract end and hardware lease end recorded
• Legal hold, audit or regulatory retention requirements confirmed with the client
• Backup of the full server taken and restore-tested

Content discovery

• Folder sizes and last-modified dates reported per share
• Departments mapped to shares: sales, finance, operations, engineering, HR
• Oldest and newest file dates recorded for each top-level folder
• Shares holding SOPs, proposals, project archives and templates flagged
• Sensitive areas flagged: HR, payroll, health information, customer personal data

The records value screen

Run this after discovery, before cleanup. It takes roughly the length of one client meeting.

Four signals worth a second look

• Depth: folders going back many years, including closed projects
• Structure: consistent naming, versioned documents, project numbering
• Context: proposals alongside contracts, delivery notes and close-out reports, so you can follow a job from quote to finish
• Ownership: the client wrote and owns the documents, not mainly a customer's or a vendor's files

Qualifying questions for the owner

• Does the company have 50+ full-time employees at peak, contractors excluded?
• Is there an owner, CEO, CFO or authorized representative who would consider a licensing conversation?
• Would the owner accept an exclusive AI-training license for an agreed term?
• Are other systems, such as email, CRM and finance, also long-lived? Strong candidates often have 10-15+ systems.

The who qualifies page lists the full baseline.

How to read the screen results

Cleanup rules while the gate is open

• Do not delete project, proposal, SOP or template folders on the server
• Remove only agreed junk: temp files, installers, personal media, duplicate backups
• Keep original timestamps and folder structure in the migrated copy
• Keep permission and ownership metadata where the target allows it
• Record what was excluded from migration and why
• Store the cold archive in client-owned storage, with an index file

What to do with the server and the contract

• Power the server down only after the migrated copy is verified by the client
• Keep the disks, or a verified image, for a set period agreed in writing
• Wipe or destroy drives only on the owner's written approval and with a certificate
• Update the client's asset register and renewal calendar

When the project is part of a wider shutdown, the office closure checklist and the year-end close checklist cover records the file server does not hold. For helpdesk archives that sit alongside shares, see what happens to your ticket archive.

What do you say to the client?

The introduction email builder drafts an owner-approved version. As the MSP, you never export, upload or describe the files; you share basic fit information only.

What do MSP partners earn, and what are the rules?

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. It is a share of SourceX's fee and never reduces what the client receives. Disclose the arrangement to clients where your agreements or policies require it, and read the program terms. The MSP client offboarding checklist pairs well with this one.

Next step

Add the records value screen to your next retirement project. When a client passes, register as a partner and make the introduction. The page for managed service providers explains the role, and how to wind down a company covers closures.