---
title: "Sitecore XP End of Support 2026: The Version-by-Version Guide"
slug: sitecore-xp-end-of-support-2026-the-version-by-version-guide
date: 2026-10-12
author: Abdul Wahab
categories: [Sitecore, Migration Guide]
excerpt: "Sitecore XP 10.0 and 10.1 lose Extended Support on 31 Dec 2026. Here's the version-by-version timeline, the June 2026 support change, and what to do next."
tldr: "Sitecore XP 10.0/10.1 Extended Support ends 31 Dec 2026 — no security patches at any price after that. Since 1 June 2026, security updates are already a paid add-on for all XP versions in Extended Support. Start scoping now."
canonical: https://clonepartner.com/blog/sitecore-xp-end-of-support-2026-the-version-by-version-guide
---

# Sitecore XP End of Support 2026: The Version-by-Version Guide


# Sitecore XP End of Support 2026: The Version-by-Version Guide

**Sitecore XP 10.0 and 10.1 reach the end of Extended Support on 31 December 2026.** After that date, security patches are not available at any price — not even through a paid arrangement. And since 1 June 2026, a separate change already made security updates and production incident support a paid add-on for every XP version still in Extended Support.

The mistake is treating these as one event. They are three different clocks. **1 June 2026** changed what Extended Support includes. **10 November 2026** ends support for .NET 8 and .NET 9, which affects your Sitecore Identity Server and any headless components before the CMS deadline arrives. **31 December 2026** ends Extended Support for XP 10.0 and 10.1, after which security updates are unavailable.

This guide lays out the exact deadlines by version, explains the support-model change, flags the .NET runtime and infrastructure compatibility constraints, and walks through migration paths with explicit decision criteria.

