Retiring an on-premises file server: what to do with decades of project files

What should happen to project files when a file server is retired?#

When an on-premises file server is retired, project files should be sorted rather than moved as one block. Active projects migrate to the new platform, closed projects go to a read-only archive, true duplicates and temporary files are deleted under the retention schedule, and records with reuse value are set aside for review.

The trigger is often a hardware refresh or the end of support for the server's Windows Server version; Microsoft publishes lifecycle dates for each version, so check yours early. Whatever the trigger, the server usually holds the firm's whole history: project folders, CAD and Revit files, scanned contracts, PST files and the personal drives of people who left long ago.

The decision table for every top-level folder#

The decision table assigns every top-level folder one outcome, with the permission and client-file cautions that apply. A folder without a recorded outcome is not ready to move.

Assign outcomes at the project level, not the file level. Sorting individual files across decades of work is not practical, but a project principal or records owner can usually assign an outcome to a whole project folder from the inventory and the accounting record.

Inventory before you move anything#

Inventory comes before any migration, because every decision needs facts about what is on the server. A file-share inventory report gives path, size, owner, file type and last modified date for every folder; most migration tools and storage reports can produce one.

The inventory also shapes the destination. Renders, point clouds and scanned drawings often account for much of the volume, and they may belong in archive storage rather than the collaboration platform.

• 1Map top-level folders to project numbers in Deltek, BQE or the ERP, and flag folders that match nothing.
• 2Find CAD and Revit files with external references, linked models and central files.
• 3Locate PST files, scanned contracts and the home drives of departed staff.
• 4Flag folders holding client-furnished material, restricted projects or secure facility work.
• 5Note folders with unusual permissions, such as one person only or everyone with full control.

Why CAD and BIM files break in migrations#

CAD and BIM files break in migrations because they depend on paths. AutoCAD drawings load external references by path, Revit models link to other models and may rely on a central file, and plot styles, fonts and title blocks often sit in an office standards folder on the old server.

Cloud file platforms such as SharePoint and OneDrive also have path length and character restrictions, so check Microsoft's current limits before moving deep project trees. Folder names that worked on a mapped drive can exceed them.

Two practical options work for closed projects: archive the project tree as it is, with paths and standards preserved, or bind references before archiving so each drawing opens on its own. Active projects need a tested plan for references, usually proven on a pilot project first.

Permissions, ownership and client files#

Permissions on an old file server rarely map cleanly to a new platform, and copying them blindly can expose restricted folders. Rebuild access around current groups, and treat any folder with special restrictions as a decision for the project principal.

Client confidentiality obligations travel with the files. Projects for secure facilities, public agencies with records rules, or clients with strict confidentiality clauses need the same or tighter restrictions in the archive, and client-furnished surveys, reports and drawings remain the client's wherever they are stored.

Departed staff need a separate pass. Their home drives and mailboxes often hold the only copy of some project correspondence, mixed with personal files that should not move into any firm archive. Move project material into the right project folders and handle personal content under the firm's HR and privacy policies.

What is safe to delete#

What is safe to delete depends on file type, the retention schedule and any hold. The table separates the usual candidates from records that only look like clutter.

Illustrative: a CTO retires the firm's last file server#

Illustrative: a fictional engineering and architecture firm still runs one on-premises file server holding every project since its founding. The CTO plans a move to SharePoint for active work and cloud archive storage for closed projects.

The inventory shows many folders whose names no longer match Deltek project numbers, PST files from retired principals and a scanned archive of old drawing sets. Revit links break in a test migration of one active project.

The CTO archives closed projects as they are, with paths preserved, migrates active projects in phases after fixing links on a pilot, sends PST files to counsel for a retention decision, and tags closed projects with linked RFI logs and QA comments for a later review of internal reuse and licensing. Nothing is deleted until the retention schedule is approved.

How SourceX fits into a server retirement#

SourceX fits at the review-for-value step. Before the server is shut off, a firm can describe its closed project archive in metadata only, such as systems, years of history, record families and known restrictions, which is enough for a fit check without sharing any files.

If a package proceeds, the data stays in the firm's own storage or ships on encrypted drives; SourceX never hosts multi-TB datasets. Rights, preparation and approval follow the SourceX five-step transaction, and the firm approves each step.