Sitecore XP and XM customers in the Middle East are being asked to pick a destination: XM Cloud, or the new SitecoreAI platform. Both end the infrastructure era — they differ in what they put at the centre.
Where each one fits
XM Cloud is the proven SaaS CMS: headless delivery, Pages editing, and a mature partner ecosystem. If your roadmap is content operations at scale with a front end your team already owns, XM Cloud is the conservative, well-trodden route.
SitecoreAI is Sitecore’s AI-native platform — the CMS rebuilt around agents, brand-aware generation, and automated personalization rather than hand-tuned rules. If the reason you are migrating is to do more with a smaller content team, that is the bet SitecoreAI makes for you.
The 2027 clock
Sitecore XP’s support horizon makes this a planning question for 2026, not 2028. Replatforming takes quarters — content model rework, integration rewiring, and front-end rebuilds all land on the same timeline, and Arabic-English estates carry extra weight: per-language content models, RTL front ends, and bilingual editorial workflows have to survive the move.
What actually moves
- Content — audit first; most XP estates carry years of dead items that should not pay the migration toll.
- Templates and layouts — headless means rebuilding rendering, not lifting it.
- Personalization — XP rules do not port one-to-one; decide what the AI layer should own.
- Integrations — the quiet majority of effort. Inventory every connector before you price anything.
How we would start
We run a fixed-scope Sitecore health check that inventories exactly this — content debt, integration surface, Arabic parity risks — and gives you a defensible migration case either way. Start there, or read our deeper piece on what SitecoreAI changes.
Image: Colin, via Wikimedia Commons (CC BY-SA 3.0).
