Sitecore XP to SitecoreAI: A Migration Readiness Checklist

Moving from Sitecore XP to SitecoreAI is not an upgrade. It is a move from a self-hosted platform with full server-side control to a SaaS content management system with a headless front end. MVC, xDB, Sitecore Forms and the Content Delivery role do not exist in SitecoreAI, and custom server-side code on the content management (CM) instance is discouraged.

The cost of a Sitecore XP to SitecoreAI Migration is decided by what the XP solution depends on, so that inventory should come first. Every Sitecore XP solution is different, so treat this as a framework for assessing your own project rather than a fixed plan. This post lists what changes, what the official replacement is, and what to check before committing to a plan. Platform facts are taken from the official SitecoreAI documentation and the Sitecore Accelerate cookbook referenced at the end; the author’s recommendations are labelled as such.

What changes at a glance

XP capabilityIn SitecoreAIMigration action
MVC renderingsNot availableRebuild as components in a Next.js head application
SXA with MVC, SXA Search componentsNot availableMove to Headless SXA
Content Delivery role, web database, Sitecore Publishing ServiceNot availablePublish to Experience Edge; review the Edge restrictions in section 5
Custom pipelines, processors, event handlersDiscouraged on the CMMove to webhooks, the head application or external services
xDB, xConnect, personalization rulesNot availableRebuild with Conversion Optimization and Audience & Insights
Experience Analytics, Experience Profile, Marketing Automation, EXM, List ManagerNot availableSee section 3; Marketing Automation and EXM have no equivalent
Sitecore FormsNot availableRebuild in SitecoreAI Forms
Custom search indexesNot availableUse an external or composable search service
Device detection, IP GeolocationNot availableUse Page builder personalization or the Sitecore Cloud SDK
Identity Server, Data Exchange Framework, Update CenterNot availableNo replacement is documented; select an alternative before migrating

Sources: Limitations and restrictions (SitecoreAI), Transition from XM/XP to SitecoreAI (Accelerate).

1. Rendering and migration approach

MVC is not available in SitecoreAI. Every rendering becomes a component in a headless front end, typically a Next.js application built on the Sitecore Content SDK, and SXA sites move to Headless SXA.

The Accelerate cookbook describes two approaches:

Big bangHybrid
Best forMost existing implementationsSeveral websites, or one very large site
How it worksPort existing HTML and CSS to Next.js, reshape content for Headless SXA, cut over onceBuild shared elements (header, footer, navigation) first, then migrate self-contained sections, routing traffic between old and new platforms
Main trade-offWork on the existing platform slows or stops during the projectContent lives on two systems, so search, login tokens and visitor identification must span both

Readiness questions:

  • How many distinct renderings and rendering variants does the solution use?
  • Is the site on SXA, and does it use SXA Search components?
  • Do any renderings depend on per-request server logic, such as user, query string or session? Experience Edge publishes a static snapshot of Layout Service output and does not support contextual output.
  • Does the team have Next.js and React experience?

Upgrading Sitecore XP before migrating is not generally required, according to the Accelerate cookbook. Evaluate it case by case, because it adds cost and time.

Sources: Limitations and restrictions (SitecoreAI), Transition from XM/XP to SitecoreAI (Accelerate), Limitations and restrictions of Experience Edge.

2. Custom server-side code

In Sitecore XP, extending the platform usually meant pipeline processors, event handlers and config patches on the server. SitecoreAI is a SaaS platform, and the documentation narrows that model in three ways:

  • Webhooks are the supported way to react to system events. External services subscribe to events instead of custom event handlers running inside the platform.
  • Custom CM code is discouraged. The Accelerate cookbook lists custom content resolvers, custom event handlers and customizations to the editing UI as patterns to move away from. They still work but slow future migration. Its content audit guidance also describes deploying custom C# code to the CM, for example to create custom bucket structures, as not a recommended practice.
  • Environments are immutable. Installing DLLs, configs or handlers through packages, as the Package Designer allowed in XP, is not supported.

Mapping common Sitecore XP patterns:

XP patternSitecoreAI approach
Custom event handler (item saved, published)Webhook event handler calling an external service
Custom workflow actionWebhook submit action or validation action
Custom content resolverGraphQL query from the component; integrated GraphQL is recommended for shared components
Pipeline processor that changes rendered outputLogic in the head application
Scheduled task or agentExternal scheduler calling SitecoreAI APIs
Package installing code or configNot supported; deploy through source control

The first three rows follow the documentation directly. The last three are the author’s recommendations, based on where each responsibility sits in a headless architecture.

Readiness questions:

  • Which config patches and custom assemblies does the XP solution deploy, and what does each one do?
  • Which of them exist only to support MVC rendering and disappear with the move to headless?
  • Which react to events or workflow, and can become webhooks?
  • Which must still run on the CM, and is there a supported alternative?

Sources: Webhooks, Transition from XM/XP to SitecoreAI (Accelerate), Content audit (Accelerate), Migrating content between SitecoreAI environments, Limitations and restrictions of Experience Edge.

