Retire a Windows Server 2016 File Share Without Losing Legacy Files

Many small offices still keep decades of memos, budgets, and client packets on a Windows Server 2016 file share. That box may still feel fine day to day. Microsoft’s lifecycle and release-health guidance is clear: Windows Server 2016 reaches end of updates on January 12, 2027. Retiring the share without first dealing with the legacy files on it is how archives go dark — WordPerfect, Works, Lotus, AppleWorks, and other formats that never open cleanly on a brand-new file server.

What “end of updates” means for the share

Microsoft documents that Windows Server 2016 reaches end of support with a final monthly update on January 12, 2027. After that date, the product no longer receives the regular security update stream under extended support. Your IT plan may include Extended Security Updates, a move to a newer Windows Server, or a cloud file service — none of those plans automatically modernize the legacy files sitting in `\\fileserver\Shared`.

• Replacing the server does not convert WordPerfect, Works, Lotus, or AppleWorks files.
• Mapped drives on new PCs still leave unreadable formats unreadable.
• Waiting until the share is powered off is the hardest time to recover missing folders.

This is not “migrate an old Windows PC”

A common related problem is retiring a dusty desktop — covered separately in Migrating Files Off an Old Windows PC. That guide is about files trapped on a personal machine you are replacing. This post is about the office file share on Windows Server 2016: a shared volume many people use, often full of zip backups and decade-old project folders, that IT is about to decommission before the January 12, 2027 cliff.

Step 1 — Inventory the legacy files on the share

Before anyone “just copies everything to the new server,” walk the share with an inventory mindset. You are looking for formats that modern Word, Excel, and PowerPoint will not open cleanly — the same legacy files that turn up on old PCs, but concentrated on one network volume.

• Word processors: WordPerfect (`.wpd`), Microsoft Works (`.wps`), Lotus Word Pro (`.lwp`), Ami Pro (`.sam`), AppleWorks / ClarisWorks (`.cwk`).
• Spreadsheets: Lotus 1-2-3, Quattro Pro, older Works spreadsheets.
• Layouts and packets: older Publisher (`.pub`) and other layout files saved beside the Word docs.
• Archive wrappers: ZIP, 7z, and similar backups dropped on the share “for safekeeping.”

Step 2 — Copy to a local folder first

Once you know what matters, copy those legacy files to a local folder on a Windows PC before you convert. Treat the share as the source of truth for the copy job, not as the working folder for conversion.

• Why local: you can spot-check, rename, and batch-convert without depending on VPN latency or a share that might vanish mid-project.
• Why not “convert in place on the mapped drive”: do not plan on using the live share or a mapped network drive as the conversion working path. Copy first, convert second.
• Keep structure: mirror the share’s folder tree into something like `C:\ShareRescue\Shared\…` so owners still recognize paths.

Step 3 — Convert locally to PDF or current Office formats

With a local folder in hand, convert the pile offline. Prefer PDF when you need a frozen, long-lived reading copy; prefer current Office formats (DOCX, XLSX, PPTX) when someone still needs to edit. You can do both: a PDF for the archive and an editable copy for active work.

Legacy File Converter runs on Windows 10/11 as a desktop app. Conversion stays on the PC — nothing is uploaded. Use it as a soft option for the local rescue folder after the copy step, not as a reason to skip inventory.

What “done” looks like before cutover

• Every share path that still matters has a local copy.
• Legacy files you care about have a PDF and/or current Office sibling.
• ZIP/7z backups from the share are either expanded into the rescue tree or converted via the archive workflow.
• IT can retire or rebuild the Server 2016 share without the only readable copy living on that box.
• Owners know where the new local (or new-server) paths live.

Summary

January 12, 2027 is the Windows Server 2016 update cliff on Microsoft’s published timeline. October 13, 2026 already closed Office 2021 support. Before the office file share goes away, inventory the legacy files, copy them to a local folder, then convert offline to PDF or current Office formats. For folder-scale work see batch convert; for archives see ZIP and 7z. That is how you retire the server without retiring the documents.