Sitecore’s Pathway tool moves your content and page structure. ArcShift™ moves the parts Pathway leaves out: your code, personalization, integrations, analytics, media and the Arabic experience. Eight components and one method, run by our Sitecore team in Arabic and English.
- Sitecore XP and XM to SitecoreAI
- Arabic and English
- Next.js, right to left
- Factory method
Eight components. One toolkit.
Four are software we bring to every migration from day one. Four are the playbooks that make every migration run the same way, so estimates hold and nothing is left to chance.
01
Estate Scan
An inventory of templates, renderings, content per language, personalization rules, integrations and custom modules. It feeds the decision memo: licence maths, risk, timeline and the honest stay option.
Playbook
02
Pathway Runbook
How we run SitecoreAI Pathway: bundling pages, reviewing the AI’s proposed mappings, running a pilot bundle and phasing Arabic and English, with sign-off gates at every step.
Playbook
03
Arabic-first Starter
A Next.js head for SitecoreAI with right-to-left layouts, Arabic typography and numerals, bilingual routing and hreflang pairs, ready for the page builder from the first sprint.
Software
04
Bilingual Component Library
Reusable SitecoreAI components built and tested in Arabic and English, accessible by design and ready for personalization, so editors assemble new pages from tested parts.
Software
05
Code Conversion
Scripts and tooling that convert MVC renderings and custom code into Next.js components. A Sitecore developer reviews every change before it ships.
Software
06
Personalization Carry-over
XP rules, goals and audiences mapped to SitecoreAI personalization, with a written loss report before cutover, so nothing disappears quietly.
Playbook
07
Integration Re-pointing
CRM, commerce, DAM and search connections re-pointed and regression-tested. Salesforce and MuleSoft work runs through our own Salesforce practice, under one roof.
Playbook
08
Automated QA and Cutover
Visual regression in both languages, accessibility and performance checks in the pipeline, redirect maps and sitemap parity, then hypercare until the numbers hold.
Software
Pathway and ArcShift™
Pathway moves your content. ArcShift™ moves the rest.
SitecoreAI Pathway is Sitecore’s AI-assisted migration tool, included as part of Sitecore 360. It is good at what it does, and Sitecore is clear about what it leaves out. ArcShift™ is built around that line.
| Part of your estate | SitecoreAI Pathway | With ArcShift™ |
|---|---|---|
| Content items, page structure and layouts | Migrated, with AI-proposed bundles and mappings | Run with our Pathway Runbook and sign-off gates |
| Configured languages | Migrated | Arabic and English checked as pairs, hreflang preserved |
| Templates | Recreated in SitecoreAI | Rebuilt on the Bilingual Component Library |
| Custom code and renderings | Not migrated | Converted to Next.js on the Arabic-first Starter, then reviewed |
| Personalization rules | Not migrated | Mapped to SitecoreAI personalization, with a loss report |
| Analytics data | Not migrated | Baseline captured, measurement rebuilt and verified |
| Workflow states | Not migrated | Workflows rebuilt for two languages |
| Custom integrations and modules | Not migrated | Re-pointed and regression-tested |
| Media library | Handled separately | Moved with the content batches |
Pathway scope as published by Sitecore on its SitecoreAI Pathway page.
The shape of the job
Three ways to move, each costed in the memo.
MOVE
Move as it is
The same design and information architecture on SitecoreAI, with the code modernized underneath. The quickest way off XP.
REFRESH
Refresh
The same structure, rebuilt on the Bilingual Component Library with a cleaner design system and faster pages.
REDESIGN
Redesign
A new experience designed for SitecoreAI, with content modelled for personalization and AI agents from day one.
The clock
Treat December 2027 as a budget line.
Mainstream support for Sitecore XP and XM 10.4 runs to the end of 2027, with extended support to the end of 2030. XP 10.5, released in August 2026, moves mainstream support to the end of 2029: it buys time, and the move still lies ahead. Teams that decide early migrate on their own calendar, with time to train editors and tune performance. Teams that drift pay rush rates for the same work.
The method
One method, every time.
The decision memo
Licence maths, risk, timeline and the honest stay option, on one page and before any commitment. If the answer is move, you also get the shape of the job, each option with a cost range. Often fed by the free Sitecore Health Check.
Factory migration
Templates, components, content and integrations move in repeatable, tested batches with the ArcShift™ kit. The same method every time, so estimates hold.
Cutover and tune
SEO-safe redirects, performance budgets enforced, editors trained, then hypercare until the numbers prove the move.
What the move is worth.
Forrester studied organizations running SitecoreAI. Your decision memo turns findings like these into your own numbers.
Source: Forrester Consulting Total Economic Impact™ study of SitecoreAI, commissioned by Sitecore. Results are for a composite organization representative of the customers Forrester interviewed.
On the record
SitecoreAI for a national airline.

