Sitecore XM Cloud Healthcare Case Study: Next.js Migration, Search & Personalization

Enterprise healthcare websites often grow into complex digital ecosystems containing provider directories, medication and formulary information, pharmacy search, healthcare plans, educational content, member experiences, personalization, forms, and multiple third-party integrations.

As these platforms evolve, a traditional CMS architecture can become increasingly difficult to maintain.

Murmu Software Infotech contributed to the modernization of a large enterprise healthcare ecosystem by migrating it from Sitecore XP to Sitecore XM Cloud, rebuilding the frontend with Next.js and Sitecore JSS, introducing GraphQL-driven headless delivery, modernizing healthcare search, and creating a more flexible foundation for future digital experiences.

The Challenge: A Complex Legacy Healthcare Ecosystem

The existing Sitecore XP implementation supported far more than a conventional marketing website.

The ecosystem included healthcare marketing experiences, member-facing functionality, provider and pharmacy discovery, drug and formulary search, medical-plan journeys, personalization, integrations, and complex business modules.

Modernize Healthcare Experiences With XM Cloud

Transform complex healthcare platforms with XM Cloud, Next.js, Sitecore Search, personalization, Content Hub, and scalable headless architecture for digital growth.

Sitecore XM Cloud development team

Over time, the legacy architecture created challenges around component maintenance, developer dependency, content flexibility, frontend modernization, and the ability to evolve sophisticated search experiences.

Migrating such a platform therefore required more than transferring pages into a cloud CMS.

The team needed to determine which legacy components could be restructured, which experiences required headless redevelopment, how third-party integrations would operate in the new architecture, and how healthcare search and personalization could evolve without disrupting important user journeys.

Migration Discovery and Architecture Planning

The modernization began with a detailed discovery phase.

Existing Sitecore components, business modules, search workflows, forms, APIs, and third-party integrations were analyzed before development started.

This created a clearer migration map between the existing Sitecore XP implementation and the target XM Cloud architecture.

That planning is particularly important for XM Cloud migrations because legacy MVC-based Sitecore implementations cannot simply be moved unchanged into XM Cloud. Sitecore’s own migration guidance explains that traditional implementations generally require frontend redevelopment into a JSS-based headless architecture, with content and layout delivered through Experience Edge.

Rebuilding the Platform with Sitecore XM Cloud

The presentation layer was rebuilt using reusable Sitecore XM Cloud JSS components.

The implementation included custom templates, data sources, JSON renderings, dynamic rendering workflows, and extensions to selected out-of-the-box components.

This created a more reusable component ecosystem where healthcare marketing and content teams could manage structured experiences without requiring developers to hard-code every page variation.

The migration therefore improved not only the underlying technology but also the relationship between content operations and engineering.

Next.js Headless Frontend

Next.js became the rendering layer for the modernized healthcare experience, supported by Sitecore JSS and Tailwind CSS.

This decoupled the frontend from the CMS runtime and created greater flexibility around responsive healthcare interfaces, reusable components, SEO-oriented rendering, deployment, and future frontend development.

Sitecore’s current JSS architecture supports Next.js applications consuming Sitecore content through GraphQL-aware services and Experience Edge, allowing the CMS and frontend application to operate as separate but connected parts of the digital platform.

GraphQL-Driven Content Delivery

GraphQL was used for component-level and dynamic content retrieval.

Instead of every component depending on one rigid page response, components could retrieve the structured content required for their individual experience.

Sitecore JSS officially supports GraphQL for layout, dictionary, sitemap, and component-level data retrieval, making it well suited to complex headless experiences where different healthcare components need different data structures.

Modern Healthcare Search and Discovery

Search was one of the most important areas of modernization.

The platform included experiences for discovering healthcare providers, pharmacies, medications, formularies, plans, and other healthcare information.

Sitecore Search was configured to support more relevant search experiences, structured filtering, and faster discovery across large healthcare information sets.

For medication-related experiences, users could search approved drug and formulary information and surface relevant alternatives or related entries based on the available source data.

The important distinction is that search supports information discovery; it should not be positioned as independently making clinical treatment or medication decisions.

Provider, Pharmacy and Plan Journeys

The modernized architecture also supported specialized healthcare finder experiences.

Users could navigate provider information, pharmacy availability, healthcare plans, and other structured healthcare data through purpose-built interfaces rather than relying solely on generic site search.

This is where the value of headless architecture becomes especially clear: Sitecore manages structured healthcare content while Next.js and integrated APIs can deliver focused application-like experiences around that content.

Content Hub and Personalization

Sitecore Content Hub was incorporated to support centralized digital-asset management, giving teams a stronger foundation for managing approved images, PDFs, videos, and other healthcare assets.

Personalization capabilities were also implemented to support more contextually relevant journeys based on configured business rules and experience requirements.

Cloud Deployment and Composable Architecture

The final platform combined Sitecore XM Cloud, Next.js, JSS, GraphQL, Sitecore Search, Content Hub, third-party healthcare integrations, XM Cloud Deploy, and Vercel.

This created a composable architecture where content management, frontend delivery, search, digital assets, personalization, and external healthcare services could evolve more independently.

Business Impact

The modernization transformed a legacy healthcare Sitecore implementation into a more flexible headless digital platform.

The new architecture created a stronger foundation for reusable content, modern frontend development, provider and medication discovery, personalization, cloud delivery, and future healthcare integrations.

Most importantly, this project demonstrates that migrating healthcare organizations to XM Cloud is not simply a CMS upgrade.

It is an opportunity to redesign how content, search, APIs, personalization, digital assets, and patient or member information journeys work together across the entire healthcare digital ecosystem.

Planning a Sitecore Healthcare Modernization?

Murmu Software Infotech provides Sitecore XM Cloud migration, healthcare Sitecore development, Next.js and JSS engineering, Sitecore Search, Content Hub integration, GraphQL development, personalization, API integration, and ongoing Sitecore support.

Whether you are modernizing Sitecore XP, rebuilding an existing healthcare portal, improving provider discovery, or planning an XM Cloud migration, we can help define the architecture and migration roadmap around your existing healthcare ecosystem.

Talk to our Sitecore healthcare team to build a more searchable, composable, and future-ready digital experience.