SharePoint Server Support Ends July 14: Your On-Prem Migration Plan

Microsoft ends all support for SharePoint Server 2016 and 2019 on July 14, 2026. No more security patches, bug fixes, or technical support after that date. If your business still runs on-premises SharePoint, you have six weeks to choose a migration path and start moving.

This is not a theoretical deadline. SharePoint Server has been a consistent target for ransomware groups and state-sponsored attackers, specifically because organizations are slow to patch it. Once Microsoft stops issuing patches entirely, every future vulnerability becomes permanent. The good news: SMB-sized environments with under 500 users can complete a migration in two to four weeks if you start now and know what to prioritize.

What Stops Working After July 14

End of support means Microsoft stops delivering three things simultaneously: security updates, non-security hotfixes, and assisted technical support.

Security updates are the most critical loss. Microsoft’s Security Response Center publishes vulnerability details monthly, and attackers actively reverse-engineer patches to build exploits for the exact issues that were fixed. When your SharePoint server stops receiving those fixes, every disclosed vulnerability becomes an open door that will never close.

Beyond the security risk, compliance frameworks treat unsupported software as a finding. HIPAA’s Security Rule requires reasonable safeguards, and running software with known unpatched vulnerabilities fails that test. PCI DSS Requirement 6.3.3 mandates patching critical vulnerabilities within 30 days. CMMC requires vulnerability remediation within defined timelines. You cannot meet any of these requirements on software that no longer receives patches.

Cyber insurance carriers are tightening on this point as well. Multiple carriers now ask specifically about end-of-support software during underwriting, and running an unpatched SharePoint server could complicate a future claim.

The April 2 Retirement You Might Have Missed

Microsoft didn’t wait until July to start removing functionality. On April 2, 2026, SharePoint Add-Ins and Azure Access Control Service (ACS) authentication were retired across all SharePoint Server versions.

If your organization built custom solutions using the SharePoint Add-In model, those solutions stopped working two months ago. The same applies to any third-party tools that relied on ACS tokens for authentication. Common examples include custom document management workflows, third-party scanning integrations that route documents into SharePoint libraries, and automated approval processes built on the Add-In framework.

If you haven’t noticed the breakage, it’s possible nobody was using those features regularly. But check before you assume. Talk to the team members who built or requested those customizations and confirm whether their workflows are still functioning. A broken workflow that silently fails is worse than one that throws an error, because data may be missing for weeks before anyone notices.

Two Migration Paths

You have two options: move to SharePoint Online as part of Microsoft 365, or stay on-premises with SharePoint Server Subscription Edition (SPSE). Each path has clear tradeoffs.

SharePoint Online (Microsoft 365)

This is Microsoft’s recommended path and the right choice for most SMBs. SharePoint Online eliminates the server hardware, the patching cycle, and the IT overhead of running on-premises infrastructure. Microsoft manages updates, security patches, and capacity planning on your behalf.

The practical benefits for a 50 to 500 person business are significant. Automatic security updates mean you never face another end-of-support deadline for SharePoint. Storage starts at 1 TB per tenant plus 10 GB per user, which exceeds what most SMBs store on-premises. Integration with Microsoft 365 features like Teams, OneDrive, and Copilot is tighter than anything you can achieve with an on-prem server.

The tradeoffs are real, though. You need reliable internet connectivity for daily operations. Your data lives in Microsoft’s data centers rather than on hardware you control. If you have large volumes of data (over 500 GB), the migration itself takes longer because everything transfers over your internet connection.

If your business already uses Microsoft 365 for email, Teams, or OneDrive, you likely have SharePoint Online licenses included in your subscription already. Many businesses don’t realize they are paying for SharePoint Online while simultaneously maintaining on-premises servers that duplicate the same functionality.

SharePoint Server Subscription Edition (SPSE)

SPSE is the on-premises continuation of SharePoint Server. It follows a continuous update model similar to Windows, with feature updates and security patches delivered regularly. Unlike 2016 and 2019, there is no fixed end-of-support date as long as you keep current with updates.

This path makes sense in specific situations: air-gapped environments with no internet access, data sovereignty requirements that prevent cloud hosting, or regulatory mandates that require on-premises storage with physical control over the hardware.

