Microsoft SharePoint Server 2016 and 2019 are reaching end of support on July 14, 2026. With the April 2026 feature retirement deadline now behind us, it's important to understand your current options and make informed decisions about your SharePoint environment's future.
The Retirement Timeline
Here are the key dates for SharePoint Server 2016 and 2019:
End-of-Support Date
July 14, 2026: SharePoint Server 2016 and SharePoint Server 2019 reach end of extended support
No more security updates or patches after this date
No more bug fixes or non-security updates
No standard Microsoft assisted support
No ongoing technical content updates for these product versions
Important to understand: Your servers will continue to function after July 14, 2026. This date marks when Microsoft stops providing updates and support, not when your environment stops working.
Feature Retirements That Have Already Occurred
April 2, 2026:
July 14, 2026 (Same date as server retirement):
December 31, 2026:
October 1, 2026:
Understanding Your Current Situation
Organizations running SharePoint Server 2016 or 2019 should understand two important timelines:
Feature Retirement Timeline (April 2, 2026 - Now Past)
SharePoint Add-Ins and SharePoint 2013 Workflows are no longer supported in SharePoint Online
This primarily affects migration paths to the cloud
Your on-premises environment continues to function normally
Server Support Timeline (July 14, 2026 - Approaching)
The date when SharePoint Server 2016 and 2019 become unsupported
After this date, no security patches or support from Microsoft
Your servers will continue to operate, but without vendor support
What this means for you: If you're planning to migrate to SharePoint Online, you'll need to rebuild workflows and add-ins using modern tools. If you're staying on-premises, you have clear options to remain supported beyond July 2026.
What "End of Support" Really Means
End of support doesn't mean your SharePoint environment stops working. Here's what actually happens:
What changes on July 15, 2026:
Microsoft stops releasing security patches for newly discovered vulnerabilities
No bug fixes for issues discovered after the support end date
No assisted support options from Microsoft
No online technical content updates
No compliance backing from Microsoft for the platform
What doesn't change:
Your servers continue to run
Your content databases still mount
Users can still browse sites and access documents
Existing functionality continues to operate
The real issue: Your environment becomes progressively more vulnerable as new security threats emerge with no vendor-provided fixes.
Why This Matters: The Business Impact
While the servers technically keep running, operating SharePoint Server 2016 or 2019 after July 2026 creates significant organizational risks:
Security Exposure
Unpatched vulnerabilities: New exploits discovered after July 2026 will remain permanently unaddressed
No vendor protection: Microsoft won't provide fixes for security issues
Prime attack target: Hackers specifically target unsupported platforms knowing vulnerabilities won't be patched
Increasing risk over time: The longer you run unsupported, the more exposed you become
Compliance and Audit Issues
Regulatory frameworks: HIPAA, GDPR, SOC 2, ISO 27001, and other compliance standards may flag unsupported software
Audit complications: Auditors often require formal risk exceptions for unsupported systems
Compensating controls: Running unsupported software may require expensive additional security measures
Cyber insurance: Insurance providers may raise rates or refuse coverage for unsupported platforms
Risk documentation: Organizations must formally document and accept the risk of running unsupported software
Operational and Integration Challenges
Modern tool integration: Newer Microsoft 365 features and security controls don't integrate with legacy SharePoint
Limited interoperability: Cloud-optimized tools increasingly fail to work with classic on-premises SharePoint
Rising maintenance costs: Supporting aging infrastructure becomes more expensive over time
Talent scarcity: Finding IT professionals skilled in legacy SharePoint becomes harder and more costly
Business Process Continuity
Current state for on-premises environments:
Your SharePoint 2016 or 2019 environment continues to function normally
All workflows, add-ins, and customizations work as they do today
After July 14, 2026, the environment continues to operate but without Microsoft support
For organizations migrating to SharePoint Online:
SharePoint 2013 Workflows need to be rebuilt using Power Automate
Custom add-ins need to be redesigned using modern frameworks
InfoPath forms should be converted to Power Apps or Microsoft Forms before July 14, 2026
This is part of modernization—an opportunity to improve processes while migrating
Migration Path Options
Organizations running SharePoint Server 2016 or 2019 have three primary migration paths:
Option 1: Migrate to SharePoint Online (Microsoft 365)
Best for:
Organizations with cloud-first strategies
Companies seeking to reduce on-premises infrastructure
Teams wanting access to continuous Microsoft innovation
Organizations needing modern collaboration capabilities
Key advantages:
No more server patching or infrastructure maintenance
Automatic updates and new features
Built-in security and compliance capabilities
Integration with Microsoft Teams, Power Platform, and Microsoft 365 suite
Scalability without hardware constraints
Migration considerations:
SharePoint 2013 Workflows can be rebuilt using Power Automate (often with improved functionality)
Custom add-ins can be redesigned using modern SharePoint Framework (SPFx)
InfoPath forms can be converted to Power Apps or Microsoft Forms
This is an opportunity to modernize and improve processes during migration
Modern tools offer better integration, mobile support, and ongoing innovation
Option 2: Upgrade to SharePoint Server Subscription Edition (On-Premises)
Best for:
Organizations with regulatory requirements to keep data on-premises
Companies with specific data sovereignty constraints
Environments with air-gapped or highly secure network requirements
Organizations needing local control over the platform
Key advantages:
Remains on-premises while staying on supported platform
Modern feature set compared to SharePoint 2016/2019
Active Microsoft support and security updates
More time to plan eventual cloud migration if desired
Critical considerations:
Still requires server infrastructure and maintenance
Ongoing hardware, patching, and operational costs
Limited integration with modern Microsoft 365 cloud services
Feature development focused primarily on SharePoint Online
Eventually will face another migration decision in the future
Option 3: Hybrid Approach
Best for:
Large organizations with complex requirements
Companies needing gradual migration over extended periods
Organizations with mix of workloads (some must stay on-premises, others can move to cloud)
How it works:
Run SharePoint Online and SharePoint Server Subscription Edition simultaneously
Gradually move workloads from on-premises to cloud over time
Maintain critical regulated data on-premises while moving collaboration to cloud
Key advantages:
Phased migration reduces risk and allows learning
Flexibility to keep specific workloads on-premises
Time to modernize complex customizations incrementally
Critical considerations:
More complex to manage (two environments)
Requires hybrid configuration and identity management
Higher short-term costs (running both environments)
Still need to address feature retirement deadlines for cloud workloads
Option 4: Alternative Platforms
Consider when:
SharePoint complexity exceeds business needs
Organization wants purpose-built intranet/collaboration platform
Current SharePoint usage is primarily basic intranet and document sharing
Alternatives include:
Dedicated intranet platforms (MangoApps, Simpplr, etc.)
Alternative collaboration suites
Custom-built solutions for specific needs
Your Options and Next Steps
If you're still running SharePoint Server 2016 or 2019, you have several viable paths forward. Here's how to approach your decision:
Step 1: Assess Your Current Situation (This Week)
Understand your environment:
Which SharePoint version are you running (2016, 2019, or mixed)?
How many sites and users do you have?
What are your most important business processes using SharePoint?
Identify what you're using:
Document custom workflows and their business purposes
List any custom add-ins or third-party solutions
Note any InfoPath forms still in use
Identify custom code solutions
Determine your priorities:
What are your compliance and security requirements?
Do you prefer cloud or on-premises solutions?
What's your timeline and budget for changes?
Step 2: Choose Your Path Forward (This Month)
You have three solid options, each appropriate for different situations:
Option 1: Upgrade to SharePoint Server Subscription Edition
Best if: You need to stay on-premises or want more time to plan cloud migration
Benefits: Remains supported, modern feature set, gives you time to plan properly
Timeline: Can typically be completed in 4-8 weeks with proper planning
This is a popular choice for organizations wanting to remain supported while taking time to plan future moves
Option 2: Migrate to SharePoint Online
Best if: Your organization is moving to cloud-first strategy
Benefits: No more server maintenance, continuous updates, modern collaboration tools
Timeline: Expect 6-12 months for proper migration with workflow/add-in rebuilding
Realistic approach: Many organizations stay on-premises while migrating (see Option 3)
Option 3: Continue on 2016/2019 While Planning Migration
Best if: You need time to plan and budget for your preferred long-term solution
What this means: Your environment continues to work, but without Microsoft support after July 14
Recommended: Document this decision with leadership, implement enhanced monitoring
Many organizations do this as a bridge to their chosen long-term solution
Plan to: Complete your migration within 12-18 months
Step 3: Begin Implementation (Within 60-90 Days)
If choosing Subscription Edition upgrade:
Engage Microsoft partner or internal team for upgrade planning
Schedule upgrade during maintenance window
Test critical workflows and customizations post-upgrade
This gives you a supported platform while planning future cloud migration if desired
If migrating to SharePoint Online:
Start with a pilot migration of 5-10 low-risk sites
Begin rebuilding critical workflows in Power Automate
Convert InfoPath forms to Power Apps gradually
Plan phased migration over 6-12 months
Accept that you may run on 2016/2019 during part of the migration
If continuing on current version:
Document formal decision with executive leadership
Implement enhanced security monitoring
Keep servers patched to latest available version
Create 12-18 month plan for eventual migration
Review security posture quarterly
Understanding Migration Timelines
It's helpful to understand realistic timeframes for SharePoint projects:
Subscription Edition Upgrade:
4-8 weeks for planning and execution
This is the fastest path to remaining on a supported platform
Minimal disruption to users
Buys time for longer-term planning
SharePoint Online Migration:
Small environments (< 50 sites): 3-6 months
Medium environments (50-500 sites): 6-12 months
Large environments (500+ sites): 12-18 months
Factors that affect timeline:
Volume of content to migrate
Number of custom workflows and add-ins to rebuild
Complexity of InfoPath forms
Available internal resources
Budget for external consultants
Good news: Many organizations successfully complete migrations while running on their current platform beyond the July 2026 date. While this means operating without vendor support for a period, it's a common and manageable approach when:
You implement proper security monitoring
You document the decision with leadership
You have a clear migration timeline
You maintain your servers at the latest available patch level
Common Pitfalls to Avoid
Organizations that struggled with previous Microsoft retirements often made these mistakes:
Waiting too long to start: Assuming "there's plenty of time" until it's too late
Underestimating complexity: Discovering hidden dependencies during migration execution
Ignoring feature retirement dates: Focusing only on July 2026 while missing April 2026 deadlines
Insufficient discovery: Not knowing what workflows, add-ins, and customizations exist
Last-minute resource scrambling: Competing for scarce consultant availability in late 2025/early 2026
Lack of governance: Making ad-hoc decisions instead of following structured migration plan
Inadequate testing: Rushing migrations without proper validation
Forgetting change management: Focusing on technology while neglecting user adoption
The Bottom Line
SharePoint Server 2016 and 2019 reach end of support on July 14, 2026. Your servers will continue to function, but Microsoft will no longer provide security updates or support.
You have clear options:
Upgrade to SharePoint Server Subscription Edition - Fastest path to remaining supported (4-8 weeks)
Migrate to SharePoint Online - Modern, cloud-based collaboration (6-12 months realistic timeline)
Continue on current version while planning - Document the decision, enhance monitoring, and plan your long-term strategy
Important perspective: Many organizations find themselves in similar situations during Microsoft product lifecycles. The key is making an informed decision and having a plan. There's no single "right" answer—the best choice depends on your organization's specific needs, resources, and priorities.
What happens after July 14, 2026:
Your SharePoint environment continues to operate normally
No new security patches will be available from Microsoft
You'll need to implement compensating security controls
Many organizations successfully manage this transition period while completing migrations
Your next step: Schedule time with your team this week to assess your environment and discuss which option best fits your organization. Whether you choose to upgrade to Subscription Edition, begin a cloud migration, or continue on your current platform while planning—having a documented strategy is what matters.
Remember: This is a common technology lifecycle transition. Organizations work through these regularly, and there are proven approaches for each path forward. Focus on making the choice that's right for your specific situation rather than trying to meet an arbitrary deadline that may not align with your organization's needs.
Join the conversation! Your thoughts help the community grow.