In this part of the migration series, I am going to look at migrating an existing Sitecore Experience Platform (XP) solution that has been built as a classic Sitecore MVC implementation with simple personalization implemented.
The scenario breakdown:
- Single MVC site built on Sitecore XP 8.2
- Basic session-based personalization in use, primarily using Geo IP to determine user location and campaign IDs in the URL
- No SXA or Sitecore JSS in use
- No custom site search, using third party search engine for site search
- Development team is all .NET developers, no desire to move to a JavaScript framework
Follow the series to look at different Sitecore XM and XP scenarios and how you can gradually migrate your Sitecore platform solution over to a composable DXP architecture.
The goal is to walk through the example migration and highlight for you:
- What challenges will you face along the way?
- What options are available and when do they make sense?
- What are the benefits of making certain changes to your architecture?
Every project is a little different, so hopefully this series can help you understand some of the questions to ask, and what options you have, to guide you in the right direction.