For most SMBs, SPSE is the more expensive and labor-intensive option. You are still responsible for the server hardware, the OS patching, the SharePoint patching, the backups, and the disaster recovery plan. You also need someone with SharePoint Server administration skills, which is an increasingly specialized and expensive role to fill.

What to Audit Before You Start

A successful migration depends on knowing exactly what you have. Run through this checklist before you commit to a timeline or a vendor.

Storage volume. Measure the total size of your SharePoint content databases. This number determines how long the migration takes and whether you need to budget for additional SharePoint Online storage. Environments under 500 GB typically migrate in days, not weeks.

Custom workflows and automations. Inventory every SharePoint Designer workflow, Power Automate flow connected to SharePoint, and any custom code that reads or writes to your SharePoint environment. Solutions built on the Add-In model need to be rebuilt using the SharePoint Framework (SPFx) or replaced with Power Platform alternatives. This is usually the longest part of any migration project.

Third-party integrations. Identify every tool that connects to your SharePoint environment. Document scanners, CRM integrations, ERP document feeds, backup agents, and compliance tools all need reconfiguration or replacement when the target moves from an on-prem server to SharePoint Online.

Permissions and access controls. SharePoint on-premises uses Active Directory security groups. SharePoint Online uses Entra ID (formerly Azure AD). If your permission structure is complex, with nested groups, broken inheritance, and item-level permissions, the migration tool will carry it over, but the result needs careful validation afterward. Overly complex permissions are also a sign that cleanup should happen before migration, not after.

Site structure and content organization. Most on-prem SharePoint environments accumulate unused sites, orphaned document libraries, and content nobody has accessed in years. Migrating everything blindly wastes time and storage. Consider archiving content that hasn’t been accessed in 24 months rather than moving it to the new environment.

Realistic Timelines for SMB Environments

Standard SharePoint migrations take six to eighteen months for large enterprises. SMBs operate at a different scale. Here are realistic timeframes for businesses with 50 to 500 users and under 500 GB of content.

Assessment and planning: 1 week. Inventory your environment, measure storage, catalog customizations, and choose your migration path. This is the audit work described in the section above.

Pilot migration: 1 week. Migrate a single non-critical site to SharePoint Online and validate that content, permissions, and links work correctly. Use this as a test run for your migration tool configuration and to estimate the data transfer rate over your internet connection.

Production migration: 1 to 2 weeks. Migrate remaining sites in priority order, with critical business sites first and archival content last. Most migration tools support incremental syncs, so users can keep working on the on-prem server during the migration. A final delta sync catches any changes made during the transfer window.

Validation and cutover: 2 to 3 days. Run a final sync, validate content in SharePoint Online, update bookmarks and shortcuts, and redirect users to the new environment. Keep the old server online in read-only mode for 30 days as a safety net.

If you have extensive custom workflows that need rebuilding, add two to four weeks depending on complexity. This is the variable that stretches timelines, and the reason you should start the audit now rather than at the end of June.

How This Fits Your Broader IT Roadmap

SharePoint Server end-of-support doesn’t exist in isolation. It’s one piece of a broader set of Microsoft product retirements happening in 2026. Windows 11 24H2, Office LTSC 2021, and SQL Server 2016 all lose support later this year. If you are planning one migration, evaluate all of them together rather than running separate projects over the next six months.

The new SharePoint Online experience that Microsoft started rolling out in May 2026 also means your team will need to adjust to a redesigned interface regardless of when you migrate. Moving to SharePoint Online now means your team learns the new experience once, rather than adapting to it later after building habits on the old on-prem interface.

For businesses that work with a managed IT provider, the migration assessment and planning typically falls within your existing service agreement. Your MSP can pull the inventory, evaluate your customizations, run the migration tools, and handle the cutover without pulling your internal team away from their regular work.

The first step is knowing what you have. Pull your content database sizes, catalog your custom solutions, and list every tool that connects to SharePoint. That inventory drives every decision that follows, from choosing between SharePoint Online and Subscription Edition to setting a realistic migration timeline.

Six weeks is enough time to complete this migration for most SMB environments. It is not enough time to wait three weeks and then start.