There were many factors that went into our decision to upgrade to Sitecore XM Cloud, and it was not a decision that we made lightly. Just a few of the factors considered include:

• In 2022, Sitecore announced significant updates to its product line including release of the new enterprise web content management system. Sitecore’s investment in the current system will be limited.
• Sitecore is hinting that XM Cloud is the critical path of their future roadmap. While Sitecore XP isn’t going anywhere yet, new features and capabilities are focused on and primarily released for Sitecore XM Cloud.
• Systems that live in a vendor’s cloud can be updated as soon as new features and capabilities are ready rather than packaging them into new versions that require expensive upgrades done once a year or less.
• The new system is built on a modern architecture that positions MSU for the future and provides flexibility to easily connect complimentary systems to Sitecore.
• The new system is substantially easier to use. Users of the new system will be able to create pages and load content much more easily and quickly, saving considerable time.
• Site templates can be created in the new system enabling much faster website creation.
• AI is being incorporated into the system to assist with tasks like writing headlines.

Some key differences between Sitecore XP and Sitecore XM Cloud include:

• Improved user interface for content authors: Sitecore has drastically improved the content author experience in Sitecore XM Cloud. Page templates, section templates and site templates make quick work of adding content. Drag-and-drop features and better preview functionality make it easier to envision what your new website will look like as you create the pages.
• In-session personalization: Sitecore XM Cloud offers a set of personalization capabilities for in-session visits. These require less backend set up and are easier to use than personalization in Sitecore XP.
• Maximize Core Web Vitals: The architecture of Sitecore XM Cloud is designed to be edge friendly (referring to computing architecture). This can improve Core Web Vitals and page speed scores, ultimately helping to maximize website SEO.
• Technical differences: Sitecore XM Cloud is headless, meaning the data stored in XM Cloud can be presented anywhere (e.g., website, app, display screen). MSU’s Sitecore XP was not developed to be headless. XM Cloud is a SaaS system, hosted in the cloud on secure servers. Sitecore XP required campus servers. XM Cloud is composable, meaning that system products can be combined and integrated to meet business needs. By contrast, Sitecore XP is an all-in-one system, with unnecessary products included and limitations on what could be integrated. XM Cloud does not require future upgrades; updates are rolled out routinely. Sitecore XP requires regular full-system upgrades, at added cost.

Units with a website in development in QA that has not been launched and moved to the production, or prod, server have a few choices:

• Stop all work in QA and wait to complete the website in Sitecore XM Cloud. Once Sitecore XM Cloud is available, units can migrate the completed work from Sitecore XP to Sitecore XM Cloud, finish the website in XM Cloud and launch. This approach is recommended for sites that have a fair amount of content in Sitecore XP but are not close to completion and launch. You do not have to have your site launched in Sitecore XM Cloud by Jan. 31, 2025, but you will lose all access to content currently in Sitecore XP by that date.
• Finish work in QA and launch in Sitecore XP by an agreed upon date with University Communications, then have the site migrated to Sitecore XM Cloud. This allows you to publish a live site prior to migrating. Since the unit would then have a live site available to the public, the site migration would need to be completed in Sitecore XM Cloud by Jan. 31, 2025. This is recommended if your website is close to completion and a new site is needed as soon as possible.
• Stop working in QA in Sitecore XP and start over in Sitecore XM Cloud. If a unit has a site instance in Sitecore XP but has not completed much (if any) work in building the website, the unit could abandon the work done in Sitecore XP and start from scratch in Sitecore XM Cloud. Content currently in QA in Sitecore XP will be deleted.

University Communications and MSU IT are working through additional details regarding the migration process for QA websites. Check back in the future for updates.

If your unit no longer needs a website, it can be retired. University Communications and MSU IT can work with you to redirect traffic to another website or to msu.edu and will delete your website. Whether they’re moved to Sitecore XM Cloud, moved to another platform or deleted, all websites must be removed from Sitecore XP by Jan. 31, 2025.

