SitecoreAI went live on 10 November 2025, announced at Sitecore Symposium — and with it, every Sitecore roadmap conversation changed. If you run XP, XM, or XM Cloud today, “should we migrate?” now has a concrete platform, tooling, and timeline attached. Here is what SitecoreAI actually is, what you gain, and how to migrate without breaking what works.
What SitecoreAI actually is
SitecoreAI is the evolution of XM Cloud, not a separate product — the same Azure-hosted, composable foundation with an AI-native layer built across it. The platform is organised into connected studios: Agentic Studio (AI agents for marketing workflows), App Studio (custom applications), Sitecore Connect (integrations), and a Marketplace. Under it all sits one data model — content, customer data, and personalization share a unified profile, with Search, CDP, and Personalize connected natively rather than through separate integration layers.
The practical headline: AI agents can now generate content variants, run A/B tests, and optimise personalization inside governed boundaries your team defines — work that previously queued behind sprints.
The benefits, stated plainly
- Agents in the workflow, not beside it. Content generation, testing, and personalization optimisation run as governed platform capabilities — marketers configure them; developers set the boundaries.
- One customer profile, no ETL glue. The unified data model ends the CDP-to-CMS plumbing projects that consumed quarters.
- Cloud economics. Legacy XP means servers, upgrades, and patch cycles. SitecoreAI inherits XM Cloud’s SaaS model — the infrastructure line largely disappears.
- Enterprise governance. Agent operations come with deployment controls and auditability — the difference between AI your risk team blocks and AI it signs off.
- Bilingual leverage. For Middle East brands, agent-assisted content operations change the economics of running true Arabic-English parity — the variant work that made bilingual sites expensive is exactly what agents do well.
What migration involves — by starting point
From XM Cloud
The transition is non-breaking. Existing customisations, integrations, and content carry over, and the AI capabilities light up on the platform you already run. Your work is adoption, not migration: data-model readiness, agent governance, and training.
From XP or XM 10.x
This is a real migration — content model translation, a rebuilt head, integration rework, and SEO preservation. Sitecore’s SitecoreAI Pathway tooling automates content conversion with intelligent mapping and schema translation with manual review points, and workflows are either replicated or — better — redesigned around agents. The right approach is an assessment first, then per-component replicate-or-reimagine decisions, then a phased rollout.
From another DXP
A replatform, with the same disciplines — and often the moment organisations consolidate CRM and experience onto one accountable architecture. That conversation is where our Salesforce practice and Sitecore practice work as one team.
The five pitfalls we see
- Lift-and-shift thinking. Recreating your 2018 workflows on an agentic platform wastes the reason you migrated.
- Personalization data left behind. Rules and segments need deliberate translation into the unified model, or you restart from zero.
- SEO debt. URL maps, redirects, metadata, and structured data must survive the move — rankings lost in migration take quarters to rebuild.
- Governance as an afterthought. Define what agents may touch before go-live, not after the first incident.
- No capability transfer. If your team can’t run it, you’ve bought a dependency, not a platform. Training belongs in the plan.
How to start
Start with evidence, not a licence. Our free Sitecore health check gives you a senior read of your current estate — what migrates cleanly, what needs rework, what to leave behind. From there, Arcsen Ascend is our structured migration programme, and our work with EgyptAir shows what the destination looks like at national-carrier scale.
Frequently asked questions
Is SitecoreAI a new product or XM Cloud renamed?
Neither, exactly: it is XM Cloud’s evolution — same foundation, new AI-native layer (agents, unified data model, governance). XM Cloud customers transition without breaking changes.
Do we have to leave XP now?
No — but the centre of gravity has moved. Every quarter on XP is a quarter of infrastructure cost and widening capability gap. The sensible move is an assessment now, a phased plan on your timeline.
Will our SEO survive the migration?
It will if it is treated as a first-class workstream: full URL inventory, redirect map, metadata and schema parity, and crawl verification before and after cutover. We have done this for national-scale sites without losing positions.
How fast can we be live?
A scoped first release — one site or journey, measured — beats a big-bang replatform. Assessment first; the roadmap tells you the rest honestly. Talk to the team.