For a broader view of every major product retirement hitting in 2026, see our [Complete EOL Calendar](https://clonepartner.com/blog/blog/software-end-of-life-2026-the-complete-eol-calendar).

## Which Sitecore XP Version Are You Running?

Confirm your exact version before anything else. The support runway differs by minor version, and "we're on 10" is not specific enough to make a decision.

Three ways to check:

1. **Content Editor → System Menu → License Details.** The dialog shows your exact version and revision number.
2. **Version XML file.** Browse to `/sitecore/shell/sitecore.version.xml` on your CM server. This returns the version without requiring a CMS login.
3. **Sitecore.Kernel.dll.** Navigate to the `/bin` folder, open the file's Properties → Details tab. The Sitecore Product Version is visible there.

```text
/sitecore/shell/sitecore.version.xml
/sitecore/logs/*.txt
/sitecore/shell/patches
/sitecore/shell/hotfixes
```

Beyond the core version, record your installed modules, patches, and hotfixes. Sitecore logs record installed modules, and patch and hotfix metadata lives under the `patches` and `hotfixes` folders. ([support.sitecore.com](https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB0891209)) This matters because Sitecore's commercial modules generally follow the support phase of the version they run on, and upgrade assistance only applies when you use official instructions to move to a version in Mainstream Support.

Write down the major.minor version (e.g., 10.1, 10.2, 10.4) and the full update level. That combination determines every deadline below.

## Sitecore XP Support Dates: The Version-by-Version Runway

Sitecore's lifecycle knowledge base article KB0641167 records the support dates for each version. ([support.sitecore.com](https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB0641167)) Here is the consolidated picture:

| Version | Mainstream Support Ends | Extended Support Ends | Sustaining Support Ends | Current Phase |
|---------|------------------------|----------------------|------------------------|---------------|
| **XP 9.x** | Ended | Ended (9.2/9.3: Dec 2025) | Dec 2027 | Sustaining — no patches at any price |
| **XP 10.0** | Ended (Dec 2023) | **31 Dec 2026** | Dec 2028 | Extended (paid security updates) |
| **XP 10.1** | Ended (Dec 2023) | **31 Dec 2026** | Dec 2028 | Extended (paid security updates) |
| **XP 10.2** | Ended (Dec 2024) | **31 Dec 2027** | Dec 2029 | Extended (paid security updates) |
| **XP 10.3** | Ended (Dec 2025) | **31 Dec 2028** | Dec 2030 | Extended (paid security updates) |
| **XP 10.4** | **31 Dec 2027** | **31 Dec 2030** | Dec 2032 | Mainstream |
| **XP 10.5** | **31 Dec 2029** | **31 Dec 2032** | Dec 2034 | Announced; release date August 2026 (unshipped at time of writing) |

Support for service packs (like 10.4.1) follows the parent version's lifecycle. Sitecore module support matches the version they're installed on unless stated otherwise.

The key takeaway from this table: **only version 10.4 remains in Mainstream Support today, and that window closes at the end of 2027.** Version 10.5 has been announced with an August 2026 release date per KB0641167, but had not shipped at time of writing — see the contingency discussion in the migration paths section below.

If you are on 9.2 or 9.3, both lost Extended Support on 31 December 2025 and entered Sustaining with no security patches available. There is no action left to take within the Sitecore support framework.

## What Changed on 1 June 2026?

**Sitecore's Extended Support phase no longer includes security updates or production incident support by default.** These capabilities moved from the "included" column to a paid add-on for every XP version in Extended Support. ([support.sitecore.com](https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB0641167))

**What remains included in Extended Support at no extra charge:**

- Documentation, knowledge base, and community forums
- Assistance with product version upgrades (limited to moving to a version in Mainstream Support using official instructions)

**What now requires a separate paid arrangement:**

- Security updates and fixes
- Assistance with production incidents
- Hotfixes and patches for defects (already paid before June 2026)
- Assistance with installation and development errors (already paid before June 2026)

There is a further overlooked constraint in Sitecore's lifecycle table: **compatibility fixes for supported technology platforms** are listed as included only in Mainstream Support, not Extended or Sustaining. In practice, that means being in Extended Support does not guarantee a safe path for OS, SQL Server, container, or runtime modernization — those compatibility changes require a version upgrade, not just a support contract.

**The June 2026 change does not affect Mainstream Support**, where 10.4 lives through end of 2027. If you are on 10.4, your security update entitlement is unchanged today. When 10.4 enters Extended Support in 2028, it will be subject to whatever model is in effect at that point.

The practical translation: for versions 10.0 through 10.3, "supported" now describes a service tier, not a free entitlement. Budget for security patch access as a separate line item rather than assuming it is included in standard licensing.

> [!WARNING]
> **Check your agreement.** The specifics of what you pay depend on your existing Sitecore contract. What applies to your estate is a question for your account representative. Do not budget for standard licensing renewals assuming security patches are included.

## What Happens on 31 December 2026?

**Sitecore XP 10.0 and 10.1 drop from Extended Support into Sustaining Support.** Both leave Extended Support on 31 December 2026, entering a phase with no security updates listed at any price — no paid arrangement, no escalation path, nothing.

**Sustaining Support** is not operational support. While the distinction between [end of support and end of life](https://clonepartner.com/blog/blog/end-of-support-vs-end-of-life-what-the-terms-actually-mean) means your Sitecore instance will still boot and Sitecore does not remotely disable anything, you will be running unpatched software with known public vulnerabilities, and that exposure compounds with every month.

To understand the real-world risk: Sitecore XP has a documented history of high-severity CVEs. **CVE-2021-42237** (CVSS 9.8) allowed unauthenticated remote code execution via a deserialization flaw in Sitecore XP 7.5 through 9.1. **CVE-2019-9874** (CVSS 9.8) enabled remote code execution via insecure deserialization in the `Sitecore.Security.AntiCSRF` module. Both were actively exploited in the wild. After Extended Support ends, any equivalent vulnerability in XP 10.0 or 10.1 will not receive a patch — the exposure window becomes permanent rather than temporary.

For compliance-sensitive environments — PCI DSS, SOC 2, HIPAA, ISO 27001 — running a version with no available security patches typically produces audit findings. The version is flagged not because something has gone wrong, but because nothing *can* be fixed. Because Sitecore sits at the edge of your network handling public web traffic and user data, an unpatched RCE or injection vulnerability carries maximum blast radius. CISA explicitly warns that unsupported software remains permanently exposed to known vulnerabilities, recommending isolation, reduced exposure surface, and data access restrictions as damage-containment measures rather than solutions. ([cisa.gov](https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-278a))

## The .NET 8 and .NET 9 Deadline Lands First

Before Sitecore's own 31 December date, a dependency underneath it reaches end of support. [**.NET 8 and .NET 9 reach end of support on 10 November 2026.**](https://clonepartner.com/blog/blog/net-8-9-end-of-support-the-cms-deadline-everyone-is-missing) After that date, Microsoft will no longer provide servicing updates, security fixes, or technical support for these runtimes.

This requires a precise distinction. **Sitecore XP itself runs on .NET Framework 4.8**, a separate, older runtime with its own lifecycle that is not affected by the November 2026 deadline. But Sitecore Identity Server 8.x is built on .NET 8 and cannot simply be moved to newer .NET versions such as .NET 10. Identity Server handles authentication for the Sitecore shell and xConnect. ([support.sitecore.com](https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB0087164))

**The version mapping:**

- **Sitecore Identity Server 8.x** — supports XP versions 9.1 through 10.4; built on .NET 8
- **Sitecore Identity Server 9.x** — supports XP versions 10.3 through 10.5; built on a newer runtime stack

If you are on XP 10.0 or 10.1, your Identity Server is running on .NET 8. After 10 November 2026, it will continue to function, but no new security updates will be issued for the runtime. Your authentication layer becomes unpatched **seven weeks** before Sitecore's own Extended Support deadline.

**xConnect**, which runs as a separate IIS site and handles the xDB data collection and processing pipeline, also runs on .NET Framework 4.8 for the core service but uses .NET for its client SDK components. If you have headless rendering hosts or .NET Core client applications running on .NET 8 or .NET 9, those are also affected by the 10 November date — regardless of where the core XP branch sits in its support lifecycle.

**The natural upgrade target for components moving off .NET 8 or .NET 9 is .NET 10**, which released in November 2025 as an LTS version with support through May 2028. Components that can be upgraded to .NET 10 (rendering hosts, custom microservices, API layers) should be scoped for that upgrade independently of whatever decision you make about the core XP platform.

> [!NOTE]
> **Two clocks, one calendar.** The .NET 8 end-of-support date (10 November 2026) and the Sitecore XP 10.0/10.1 Extended Support date (31 December 2026) are related but separate. If your security posture requires supported runtimes, the effective deadline for Identity Server is 10 November, not 31 December.

## Infrastructure Compatibility Constraints

Support dates are only half the picture. Sitecore's compatibility table reveals hard constraints that affect infrastructure modernization independently. ([support.sitecore.com](https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB0087164))

| Version | Windows Server 2022 | SQL Server 2022 | Note |
|---------|---------------------|-----------------|------|
| **10.0 / 10.1** | No | No | No LTSC 2022 container images |
| **10.2** | Containers only | No | Already outside Mainstream Support |
| **10.3** | Yes | No | Already outside Mainstream Support |
| **10.4** | Yes | Yes | Sitecore Experience Commerce not supported |

**Sitecore XP 10.0 and 10.1 do not support Windows Server 2022 or SQL Server 2022.** If your infrastructure roadmap includes OS or database modernization, calendar runway alone is misleading — you cannot modernize the underlying stack without changing the Sitecore version first.

If you run Sitecore in containers, the constraint is sharper. Sitecore publishes XP container images with monthly LTSC base OS updates only until the end of the product's Extended Support. XP 10.0/10.1 remain on LTSC 2019 images only, through December 2026, with no LTSC 2022 images for those branches. ([support.sitecore.com](https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB1000600))

The ecosystem follows these dates. As a concrete example: Coveo's official deprecation notice states that support for Coveo for Sitecore targeting 10.1 and older ends when Sitecore's Extended Support ends on 31 December 2026. ([docs.coveo.com](https://docs.coveo.com/en/q62g0532/)) Your module and add-on inventory matters, not just the core CMS version.

## How Does Each Version's Runway Compare?

### If you are on XP 9.x

You are already in Sustaining Support with no security patches available at any price. There is no action left to take within the Sitecore support framework. Scoping for upgrade or migration should already be underway.

### If you are on XP 10.0 or 10.1

Treat 2026 as a decision year, not a cleanup item for 2027. Extended Support ends on 31 December 2026, and the .NET 8 Identity Server deadline hits on 10 November — seven weeks earlier. Budget cycles and approval windows tend to consume more of the remaining months than the technical work does. Use the decision matrix in the next section to evaluate your path.

### If you are on XP 10.2

Extended Support runs through 31 December 2027, Sustaining through 31 December 2029. The June 2026 change already applies — security patches and production incident support are paid add-ons now. You have time, but the cost structure has changed even before the deadline pressure arrives.

### If you are on XP 10.3

Same cost economics as 10.2, with more calendar. Extended Support runs through 31 December 2028, Sustaining through 31 December 2030. You have the longest window of any version currently in Extended Support, but the June 2026 change means you are paying more for less than you were before.

### If you are on XP 10.4

You are in Mainstream Support through 31 December 2027, with Extended Support through 31 December 2030. The June 2026 support-model change does not affect you yet. This is the most comfortable position in the XP installed base — but not automatically the end state.

Two specific constraints apply: **Sitecore Experience Commerce is not supported for XP 10.4 and later**, so teams running XP plus XC cannot treat 10.4 as a like-for-like landing zone. ([doc.sitecore.com](https://doc.sitecore.com/xp)) And 10.4 does not resolve the 10 November 2026 .NET 8/.NET 9 deadline for adjacent headless components or Identity Server 8.x.

## Migration Path Decision Matrix

The right destination depends on what you actually run Sitecore XP *for*. The following matrix maps key variables to each migration path. Use it to identify which path is viable before evaluating effort or cost.

| Decision Variable | Upgrade to XP 10.4/10.5 | Migrate to XM Cloud | Evaluate Alternative Platform |
|---|---|---|---|
| **Heavy xDB personalization / MA / EXM** | ✅ Preserves these | ❌ Requires CDP + Personalize (separate products) | ❌ Requires custom rebuild |
| **Sitecore Experience Commerce (XC)** | ❌ XC not supported on 10.4+ | ❌ XC not available in XM Cloud | ✅ Evaluate commerce-native platforms |
| **Existing MVC presentation layer** | ✅ Preserved | ❌ Must refactor to JSS or .NET Core headless | ⚠️ Depends on target |
| **Custom Solr indexes** | ✅ Preserved | ❌ Not supported in XM Cloud | ⚠️ Depends on target |
| **Sitecore Forms** | ✅ Preserved | ❌ Not directly supported | ⚠️ Depends on target |
| **XP 10.0 or 10.1 as starting point** | ✅ Supported upgrade path | ✅ XM-to-XM Cloud migration tool supports 10.1+ | ✅ Any version viable |
| **Compliance requirement for patched software** | ✅ Resolves immediately | ✅ Resolves immediately | ✅ Resolves immediately |
| **Budget for infrastructure ownership** | ❌ Continues on-prem / managed cloud costs | ✅ Eliminates infrastructure layer | ⚠️ Depends on target |
| **Timeline under 6 months** | ⚠️ Feasible for minimal customization | ❌ Unlikely for full refactor | ❌ Unlikely |

**Choose Upgrade to XP 10.4/10.5 if:** xDB personalization, Marketing Automation, or EXM is core to your business; your team has deep Sitecore expertise; and you need the fastest path back to Mainstream Support without a frontend rewrite.

**Choose XM Cloud if:** your frontend can be rebuilt headless (or is already headless); you have no XC dependency; and you want to eliminate infrastructure management long-term. Factor in that xDB analytics and personalization do not exist in XM Cloud — they migrate to Sitecore CDP and Personalize, which carry separate licensing.

**Evaluate alternative platforms if:** you are already reconsidering Sitecore's total cost of ownership; your XC dependency makes 10.4+ a dead end; or your content model is simple enough that a lighter CMS (Contentful, Sanity, Storyblok) would eliminate complexity rather than preserve it.

A one-vendor business case — evaluating only the Sitecore SaaS path — is not a complete business case. The decision should explicitly compare at least two options with total cost of ownership estimated over three years.

## Path 1: Upgrade within Sitecore XP

Upgrading from 10.0 or 10.1 to 10.4 gets you back into Mainstream Support through 2027. Version 10.5, if it ships on the announced August 2026 schedule, extends Mainstream Support through 2029.

**If XP 10.5 slips past December 2026:** Teams that planned around 10.5 as their landing zone face a gap. The safe contingency is to scope and budget for 10.4 as the primary target, treating 10.5 as an optional upgrade once released. A 10.4 deployment can be upgraded to 10.5 after release — this is a lower-risk approach than waiting on an unshipped version with a hard deadline approaching.

This is a platform upgrade, not a data migration. The project involves code changes, configuration updates, infrastructure adjustments, and testing. Upgrade complexity correlates directly with customization depth:

- **Low customization** (standard templates, minimal custom renderings, no custom xDB facets): Upgrade effort typically 4–8 weeks including testing
- **Medium customization** (custom renderings, some pipeline processors, standard modules): 8–16 weeks
- **High customization** (deep xDB facets, custom xConnect models, complex search integrations, non-standard modules): 16+ weeks; evaluate whether migration to XM Cloud has lower net cost

Note that Sitecore Identity Server must also be upgraded in parallel. Moving from Identity Server 8.x (on .NET 8) to Identity Server 9.x (on a newer runtime, supporting XP 10.3+) is required to address the 10 November 2026 .NET deadline for teams landing on 10.3 or above.

## Path 2: Migrate to Sitecore XM Cloud

XM Cloud is a SaaS-only, headless CMS. It is not a lift-and-shift from XP. Sitecore's own migration FAQ confirms that XM Cloud does not support Content Delivery servers, existing MVC solutions must be refactored to JSS or another headless/.NET Core approach, and capabilities like custom Solr indexes and Sitecore Forms do not carry over. MVC solutions can continue on Sitecore Managed Cloud. ([developers.sitecore.com](https://developers.sitecore.com/learn/faq/xm-personalize/migration))

**xDB analytics and personalization rules do not exist in XM Cloud.** They migrate to Sitecore CDP and Personalize, which are separate products with different architectures, APIs, and licensing. If your business depends on xDB behavioral data and segment-based personalization, plan for this as a distinct workstream with its own data mapping requirements, not a feature flag you enable post-migration.

Sitecore provides official tooling for content migration:

- **XM to XM Cloud Content Migration Tool** — moves content, media, and user data from an XM on-prem instance to XM Cloud, supporting versions 10.1 and later
- **xDB to CDP Migration Tool** — migrates known contacts, facets, and contact lists from XP to Sitecore CDP using Sitecore Connect, supporting all XP versions from 9.0 onwards; custom facets require explicit mapping before migration

([developers.sitecore.com](https://developers.sitecore.com/downloads/xm-cloud))

Running a hybrid state — Sitecore XP handling content delivery while XM Cloud is built out in parallel — is technically feasible and is the typical approach for teams with active editorial workflows. In this model, the XP instance continues serving production traffic until cutover, while the new headless frontend is built and content is migrated incrementally. The critical planning requirement is keeping XP in Extended Support (or on a paid security update agreement) through the full duration of the parallel run, which may extend well past the initial December 2026 deadline.

## Path 3: Evaluate Alternative Platforms

Some organizations use this support deadline to evaluate the market entirely. Common destinations include Optimizely, Adobe Experience Manager, Kentico Xperience (note that Xperience 13 [reaches end of support in 2026](https://clonepartner.com/blog/blog/kentico-xperience-13-end-of-support-2026-what-actually-changes)), and headless CMS platforms like Contentful, Sanity, or Storyblok. Check our [CMS & DXP End-of-Support Calendar](https://clonepartner.com/blog/blog/cms-dxp-end-of-support-calendar-20262027) to ensure your target platform version provides sufficient runway.

This path requires stripping presentation data from content data. Sitecore stores content alongside presentation rules in the `__Renderings` field using XML layout definitions. Moving to a pure headless CMS or a different monolith requires extracting only the raw content, cleaning the HTML, and mapping it to the target platform's content model. The primary challenge is translating Sitecore's highly relational Item tree — where every page, component, and media asset is a node with a unique GUID — into the target platform's architecture.

## What Data Needs to Move?

Every Sitecore XP migration involves several data categories, each with different extraction characteristics and failure modes:

- **Content items and templates.** The Sitecore content tree: page items, data sources, dictionary entries, and template definitions. Extraction via Sitecore CLI, Unicorn serialization, or the Item Web API.
- **Media library.** Sitecore stores images and documents as binary blobs within the SQL database rather than as flat files. Extraction requires querying the Sitecore API to reconstruct the media tree, downloading the binaries, maintaining the folder hierarchy, and uploading them to your new asset manager (Cloudinary, AWS S3, or the target CMS media library).
- **xDB contact and interaction data.** If you use xDB for personalization, marketing automation, or analytics, this data either moves to Sitecore CDP or gets archived. Custom facets need explicit mapping. The volume can be substantial — large XP deployments accumulate millions of contact records and interaction events.
- **xConnect service data.** xConnect runs as a separate IIS site and maintains its own collection database and search index. It is not simply extracted along with CMS content — it requires its own migration tooling and schema mapping.
- **Users and roles.** Sitecore membership data, role assignments, and access rights.
- **Workflow state and publishing restrictions.** Content governance metadata that needs mapping to the target platform's equivalent.
- **URL structure and redirects.** Preserving SEO equity requires a redirect map from old URLs to new ones.

If your migration plan treats content migration and customer-data migration as one task, it is already under-scoped. The transfer preference for structured content is always API first, then serialized formats (JSON/YAML), then CSV as a fallback.

### The dynamic link problem

Sitecore does not store standard URLs in its rich text fields. It uses internal GUIDs formatted like `~/link.aspx?_id=1234567890ABCDEF`. If you export content as raw SQL or basic CSVs, every internal link on your new site will be broken. These GUIDs must be resolved against the content tree and translated into absolute or relative URLs matching your new routing structure before the data is loaded into the target CMS. This resolution step is not optional and is frequently omitted from initial migration scopes.

### Decoupling presentation from content

Sitecore Items contain both the actual content and XML layout definitions (presentation details) dictating how that content renders on a page. When migrating to a modern headless system or a different CMS, this XML is useless and pollutes your content payload. A proper extraction process strips Sitecore-specific layout XML, isolates raw field values, rich text, and metadata, then maps those clean fields to the target schema.

## Start Scoping Now, Not in December

If you are on XP 10.0 or 10.1, the 31 December 2026 deadline is less than three months away as of Q4 2026. Even upgrading to 10.4 needs scoping, budgeting, environment provisioning, testing, and a maintenance window — that does not happen in a week.

If you are evaluating a platform migration, the decision cycle alone — vendor evaluation, proof of concept, contract negotiation — can consume months before technical work begins.

Recommended lead times by action:

Sitecore does not publish upgrade durations. The figures below are ClonePartner estimates based on comparable upgrades, offered as a planning starting point rather than a quote — your own customization depth will move them substantially.

| Action | Minimum Lead Time |
|---|---|
| Upgrade XP 10.0/10.1 → 10.4 (low customization) | 3–4 months |
| Upgrade XP 10.0/10.1 → 10.4 (high customization) | 6–12 months |
| Migrate to XM Cloud (headless rebuild) | 9–18 months |
| Evaluate and migrate to alternative platform | 12–24 months |
| Identity Server 8.x → 9.x upgrade (standalone) | 4–8 weeks |

One practical rule: **stop adding net-new XP-specific coupling** unless essential for business continuity. Every new custom rendering, search dependency, xDB facet, or platform integration created late in the lifecycle becomes one more thing you have to unwind under deadline pressure.

Set a hard internal ownership date before the vendor date. Unsupported periods should be documented as exceptions with named owners and containment steps, not treated as neutral drift.

> ClonePartner handles the data migration layer — extracting content, media, and structured data from Sitecore XP and loading it into your target platform. We resolve dynamic GUID links, decouple presentation from content, extract the binary media library, and handle xConnect data mapping. Book a free 30-minute scoping call to get a fixed-price proposal.
>
> [Talk to us](https://clonepartner.com/talk-to-us?duration=30&utm_source=blog&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click)

## Frequently asked questions

### When does Sitecore XP 10.0 and 10.1 end of support happen?

Extended Support for Sitecore XP 10.0 and 10.1 ends on 31 December 2026. After that date, they enter Sustaining Support where security patches are not available at any price. The .NET 8 runtime underneath Sitecore Identity Server reaches end of support earlier, on 10 November 2026.

### What changed about Sitecore support on 1 June 2026?

Since 1 June 2026, production incident support and security updates are no longer included in Sitecore's Extended Support phase. Both are now paid services requiring a separate arrangement. Documentation, knowledge base access, and upgrade assistance remain included. Mainstream Support (currently covering 10.4) is unaffected.

### How long is Sitecore XP 10.4 supported?

Sitecore XP 10.4 has Mainstream Support through 31 December 2027 and Extended Support through 31 December 2030. It is the only XP version currently in Mainstream Support where security updates are still included. However, Sitecore Experience Commerce is not supported on 10.4 or later.

### Can an MVC Sitecore site move to XM Cloud without a rebuild?

Not directly. Sitecore's own migration FAQ states XM Cloud does not support CD servers, and existing MVC solutions must be refactored to JSS or another headless/.NET Core client approach. Capabilities like custom Solr indexes and Sitecore Forms also do not carry over.

### How long does a Sitecore data migration take?

Most data migrations complete within 1–5 business days depending on data volume, complexity, and API rate limits. Small datasets under 10,000 records can finish in under 24 hours. The platform rebuild is the longer project. Sitecore publishes no official duration; our own estimate, based on comparable upgrades, is 4–12 months depending on customization.