SitecoreAI Pathway site migration readiness check
Before you create a migration, review the following information to determine the best migration path to use with SitecoreAI Pathway and how to prepare for your migration.
SitecoreAI Pathway does not copy your site one to one at the push of a button. It uses AI to map your existing content into a SitecoreAI site that you have already designed and built. Plan time to review and refine the migrated pages.
Choose your migration path
Find your current site in the following table to see which migration path to use.
| Your current site | SitecoreAI Pathway path | Additional notes |
|---|---|---|
| Sitecore XM/XP · Headless SXA | Sitecore website | Strongest match. Closest to how SitecoreAI sites are built. Content and page structure are extracted from your SitecoreAI instance, so pages map most directly to your new components. IMPORTANT: Keep the rendering host running during extraction. |
| Sitecore XM/XP · SXA MVC | Sitecore website | Supported. Content and page structure are extracted from your SitecoreAI instance. MVC renderings are not reused. IMPORTANT: Build the matching components in SitecoreAI first. |
| Sitecore XM/XP · Headless JSS (no SXA) | Sitecore website | Supported. Content is extracted from your SitecoreAI instance. Without SXA, results depend on how consistent your templates are. A structure, such as Helix, improves results. IMPORTANT: Keep the rendering host running during extraction. |
| Sitecore XM/XP · MVC only (no SXA, no headless) | Any site | Content from published pages. The extraction tool cannot read MVC-only sites, so SitecoreAI Pathway takes content from the public pages instead. Up to 300 URLs and one language per run are supported. |
| Older or heavily customized Sitecore | Any site | Content from published pages. Use this path when the site does not follow standard item structures, so content cannot be extracted reliably from the SitecoreAI instance. |
| Another platform (AEM, Drupal, WordPress, or custom) | Any site | Public pages are migrated. SitecoreAI Pathway crawls the public pages and imports their content and, optionally, their images. NOTE: Bot protection can block the crawl. Content loaded by JavaScript might be missed. |
Requirements for each path
Review the requirements for the path you chose.
Use this path to migrate an XM/XP site built with SXA or headless. SitecoreAI Pathway extracts the layout, renderings, components, and data from the source environment. The following requirements must be met:
- The site runs on a currently supported version of SitecoreAI. SitecoreAI Pathway is tested with version 10.2 and later. Earlier versions can be reviewed.
- The site uses SXA or headless. It isn't mandatory to follow Helix principles with a default layout structure, but it will improve migration results.
- You have Admin access to XM/XP so you can change the security settings in the config file and upload the extraction handler.
- You have .NET 10.0 installed.
- You've moved in-scope images and other media to your SitecoreAI project with the XM to XM Cloud migration tool and kept the same item IDs. Do this before you run SitecoreAI Pathway.
You can migrate the whole site or only selected parts of it. Multiple languages are supported, with one language per migration.
Use this path to migrate any website, or a Sitecore site that doesn't follow standard item structures. SitecoreAI Pathway uses an AI crawler to extract content from the site's public pages. The following requirements must be met:
- The pages are publicly accessible without signing in. If the site is behind a firewall or IP restriction, add the crawler's IP address to the allowlist before you start.
- The site has a valid sitemap (
/sitemap.xml) that the crawler can use to discover pages, or you have a list of specific page URLs. Sitemaps can include both active and outdated URLs. - Each migration includes up to 300 URLs. Migrate larger sites in batches.
- Each migration includes one language.
Importing media is optional. If you enable it, SitecoreAI Pathway collects the images from the public pages and imports them into /sitecore/media library/project.
Access requirements
To use SitecoreAI Pathway, you need:
- A Sitecore 360 subscription. SitecoreAI Pathway is included.
- A signed Generative AI addendum. This means Stream and Agentic Studio are available in your organization.
- An organization and AI tenant in the same region: US East, US Central, EU West, Australia East, Japan East, or Singapore.
Prepare you SitecoreAI site
SitecoreAI Pathway migrates your content into an existing SitecoreAI site, so you must set up the target site before you start. Build your SitecoreAI site in the following order:
- Define the information architecture and presentation model.
- Implement the layout (for example, the footer, main section, and header), templates (content models), components, page and partial designs, and template mappings.
- Deploy the Content SDK solution.
- Confirm that every component the migration needs is available.
Readiness checklist
Work through the following checklist with your Sitecore account team or implementation partner to prepare for the migration and ensure the best results.
| Question | Why it matters |
|---|---|
| Which Sitecore version are you on? | SitecoreAI Pathway is tested with version 10.2 and later. Earlier versions need a review. |
| Is the site SXA (MVC or headless), headless JSS, or MVC only? | Determines whether you use the Sitecore website path or the Any site path. |
| How many sites, pages, and languages do you have? | Each migration covers one site in one language. The Any site path supports up to 300 URLs per migration. |
| Is the target SitecoreAI site designed and built? | SitecoreAI Pathway maps content to the templates and components in your target site, so they must exist first. |
| Are Sitecore 360 and the Generative AI addendum in place? | Both are required to use SitecoreAI Pathway. |
| Do you use personalization, and is an implementation partner involved? | Personalization isn't migrated and must be rebuilt in SitecoreAI. |
Create a migration
When your site is ready, create a migration.