EgyptAir and SitecoreAI
In October 2026, Sitecore announced that EgyptAir had chosen SitecoreAI to power its entire digital front end, including the main website, country sites and app content, as part of a wider programme, led by Arcsen, that brings Salesforce CRM into the same integrated system.
Coming from Adobe?
On Adobe Experience Manager 6.5? Every path forward is a migration.
AEM 6.5 core support is planned to end in February 2027. Our guide compares 6.5 LTS, AEM as a Cloud Service and SitecoreAI, and shows how AEM maps to SitecoreAI.
Read before you move
Thinking for Sitecore leaders.
Guide
Sitecore in 2026: SitecoreAI and the December 2027 decision every XP 10.4 customer must make
Migration
What doesn’t migrate to SitecoreAI is what your customers feel
Personalization
Personalization on SitecoreAI: what to rebuild from XP, and what to retire
Arabic-first
Arabic-first Sitecore: what RTL-ready means, and how to test it
Platform
SitecoreAI vs XM Cloud: what changed, and how to move from XP
AI agents
SitecoreAI Agentic Studio, explained: agents, flows and governance
More reading: Migrating to SitecoreAI: what you gain · Choosing a Sitecore partner: an RFP checklist
After go-live
The move is the start. Here is who runs it.
FAQ
Before you ask.
What is ArcShift™?
ArcShift™ is Arcsen’s accelerator for moving Sitecore XP and XM to SitecoreAI: eight components, four of them software and four of them playbooks, run with one method by our Sitecore team in Arabic and English.
How is ArcShift™ different from SitecoreAI Pathway?
Pathway is Sitecore’s tool for moving content and page structure. ArcShift™ runs Pathway with a tested runbook and adds what Sitecore says Pathway leaves out: custom code, personalization rules, analytics, workflow, custom integrations, media and the Arabic front end.
Should we stay on XP or move?
Sometimes staying wins, briefly and deliberately, with hardening. The decision memo puts both paths side by side, and you choose. Drifting is the only wrong answer.
How long does a migration take?
It depends on estate size, languages and integrations, which is exactly why ArcShift™ starts with the memo. You get a dated, phased plan built on your own estate.
What happens to our Arabic site?
It moves with its pairs intact. The Arabic-first Starter handles right-to-left layout, typography and numerals, and every component is tested in both languages before cutover.
Does Pathway cost extra?
Sitecore says Pathway is included as part of Sitecore 360. The decision memo checks what your agreement covers.
What about XM Cloud?
XM Cloud has evolved into SitecoreAI, so there is one cloud destination. The memo weighs your personalization, AI content and licensing needs to set the scope and sequence, with the reasoning shown.
We run Adobe Experience Manager. Can you help?
Yes. We move AEM sites to SitecoreAI with the same factory method and toolkit. Start with our AEM to SitecoreAI guide.
Get the decision memo first.
Start with ArcShift™ · Proposal in 24 hours
Free Sitecore Health Check · Arcsen × Sitecore