SitecoreAI Migration Readiness Check
Thinking about moving from Sitecore XM or XP to SitecoreAI (formerly XM Cloud)? Answer 8 questions and see whether you are ready, ready with rework, better off upgrading in place first, or fine to stay and plan, with the trade-offs behind it.
The scoring is a transparent heuristic from consulting experience: a starting point, not a verdict.
Which Sitecore version do you run today?
Points depend on the version's support phase today, from Sitecore's KB0641167.
How the scoring works
Each answer adds points to one or more of the four outcomes. The highest total wins, then these rules apply:
- If Upgrade in place first scores highest but your version is already in Mainstream support, the result becomes Stay and plan.
- If Stay and plan scores highest but your version is no longer in Mainstream support, the result becomes Upgrade in place first.
- A tie goes to the more cautious outcome, in this order: Ready with rework, Upgrade in place first, Ready: plan the migration, Stay and plan.
Every point value
Which Sitecore version do you run today?
- Mainstream support: +3 Stay and plan, +1 Ready: plan the migration
- Extended support: +2 Upgrade in place first, +1 Ready: plan the migration, +1 Ready with rework
- Sustaining support: +2 Upgrade in place first, +2 Ready: plan the migration, +2 Ready with rework, -3 Stay and plan
- Past all support: +2 Upgrade in place first, +2 Ready: plan the migration, +2 Ready with rework, -5 Stay and plan
How is your front end built?
- MVC: +2 Ready with rework, +1 Upgrade in place first, -1 Ready: plan the migration
- SXA: +2 Ready with rework, +1 Upgrade in place first, -1 Ready: plan the migration
- Headless: +3 Ready: plan the migration
Which XP marketing features does your site rely on?
- xDB: +2 Ready with rework, +1 Upgrade in place first
- Marketing Automation: +2 Upgrade in place first, +1 Ready with rework, -1 Ready: plan the migration
- EXM: +2 Upgrade in place first, +1 Ready with rework, -1 Ready: plan the migration
- Several of these: +3 Upgrade in place first, +1 Ready with rework, -2 Ready: plan the migration
- None of these: +2 Ready: plan the migration
How customized is your Sitecore build?
- Few: +2 Ready: plan the migration
- Some: +1 Ready with rework
- Heavy: +2 Upgrade in place first, +1 Ready with rework, -2 Ready: plan the migration
How many back-end integrations does the site have?
- 0 to 2: +1 Ready: plan the migration
- 3 to 6: +1 Ready with rework
- 7 or more: +2 Ready with rework, +1 Upgrade in place first, -1 Ready: plan the migration
How do you serialize Sitecore items today?
- TDS: +1 Ready with rework
- Unicorn: +1 Ready with rework
- SCS: +1 Ready: plan the migration
- None: +1 Ready with rework, -1 Ready: plan the migration
Does your team have Next.js skills?
- Yes, in house: +2 Ready: plan the migration
- Partly: +1 Ready with rework
- No: +1 Upgrade in place first, +1 Stay and plan, -2 Ready: plan the migration
When does the change need to be live?
- Under 6 months: +2 Upgrade in place first, -1 Ready: plan the migration
- 6 to 12 months: +1 Ready: plan the migration, +1 Ready with rework
- Over 12 months: +1 Ready: plan the migration, +1 Ready with rework, +1 Stay and plan
Version phases come from the Sitecore Version Support Checker and are computed against today's date.
Frequently asked questions
Does SitecoreAI include xDB, Marketing Automation and EXM?
No. Sitecore's transition guide says SitecoreAI does not include XP, xConnect or xDB functionality, and existing personalization rules do not carry over. Personalization and audiences move to SitecoreAI's Conversion Optimization and Audience & Insights capabilities, which Sitecore says are rolling out in phases. Marketing Automation and EXM have no SitecoreAI equivalent; Sitecore says email may need to shift to Sitecore Send or another solution.
Do I need to upgrade to the latest XP version before migrating to SitecoreAI?
Not necessarily. Sitecore's own guide says an upgrade first is not always required and, because SitecoreAI is fundamentally different from XM or XP MVC, usually brings no benefit in efficiency, cost or stability. Upgrading in place still makes sense when you are staying on XM or XP for a while and need a supported version.
Do I have to rebuild my front end to move to SitecoreAI?
If it is MVC, yes. Sitecore's guide says SitecoreAI requires Headless SXA, and describes porting the CSS and HTML of an MVC site to Next.js. Sitecore provides SDKs for Next.js (the Content SDK), Angular and ASP.NET Core, and recommends the Content SDK for JavaScript front ends.
How does this check reach its result?
Each answer adds points to one or more of four outcomes, and the highest total wins, with two rules for your version's support phase. Every point value is listed on this page. It is a transparent heuristic from consulting experience, a starting point for your own planning rather than a verdict.
Sources
Every statement about Sitecore in this check comes from these Sitecore pages, verified October 19, 2026.