If you are running SharePoint Server 2016 or 2019, support ended July 14, 2026,
so this is now a compliance decision rather than a roadmap item. Two destinations are supported:
SharePoint in Microsoft 365, or SharePoint Server Subscription Edition. Which one you can reach is set by your
custom code, data residency, and permissions model.

Key Facts

  • SharePoint Server 2016 and 2019 both left extended support on July 14, 2026. Neither
    receives updates of any kind, including security updates. (Microsoft Lifecycle)
  • Subscription Edition has no fixed end date, but each Public Update build is supported for
    one year from release. Being on SE is not the same as being supported.
  • The Microsoft SharePoint Migration Tool is free with an eligible Microsoft 365
    subscription, and migrates from SharePoint Server 2010, 2013, 2016 and 2019.
  • Paid tooling is optional, not assumed. ShareGate publishes $5,995, $9,995 and
    $17,995 per year by employee band; AvePoint
    does not publish pricing at all. Vendor pricing read July 22, 2026 and subject to change.
  • i3Solutions SharePoint developers, architects and consultants are 100% U.S.-based.
  • An enterprise SharePoint strategy assessment at i3Solutions typically runs four to six weeks
    with two to three consultants.

Where Your Environment Stands Today

Version Released Mainstream support ended Extended support ends Status
SharePoint Server 2016 May 1, 2016 July 13, 2021 July 14, 2026 Out of support
SharePoint Server 2019 October 22, 2018 January 9, 2024 July 14, 2026 Out of support
SharePoint Server Subscription Edition November 2, 2021 Modern Lifecycle Policy No fixed end date Supported, on a current build
SharePoint in Microsoft 365 Continuous Not applicable Not applicable Supported

Sources: Microsoft Lifecycle,
SharePoint Server 2016,
SharePoint Server 2019,
Subscription Edition.
Verified July 22, 2026.

Which Destination Can You Actually Reach?

If this is true of your environment Destination With analysis from i3Solutions
No data-residency constraint that blocks the cloud; customizations are replaceable SharePoint in Microsoft 365 The supported default. Most of the work is remediation, not movement.
Sovereignty, air-gap, or a contract clause naming on-premises Subscription Edition Supported, but only on a current build. Plan a patching rhythm, not a one-time upgrade.
Heavy farm solutions, InfoPath, or custom master pages Either, after disposition Decide per customization: rebuild, replace, or retire. Most legacy customizations do not move.
Regulated workload under CMMC, HIPAA or FedRAMP Depends on the boundary The destination is set by where the controlled data may live, which is settled before any content moves.

What Actually Consumes the Timeline

The migration tool is the cheap and predictable part. What extends an EOL migration is everything the tool
does not do: deciding what happens to each customization, redesigning permissions rather than copying a broken
inheritance model, handling sensitivity labels that do not migrate by default, and producing the reconciliation
evidence an auditor will ask for. Move the content without settling those, and you have relocated the problem.

One constraint worth checking before you plan around the free tooling: per Microsoft, if your on-premises
server is configured with multiple authentication providers including Windows authentication, SPMT does not
support Windows authentication, and you will need another method.

Frequently Asked Questions

Is SharePoint Server 2019 still supported?

No. SharePoint Server 2019 reached the end of Microsoft extended support on July 14, 2026, alongside
SharePoint Server 2016. Neither receives security updates.

Can we stay on-premises and remain supported?

Yes, by upgrading to SharePoint Server Subscription Edition, which follows the Modern Lifecycle Policy and has
no fixed end date. The condition is that the farm stays on a supported Public Update build, each of which is
supported for one year from its release.

Do we need a paid migration tool?

Often not. The Microsoft SharePoint Migration Tool is free with an eligible Microsoft 365 subscription and
covers a large share of straightforward Server-to-Online migrations. Paid tooling earns its cost on permission-heavy
restructuring, tenant-to-tenant work, and compliance reporting, not on volume alone.

What happens to our customizations?

They are disposed of individually, not migrated wholesale. Farm solutions, InfoPath forms, sandboxed
solutions and custom master pages are the usual offenders, and each is a rebuild, a replacement, or a
retirement decision made before content moves.

How does i3Solutions approach a SharePoint end-of-life migration?

i3Solutions runs the assessment before the movement. An enterprise SharePoint strategy assessment typically
runs four to six weeks with two to three SharePoint consultants, and settles destination, customization disposition, and
permissions design so the migration itself is execution rather than discovery. All i3Solutions SharePoint
developers, architects and consultants are 100% U.S.-based.

Running SharePoint Server 2016 or 2019 today?

You are unsupported now. A four to six week assessment settles which supported destination your environment can actually reach, and what has to be remediated before anything moves.

Schedule a SharePoint Risk & Roadmap Assessment

Building the internal case first? Talk to a senior SharePoint architect before you take it to committee.

Reviewed July 22, 2026 by Scott Singleton, Managing Consultant. Scott has spent more than 19 years at
i3Solutions and more than 30 years designing, developing, migrating, and implementing enterprise technology
solutions, with expertise grounded in SharePoint architecture and large-scale migration.
LinkedIn