SharePoint Hybrid to Cloud: The Final Phase of the Hybrid Era

Why Hybrid SharePoint Has an End-of-Life Problem

Hybrid SharePoint configurations — where an on-prem farm coexists with SharePoint Online via User Profile Replication, hybrid search, hybrid taxonomy, and OneDrive redirection — made sense for the better part of a decade. They let organizations modernize incrementally without a cliff migration.

That decade ends on July 14, 2026. Any hybrid configuration whose on-prem side is SharePoint Server 2016 or 2019 becomes unsupported on the on-prem side at that date. Microsoft treats this as breaking the supported hybrid topology — a technically running but officially unsupported configuration.

Organizations now face two choices: upgrade the on-prem side to SharePoint Server Subscription Edition (preserving hybrid for the subset of content that truly needs to stay on-prem), or collapse hybrid entirely and become cloud-only. This article is the playbook for the second path, which is the economic choice for 80 to 90 percent of hybrid organizations.

It pairs with the July 14, 2026 end-of-support pillar decision guide, the migration checklist, and the migration gotchas reference.

The Six Hybrid Components

Hybrid SharePoint is not one thing. It is six distinct integrations, each configured independently, each with its own decommissioning sequence:

• User Profile Replication — on-prem UPA pulls from AD and pushes profile properties to SharePoint Online profiles.
• Hybrid Taxonomy — managed-metadata term groups replicated between on-prem and cloud term stores.
• Hybrid Search — either cloud-hybrid search (on-prem content crawled into the cloud index) or federated search (queries federated between on-prem and cloud).
• Hybrid BCS (Business Connectivity Services) — on-prem external content types exposed in SharePoint Online.
• OneDrive Redirection — on-prem My Sites host redirects users to OneDrive for Business in the cloud.
• Hybrid App Launcher and Navigation — unified waffle menu and site navigation across on-prem and cloud.

Each component has to be decommissioned in a specific order. Skipping the order creates orphaned configurations and broken user experiences.

The Recommended Decommissioning Sequence

Step 1 — Finish Content Migration Including My Sites

Before touching any hybrid plumbing, complete 100 percent of content migration. That includes My Site content from every active user. ROT cleanup of ex-employee My Sites (check legal-hold status first) happens in parallel.

Step 2 — Decommission Hybrid BCS

Inventory every external content type exposed via hybrid BCS. Migrate the data sources to a cloud-native pattern (Microsoft Graph connector, Power Platform Dataverse, or direct Azure SQL / Dataverse integration). Remove the hybrid BCS connection after the migration is validated.

Step 3 — Decommission OneDrive Redirection

After all users My Site content has migrated to OneDrive for Business:

• Remove the OneDrive redirection configuration in SharePoint Central Administration.
• Verify users now land on OneDrive for Business when they click the OneDrive icon.
• Decommission the on-prem My Site host.

Step 4 — Decommission Hybrid Search

For cloud-hybrid search: stop the cloud search service application crawler on the on-prem farm. The crawler stops pushing new content to the cloud index. Existing indexed content remains available in cloud search.

For federated search: remove result sources in the SharePoint Online search admin that point to the on-prem farm. Update any query rules or promoted results that referenced the federated results.

Step 5 — Decommission Hybrid Taxonomy Replication

Stop the taxonomy replication timer job on the on-prem farm. Validate that the cloud term store is the authoritative source going forward. Assign a cloud term-store owner responsible for ongoing governance.

Step 6 — Decommission User Profile Replication

On-prem UPA has been synchronizing profile properties to SharePoint Online. After content migration is complete, the cloud profile becomes the authoritative record. Stop the UPA replication. Validate that Azure AD Connect (or equivalent) is the cloud profile source.

Step 7 — Decommission Hybrid App Launcher

The hybrid app launcher merged on-prem and cloud app tiles into a unified waffle menu. After all workloads are cloud-only, remove the on-prem configuration and confirm users see only cloud app tiles.

Step 8 — Retire the On-Prem Farm

• Stop all SharePoint timer jobs.
• Dismount content databases (preserve backups per IT retention policy and legal holds).
• Shut down SharePoint application servers.
• Retire the SQL Server instances hosting content databases.
• Decommission the farm per IT asset-retirement policy.

Common Hybrid-Specific Pitfalls

Pitfall 1 — Identity Federation Confused with SharePoint Hybrid

SharePoint hybrid runs on top of the identity layer (Azure AD Connect plus ADFS, Password Hash Sync, or Pass-Through Authentication). The identity layer persists and is used by Exchange Online, Teams, and every other Microsoft 365 workload. Do not unwind identity federation as part of the SharePoint project.

Pitfall 2 — OneDrive Redirection Removed Too Early

Removing OneDrive redirection before all users My Site content is migrated creates a user-experience gap. Always finish My Site content migration before removing redirection.

Pitfall 3 — Cloud-Hybrid Search Index Retention

When you stop cloud-hybrid search crawling, the existing indexed content remains in the cloud search index. Users can still find it. Occasionally organizations want a clean cloud-only index. In that case, manually remove the on-prem content source from the cloud search admin center.

Pitfall 4 — Hybrid Taxonomy Bidirectional Sync Confusion

In some hybrid configurations, taxonomy replicates bidirectionally. If the on-prem term store has changed more recently than the cloud, stopping replication can freeze the cloud store in a slightly stale state. Validate which store is authoritative and reconcile before stopping replication.

Pitfall 5 — BCS External Content Types Forgotten

External content types often power behind-the-scenes integrations that nobody documented. Inventory these explicitly in assessment and migrate them (typically to a Microsoft Graph connector or Dataverse) before removing hybrid BCS.

