How can AEC firms migrate file servers to the cloud before Windows Server 2016 ends?

For many architecture, engineering and construction firms, the Windows Server 2016 machine in the server closet is the project file server, holding every Revit model, AutoCAD drawing set and Civil 3D surface the firm has produced since it went in. Microsoft stops patching it on January 12, 2027, so the decision about where those files live next belongs on this quarter's agenda.

When does Windows Server 2016 support end?

Microsoft ends extended support for Windows Server 2016, the date most people call its end of life, on January 12, 2027. After that date, a server running it stops receiving security updates unless the firm pays for Extended Security Updates (ESUs).

Microsoft's lifecycle page lists the extended end date as 6:59:59 a.m. UTC on January 13, 2027, which is the evening of January 12 in California. Mainstream support ended in January 2022, so these servers have received security fixes only for almost five years.

Firms still running Windows Server 2012 or 2012 R2 are already past the end of that line. Microsoft's final ESU update for those versions shipped October 13, 2026.

Can a firm keep running Windows Server 2016 after January 2027?

Yes, with paid Extended Security Updates, which Microsoft offers for up to three years, through 2030. ESUs deliver Critical and Important security updates only, with no new features or nonsecurity fixes.

There are two main routes. Servers connected to Azure through Azure Arc can enroll in ESUs in the Azure portal. Configuration opened August 3, 2026, billing begins January 13, 2027, and the service is billed monthly on a pay-as-you-go basis. Purchasing requires Software Assurance through a volume licensing program such as an Enterprise Agreement, unless the server is licensed through SPLA or a Server Subscription. Workloads moved into Azure virtual machines and other Azure-hosted environments can also receive ESUs for three more years, according to Microsoft's ESU page.

Microsoft has not published Windows Server 2016 ESU prices on these pages; it points customers to the Azure portal or a Microsoft representative. For reference, Microsoft priced on-premises ESUs for Windows Server 2012 at 100% of the full license price each year. ESUs buy time on the operating system. The hardware underneath keeps aging.

Why don't AEC project files simply move to SharePoint or OneDrive?

CAD and BIM files behave differently from office documents, which makes a straight file server to SharePoint migration risky for project folders. They are large, they reference one another, and the applications that open them expect one shared copy on a file server where an open file is locked for everyone else.

Microsoft's own documentation shows the limits. OneDrive and SharePoint accept files up to 250 GB, and Microsoft recommends no more than 300,000 items across a user's cloud storage for best performance. A decade of project folders can pass that count on its own. Microsoft also notes that editing files offline, or changing the same files on another synced PC at the same time, can cause sync conflicts.

That matters for design work. A drawing set built on external references, or a model linked to consultants' models, depends on those links resolving to the same path for every user. When each person works from a synced local copy, two people can save over each other's changes, and a broken path can show up as a missing reference the next morning.

Jobsites add a second problem. A construction trailer on a cellular connection makes a multi-gigabyte model slow to open from anywhere. Moving files to the cloud without a local cache moves the bottleneck from the office uplink to every site connection.

SharePoint still fits much of what an AEC firm stores: contracts, RFIs, submittals, proposals, specifications and other office documents, which gain co-authoring and version history there.

What are the main options for migrating an AEC file server?

Four paths cover most firms: upgrade the server in place, extend it to Azure with Azure File Sync, move office content to SharePoint, or migrate the file server to a cloud platform with local caching. Many firms combine two of them.

Upgrade to a supported Windows Server

Microsoft supports in-place upgrades from Windows Server 2016 directly to Windows Server 2019, 2022 or 2025, and its February 2026 announcement recommends Windows Server 2025. This keeps current workflows intact. It does not help remote offices or jobsites, and a server bought for 2016 may need new hardware anyway.

Azure Files with Azure File Sync

Azure File Sync keeps a Windows file server in the office and syncs its shares to a central Azure file share. With cloud tiering, the local server keeps frequently used files on disk and leaves cold files in Azure; the full folder tree stays visible, and a tiered file is recalled when someone opens it. Microsoft says a firm can run server caches in as many offices as it needs, with changes syncing through the Azure share to every site.

Three details matter for design teams. First, when the same file changes on two servers before sync catches up, Azure File Sync keeps both copies and renames the older one with the server name appended. No work is lost, but someone has to reconcile the two files, so active projects work best with one home office. Second, Microsoft notes that recalling a tiered file means downloading it from the cloud, so cold archives tier better than live models. Third, connecting to an Azure file share directly over the internet requires TCP port 445, which some ISPs and firewalls block; Microsoft points to a VPN for that case.

SharePoint for non-CAD content

Moving office documents to SharePoint shrinks what the file server carries and places those documents under Microsoft 365 sharing and retention controls. CAD and BIM project folders stay on whichever file platform the firm chooses.

Cloud file platforms with local caching

Several vendors sell cloud file services built for large design files, typically pairing cloud storage with an on-site cache and file locking across offices. Evaluate each one against its own documentation: how locking works between sites, how the cache behaves when the internet drops, where data is stored, and which security authorizations the service holds.

What changes for firms on Defense Department work?

If the file server stores controlled unclassified information (CUI), such as CUI-marked drawings for a military facility, it falls under DFARS 252.204-7012, which requires covered systems to meet NIST SP 800-171. A server that no longer receives security patches makes requirement 3.14.1, "identify, report, and correct system flaws in a timely manner," difficult to satisfy.

Paragraph (b)(2) of DFARS 252.204-7012 ties covered systems to NIST SP 800-171, and paragraph (b)(2)(ii)(D) requires that any external cloud service storing covered defense information meet security requirements equivalent to the FedRAMP Moderate baseline. The CMMC program rule at 32 CFR Part 170 assesses Level 2 against the 110 requirements of NIST SP 800-171 Revision 2. NIST has since published Revision 3, but the CMMC rule references Revision 2.

The destination matters as much as the deadline. Microsoft states that Azure and Azure Government hold FedRAMP High P-ATOs for in-scope services. A firm still has to confirm that the specific service it uses is in scope and that its configuration matches what the System Security Plan describes. The same diligence applies to any cloud file platform under consideration.

For more on the defense side, see our guides to which NIST 800-171 gaps to close first during the CMMC pause and what still applies while CMMC Phase 2 is suspended.

What should an AEC firm do this quarter?

With less than three months until January 12, 2027, choose a path now and decide whether ESUs are needed as a bridge. These steps make the decision concrete:

• Inventory every server running Windows Server 2016 or 2012, including the file server, license server and any plotting or scanning hosts.
• Measure the project share: total size, file count, largest models and which projects are active.
• Separate office content from CAD and BIM data and decide what moves to SharePoint.
• Identify any project folders holding CUI and which contracts include DFARS 252.204-7012.
• Check licensing. Software Assurance, SPLA or Server Subscription status determines ESU eligibility through Azure Arc.
• Pilot the chosen platform with one active project across two offices and a jobsite connection before cutting over.
• If migration will run past January 12, budget ESUs for the gap and set a firm end date.

How can s90 help?

s90 manages IT, security and compliance documentation for firms across Los Angeles and Orange County. We can inventory your Windows Server 2016 systems, size your project share, compare upgrade and cloud options against how your teams and jobsites actually work, and keep your System Security Plan current if CUI is involved. If a short conversation would help, contact our team.