3. xDB, analytics and personalization

SitecoreAI has no XP, xConnect or xDB functionality, and existing personalization rules do not carry over. Nothing in this area migrates automatically: SitecoreAI Pathway does not move xDB data, email marketing content or personalization.

The Accelerate cookbook maps XP features to their SitecoreAI equivalents, provided by Conversion Optimization and Audience & Insights:

XP featureSitecoreAI equivalent
Personalization rulesPage variants, component variants, headless and triggered personalization (rebuilt)
Experience Optimization A/B testsA/B/n tests with 2 to 6 variants
Experience AnalyticsPerformance dashboards for sites, forms and component tests; reports are not migrated
Experience ProfileProfiles in Audience & Insights
Segments and List ManagerAudiences (not email recipient lists)
xDB contacts and identificationIdentity resolution and rules, off by default

Marketing Automation, EXM, Path Analyzer, Campaign Creator, the Marketing Control Panel and FXM have no equivalent. Plan alternatives if the business depends on them.

Points to plan for:

  • Profile quality depends on the head application. Events must be sent from the front end with the Sitecore Cloud SDK. Without identity events and identity resolution, profiles stay fragmented.
  • Audience membership refreshes on a schedule, every 6 hours by default. For requirements that need an immediate response, the cookbook recommends real-time signals instead of audience membership.
  • Historical data is a decision, not a default. Pathway does not move xDB history. If it is needed, load it through profile import, which reads bulk data from a JSONL file; set up identity rules first.
  • Confirm availabili first. Conversion Optimization and Audience & Insights are rolling out in phases, so confirm availability with Sitecore before designing around them.

Readiness questions: Which XP rules, goals, segments, profile cards, A/B tests and reports are actually in use? The cookbook recommends inventorying them and retiring unused items before rebuilding.

Sources: Transition from XM/XP to SitecoreAI (Accelerate), Limitations and restrictions (SitecoreAI), Migrate a site to SitecoreAI.

4. Forms

Sitecore Forms is not available in SitecoreAI, and neither is the Forms database role. The replacement is SitecoreAI Forms, created in the Design area and placed on pages in the Page builder. Creating and editing forms requires the Advanced User or Admin role.

The main architectural change is how submissions are processed. SitecoreAI Forms sends submitted data to third-party applications through webhooks. Logic that lived in Sitecore Forms custom submit actions, such as saving to a database, sending email or triggering a CRM workflow, must move to an external service that receives the webhook.

The Accelerate cookbook also notes that not every form needs to move to SitecoreAI Forms. Some are better rebuilt as front-end components, for example to improve the user experience.

Readiness questions:

  • How many forms exist, and which are still in use?
  • Which custom submit actions, validators or field types do they rely on?
  • Where does submission data go today, and which system will receive the webhook?
  • Is historical submission data needed after Sitecore migration?

Sources: Limitations and restrictions (SitecoreAI), Forms (SitecoreAI), Content migration (Accelerate).

5. Content, sites and delivery

Content migration tooling. SitecoreAI Pathway is an AI-assisted Sitecore migration app that extracts layout, renderings, components and data from an XM/XP site and maps them to a target SitecoreAI project before moving the content.

PathwayDetail
AccessMust be requested before the app appears in the Marketplace
Source prerequisitesThe XM/XP site should follow Helix principles with a default layout structure; Admin access to the source to change config security settings and upload the extraction handler; .NET 10.0 installed
Not migratedPage and partial designs; XP-related items such as xDB data, email marketing content and personalization
MediaUse the XM to XM Cloud migration tool to move in-scope media

Experience Edge restrictions that can affect migrated Sitecore XP sites:

  • Multiple site definitions pointing to the same start item are not supported, including on sites migrated from XP or SXA. The exception is language-based resolution: set ExperienceEdge.SiteResolvingMatchCurrentLanguage to true, give each site a unique default language mapped to a distinct hostname, then republish the site.
  • Virtual folders and aliases are not supported.
  • Wildcard items resolve on the Preview endpoint only, not on Delivery.
  • Language fallback rules are applied at publish time and can be enabled only per instance, not per site.
  • Items whose names differ only by a space and a dash, such as Test Item and Test-Item, receive the same identifier, so only one is available on Edge.
  • Edge does not enforce security on content. Use publishing restrictions to keep non-public content off Edge.

Readiness questions:

  • Does the Sitecore XP solution share one start item across several site definitions?
  • Does it rely on aliases, virtual folders or wildcard items for live URLs?
  • Is language fallback configured differently per site?
  • Does any content rely on item-level security for visitors?

Sources: Migrate a site to SitecoreAI, Limitations and restrictions of Experience Edge.

By inventorying what the XP solution depends on before committing to a plan, teams can scope their move to SitecoreAI accurately, choose the right replacement for each capability, and avoid costly surprises once the migration is underway.

References

Leave a Reply