Edge Case — Keeping Some Content On-Prem

If the organization has legitimate requirements to retain some SharePoint content on-prem (air-gapped networks, data sovereignty in a country without a Microsoft 365 data-residency option, offline legal-hold archives):

• Upgrade the on-prem farm to SharePoint Server Subscription Edition first. This preserves vendor support past July 14, 2026.
• Maintain the hybrid configuration indefinitely with SE on-prem and SharePoint Online in the cloud.
• Periodically reassess whether the on-prem subset has shrunk enough to fully collapse to cloud.

Continuing hybrid with an unsupported SP2016 or SP2019 on-prem side past July 14, 2026 is not a defensible posture.

Timeline for Hybrid-to-Cloud Collapse

For a typical 2,000-seat hybrid organization:

• Weeks 1 to 4: Assessment, including explicit hybrid-component inventory and BCS/UPA/search configuration capture.
• Weeks 5 to 8: Target-state design. Plan for cloud-only, including where the six hybrid components will land (or retire).
• Weeks 9 to 12: Pilot migration and hybrid-component pilot-decommission validation.
• Weeks 13 to 22: Production waves including My Site migration.
• Weeks 23 to 24: Hybrid decommissioning in the documented 8-step sequence.
• Weeks 25 to 26: On-prem farm retirement, hypercare, program close.

For larger enterprises (5,000 to 50,000 seats), extend by 4 to 12 weeks proportionally. The hybrid-decommissioning steps themselves take 2 to 4 weeks regardless of seat count — they are configuration, not content, work.

Post-Decommissioning Verification

After completing all eight decommissioning steps and retiring the on-prem farm, run a formal verification pass. This verification becomes the audit evidence that the hybrid topology has been cleanly decommissioned.

Verification Checklist

• Confirm no SharePoint on-prem server process is running on any retired server (confirm via process listing or equivalent monitoring).
• Confirm no content databases remain mounted anywhere in the organization's SQL estate.
• Confirm the SharePoint Online Admin Center no longer shows hybrid search result sources, hybrid BCS connections, or hybrid UPA replication jobs.
• Confirm users' OneDrive icons land on OneDrive for Business (spot-check across departments).
• Confirm the cloud term store is the sole authoritative term store (no residual on-prem sync artifacts).
• Confirm external sharing settings in the destination tenant reflect the target-state policy, not residual hybrid defaults.
• Confirm DNS records for old on-prem SharePoint URLs resolve either to the new destination or to a defined deprecation page.
• Confirm the on-prem farm's IIS application pools are stopped, SharePoint services are disabled, and Windows services related to SharePoint Timer, Search, and Admin are disabled.

Compliance and Evidence Artifacts

For organizations in regulated industries, preserve the following artifacts from the decommissioning process:

• Final content-migration reconciliation report (source item counts vs. destination item counts, per site collection).
• Timestamped decommissioning log showing each hybrid component stopped, with operator sign-off.
• Final backup of content databases, dated and stored per legal-hold and retention policies.
• SharePoint farm asset retirement documentation matching the IT asset-management system.
• A formal program-close document signed by the migration program sponsor and the compliance officer.

These artifacts are routinely requested in the next SOC 2 Type II, HITRUST, FedRAMP, or ISO 27001 audit following the migration. Teams that fail to preserve them pay for it in auditor interview time twelve months later.

Parallel Decommissioning Risk

Running the eight decommissioning steps in parallel to save time is tempting and is the most common cause of post-decommissioning pain. OneDrive redirection removed before My Site content migration completes produces a broken user experience. Hybrid search stopped before federated queries are rerouted produces missing search results. UPA replication stopped before the cloud profile is validated can freeze profile properties in a stale state.

The sequence is sequential for a reason. Respect it. In a 2,000-seat migration, executing the eight steps serially adds about two weeks to the timeline — trivial against the risk of skipping the sequence.

Related Reading

• SharePoint Server 2016 and 2019 End of Support — July 14, 2026 Decision Guide (pillar)
• SharePoint Server 2016 to Online Migration Checklist
• SharePoint Server 2019 Post-EOS Security Risk Assessment
• SharePoint Server Migration Gotchas — 15 Common Mistakes That Kill Projects

Frequently Asked Questions

What is special about migrating a hybrid SharePoint configuration vs. a pure on-prem farm?

Hybrid has six interconnected components — User Profile Replication, hybrid search, hybrid taxonomy, hybrid BCS, OneDrive redirection, and hybrid app launcher.

Can a hybrid configuration remain after July 14, 2026?

Only if the on-prem side is SharePoint Server Subscription Edition.

What happens to OneDrive redirection during migration?

Migrate all My Site content to OneDrive for Business, then remove the OneDrive redirection configuration, then decommission the on-prem My Site host.

How does hybrid search decommissioning work?

For cloud-hybrid search, stop the on-prem crawler. For federated search, remove result sources pointing to on-prem. Decommission only after content migration is 100 percent complete.

What is the sequence for decommissioning hybrid components?

Complete content migration; decommission hybrid BCS; decommission OneDrive redirection; decommission hybrid search; decommission hybrid taxonomy; decommission User Profile Replication; decommission hybrid app launcher; retire on-prem farm.

Do we need to preserve the hybrid configuration if some content stays on-prem?

Only if the on-prem side is upgraded to SharePoint Server Subscription Edition.

How do identity federation and hybrid Azure AD affect the migration?

Identity federation persists and is used by every Microsoft 365 workload. Do not unwind identity federation as part of the SharePoint migration project.