Skip to Main Content
Sitecore
XM + Personalize FAQ
The XM + Personalize FAQ page has loaded.

XM + Personalize FAQ - Migration

Learn more about how to develop for XM + Personalize.

How does the migration from XMP (XM on Managed Cloud) to XM Cloud look? Is it seamless? The actual process of moving an XM + Personalize customer from Managed Cloud to XM Cloud is still being determined. However, it is important to note that the XM + Personalize implementation will need to employ Experience Manager as a headless CMS, using the Sitecore JavaScript Rendering SDK (JSS), publishing to Sitecore Experience Edge, and utilizing a Jamstack framework or .NET Core to build the client application, before it can be a candidate for XM Cloud. Sitecore recommends using Next.js as the Jamstack framework because of its flexibility in supporting Static Site Generation (SSG), Incremental Static Regeneration (ISR), and Server-Side Rendering (SSR). If customers want to implement a .NET Core, React, Angular, or Vue.js client application, they will need to host a separate rendering host instance themselves - the rendering host will not be available through XM Cloud. This separate rendering host is not required by Next.js. Besides implementing XM as a headless CMS, customers will need to ensure that they are not using XM capabilities that will not be available with XM Cloud. Some examples of these capabilities are custom Solr indexes and use of Sitecore Forms. The list of XM capabilities which will not be available in XM Cloud will follow in the upcoming month.

We had planned to close in May for XM Managed Cloud, but it appears you have a new XM Cloud product and Front End as a Service coming out that we are interested in. Can we migrate from this XM Managed Cloud to XM Cloud if we start developing in May?

If you begin implementing Sitecore Experience Manager as a headless CMS in Managed Cloud in May, with the Sitecore JavaScript Rendering SDK (JSS), and publishing to Sitecore Experience Edge, while keeping in mind the XM capabilities which will not be available in XM Cloud, you should be able to transition to the upcoming Sitecore Experience Manager Cloud product. The process for transitioning from Sitecore Managed Cloud to Experience Manager Cloud is still being determined and more details will follow later.

Will JSS give us a similar component library and rendering variants like SXA? Sitecore intends to deliver new components for headless implementations with a future release of SXA for Experience Manager. The final list of new SXA components that will be compatible with headless implementations is still in development, and the objective for the new components will be to support the common scenarios with an ability to easily create additional flexible components supporting rich layout options alongside variants and grids. With the current Experience Manager 10.2 release, customers can base their headless components on the JSS Sample components as a starting point.

Can I move my current MVC-based Experience Manager solution into XM Cloud? Sitecore Experience Manager Cloud is optimized to run Experience Manager as a headless CMS with the Sitecore JavaScript Rendering SDK (JSS), publishing to Sitecore Experience Edge, with a Jamstack framework or .NET Core client application. Sitecore Experience Manager Cloud will not support Content Delivery (CD) servers so current MVC solutions will need to be converted to a JSS implementation where the web solution gets content and layout data from Experience Edge before it can be run in Experience Manager Cloud. Alternatively, customers can host their MVC solutions in Sitecore Managed Cloud, which will continue to support MVC-based solutions into the future. Besides implementing XM as a headless CMS, you will also need to ensure that you are not using XM capabilities which will not be available with XM Cloud. Some examples of these capabilities are custom Solr indexes and use of Sitecore Forms. The list of XM capabilities which will not be available in XM Cloud will follow in the upcoming month.

What is required to upgrade my current MVC solution so it can run in the XM Cloud environment? Customers with existing MVC solutions who want to move to XM Cloud will first need to refactor and rebuild their current MVC solution as a Jamstack framework or a .NET Core solution. Experience Manager Cloud will only support headless Experience Manager implementations using the Sitecore JavaScript Rendering SDK (JSS), Sitecore Experience Edge, and a Jamstack framework or .NET Core client application. The process of refactoring applies to the MVC solution's backend:

  • With JSS, customers will be able to reuse their Sitecore data source, setting, and folder templates from their existing MVC solution.
  • Page templates will need to be modified to use JSS layouts and renderings, and to inherit from the JSS route template.
  • MVC View and Controller renderings, and any object-relational mapping (ORM), should be removed as they are not applicable for JSS.
  • MVC renderings will need to be converted to JSS renderings.

In parallel to the backend being refactored, the frontend solution will need to be rebuilt, preferably using a Jamstack framework such as Next.js. Sitecore recommends Next.js because of its flexibility with support for static site generation (SSG), server-side rendering (SSR), and incremental static regeneration (ISR). Customers can implement a .NET Core, React, Angular, or Vue.js client solution as well, but they will need to host a separate rendering host instance themselves - the rendering host will not be available through XM Cloud. This separate rendering host is not required by Next.js as Next.js includes the rendering host capability as part of its run-time. Once the backend refactoring and the frontend rebuild are done, content and layout will be published to Experience Edge for consumption by the frontend solution using the Edge GraphQL endpoints.

Will upgrading my current XM/XP now to the latest version, prepare me for moving into the XM Cloud solution later?

By upgrading to Sitecore Experience Manager 10.2 now, you will be better positioned to transition to Experience Manager Cloud when it launches because Experience Manager Cloud will use a derivative of the 10.2 release. However, note that Experience Manager Cloud will only support a headless Experience Manager implementation using the Sitecore JavaScript Rendering SDK (JSS), publishing to Sitecore Experience Edge. If your current XM/XP site is MVC-based, you will need to convert it to a JSS and Experience Edge-based implementation before it can be run in Experience Manager Cloud. Besides implementing XM as a headless CMS, you will also need to ensure that you are not using XM capabilities which will not be available with XM Cloud. Some examples of these capabilities are custom Solr indexes and use of Sitecore Forms. The list of XM capabilities which will not be available in XM Cloud will follow in the upcoming month.