If your unit still needs a particular website but does not want to move to Sitecore XM Cloud, that’s fine. You’re welcome to move your website to another platform instead. However, all websites must be migrated out of Sitecore XP by Jan. 31, 2025. Units wishing to migrate to a different platform will be responsible for their website content migration. University Communications and MSU IT cannot assist with migrating to any other platforms beyond URL redirects and DNS adjustments to point to the new website. Our efforts will be focused on Sitecore XP to Sitecore XM Cloud migrations.

You can submit a question using the form linked at the bottom of this page or via email to Katie Kelly at kkelly@msu.edu. Please include your department name and the Sitecore website(s) you’re managing when emailing a question.

User access will be granted with Okta single sign on using MSU Net IDs. Units will need to determine who from their unit will need access.

We’re looking forward to having templated pages, page sections, templated sites, etc., that will include some of the more common layout elements for sites. These can be edited right in the page, will save automatically and can be previewed for desktop, tablet and mobile views. These changes will make page creation simpler.

The site visitor experience (front-end) will be very similar. Users may not notice much of a difference at all.

The Sitecore user interface (back-end) will be completely different, and we think you’ll like the improvements! Several improvements or features include:

• A WYSIWYG (what you see is what you get) editor called Pages combines the features previously available in Content Editor and Experience Editor into one interface.
• Ability to edit right on the screen instead of toggling between data source and display views.
• Functionality to easily drag-and-drop components onto your page.
• Preview page options for mobile, tablet and desktop.
• An Explorer tool that provides advanced content editing, where you can add tags and access additional editing features.
• Component building blocks are largely the same. We’ve balanced the desire to improve functionality with the need to keep things familiar enough to make the migration as easy as possible.
• Page, partial page and site templates to make creating new sites even easier.

Issues related to publishing, saving and logging in should be improved by moving to XM Cloud. That said, if you’re experiencing issues in Sitecore XP, we want to resolve those. Please email Comms.WebSupport@msu.edu to alert us to issues you’re currently experiencing.

Within its cloud version, Sitecore can release new features and updates as soon as they’re available. We will no longer need to schedule costly upgrades every two to three years. New and improved features will be available much more frequently.

All the pages are served up from what is called “the edge.” Basically, there are web servers all around the country. The website will be made available on servers throughout the country so that users access the site at the server closest to their location. For example, a visitor in California would load the site from a server there rather than one near Washington, D.C. This means your website will load much faster for all users. This also increases your Lighthouse Scores, which impact your search engine ranking. Search engines prefer fast-loading websites.

We will still have the ability to embed third-party forms.

After launch we plan to add the ability to add native Sitecore forms to the site. This feature will not be available at launch.

We will not have “internal” sites or pages now. Sitecore was built to be a public internet system, not as an intranet platform. Identity management system functionality will not be available at launch.

If this is a need for your unit, we can discuss workarounds, such as linking to SharePoint content.

For live sites in production:

University Communications will coordinate with units to determine a migration time frame. During the site’s migration window, a site freeze will be put in place. The freeze duration is dependent on the site size and complexity but will typically last 1-2 weeks. No changes can be made to the website during this time. During the site freeze, migration project staff will migrate the website, as-is, to Sitecore XM Cloud. After migration, the unit can review and approve the new site and then the site will launch. Following launch, unit staff can begin updating and managing the website in Sitecore XM Cloud. Training will be provided. The old site in Sitecore XP will be retired.

For QA sites:

University Communications and MSU IT are confirming details for the migration of QA sites. Check back for future updates.

The scope of migration will vary with the size and content on each website. We have taken all steps possible to keep components and data sources similar from Sitecore XP to Sitecore XM Cloud, so migration should be simple relative to designing a website from scratch. Migration project staff will be doing the work of moving prod sites from Sitecore XP to Sitecore XM Cloud. 

Order of migration is to be determined. Live sites will be given priority over sites in QA. Websites that can be fully built using already developed components will be given priority over those awaiting yet-to-be-launched components. University Communications will coordinate with site owners to do our best to avoid scheduling site freezes and migrations at inopportune times for units.

This depends on the number of pages on your site and the number of complex pages (i.e., pages with many components, varying component types and a high number of images) versus simple pages (e.g., an About page). We estimate for most sites the site freeze and migration process will take one to two weeks.

There will not be any downtime for users. Once the new site launches in Sitecore XM Cloud, we “flip the switch” to direct URL traffic from the Sitecore XP version of the site to the Sitecore XM Cloud.

The launch process for site migrations will be the same as the launch process for new websites: The migration project staff builds the website in Sitecore XM Cloud. The unit reviews and approves the work. Once done, University Communications does a brief technical review and then works with the unit and MSU IT to transition to the new website. This will be a faster process than in the past due to the technical structure of Sitecore Cloud’s “edge” computing.

University Communications and MSU IT are working with our partner agency to build the foundational components and templates for websites. Following this, we will conduct extensive testing to ensure the system works well before we provide access to campus users.

This foundational work is scheduled to be completed in April 2024, and we plan to begin scheduling department migrations in May 2024. Please note this timing could change to accommodate testing and development needs.

Websites not migrated by Jan. 31, 2025, will be removed. MSU IT can set up a redirect URL to drive traffic to an existing live site if a site is provided. Otherwise, traffic may be redirected to msu.edu.

We face a vendor-set deadline with substantial financial consequences if we miss that date. This deadline was not set arbitrarily. There are separate contracts for Sitecore XP and Sitecore XM Cloud. As part of the transition, we were able to negotiate only paying for one of the platforms for a limited time to allow for migration. After that time, we will be required to pay for both platforms. We need to be completely out of the Sitecore XP platform by this deadline to avoid additional costs.

The overall timeline for each migration project includes the following steps:

1. University Communications will coordinate migration schedules with units.
2. Migration project staff will migrate a prod site as-is to Sitecore XM Cloud.
3. The unit reviews and approves the migration work.
4. University Communications will conduct an initial training.
5. University Communications will conduct a process within Sitecore XM Cloud to launch each unit’s new site and then will sunset, or terminate, the Sitecore XP version of the site.
6. Units are then able to manage their website in Sitecore XM Cloud and make any content updates.

We recognize this type of change can impact unit budget requests, planning for the coming year, allocation of resources and more, and, therefore, wanted to communicate the change as soon as possible.

That said, we didn’t communicate the change until we were confident in what we were sharing. This included having confirmation regarding when the platform would be available, details on what the migration would involve and our general plan for moving forward. Once we were confident that the prework was going well and would be completed on schedule, we made the announcement.

Once Sitecore XM Cloud becomes available, units can start building new sites. We’ll be able to add in new sites alongside the migration work stream. That said, the same team that creates the site containers for migrating sites will be doing the work on site containers for new sites. So, we’ll need to fold the new sites into our schedule for site creation.

Bottom line: you don’t need to delay your new site plans until the end of the migration. You can keep moving forward.

Migration project staff resources will not be available to work on new websites. All new websites will be built by the units, but training and resources will be provided to ensure success.

Site migrations of prod sites will be completed by migration project staff.

For future site management, University Communications will provide training (via Teams) for all content authors. We also will have a new marketing technology website with on-demand training, documentation and reference materials.

The migration from Sitecore XP to Sitecore XM Cloud is centrally funded. There is no cost to your unit.

University Communications is working to develop new training and documentation. We will notify campus users when training sessions are open for registration. As of now, we anticipate training to be scheduled beginning in May 2024.

We plan to offer demos of the system once we have our first MSU website in production. These should be scheduled beginning in April.

You will want training. XM Cloud is an entirely new interface. We’ll work out a schedule for site builds and training once we’ve confirmed which sites are migrating. This process will take place in March. Training will likely be presented in groups to be most efficient. We’re revamping our training program by adding more documentation and resources and, in the future, we’ll add features like training videos. Training will be more broad than deep, with additional supportive resources available to meet units’ more specific, in-depth needs.

We need to retain support for Sitecore XP until all users have migrated.

However, new functionality will not be developed in the old system. Development resources will shift to Sitecore XM Cloud.

Training for new users on XP will be reduced as we ramp up training for XM Cloud users. Currently, we hold XP trainings weekly. You can expect this frequency to drop over time as more users shift into XM Cloud and more sites migrate away from XP.