Migrate from a Monolith Sitecore CMS to Headless: Audit

Akshay Sura - Partner

1 Mar 2022

In this video session, we talk about how to audit to help you migrate from a Monolith Sitecore CMS to Headless and Composable DXP.


Note: The following is the transcription of the video produced by an automated transcription system. 

Hi, this is Akshay Sura from Konabos. Today we'll be looking at our second of the video series looking at auditing while you're trying to move from a monolith Sitecore CMS to a headless more of a headless approach and composable dxp. So, we already established in the introduction video, which you can find on our website, as to why you would want to start looking more towards headless and composable dxp. What's the overall process to this video would mainly be talking about auditing, auditing your current environment.

Now, when I say environment, I mean, everything and anything. So, the first portion of it is investigation. So, investigate how the current process of getting something to the website affects, you know, from an IT perspective, from a marketing perspective, from a business perspective, investigate every single area, every single department, which indirectly or indirectly has something to do with one of your channels, which is your website. So, you're moving from a monolith, which is primarily your website channel. So, try to talk to every single one of these different groups figure out, hey, you know, we're trying to take on this new effort, we want to improve on what we've already done. Are there any thing you know, any issues, you're facing anything which we could be doing better anything which could be automated things we need to stop, you know, similar things stop, keep going start kind of scenario. So, dog pain points are super critical. And it's very easily forgotten. Again, when I say pain points, or any of these aspects, it doesn't necessarily mean the website team directly anything which directly or indirectly impacts the content on the web, which is one of your channels, it could be mobile tomorrow, because you're going composable.

So for instance, you might have a print department, they not did not necessarily they're gonna be dealing with your directly for web based content, but they might be using assets, which are high quality assets in their printing, which would, you know, they might have to interact with the web team in order to provide a lower end asset, for instance, so you need to keep them in mind a, a legalese department as well as product departments. So, by talking to all of them, maybe you'll learn a few pain points only, you know, what I get asked this every once a month, I have to generate these reports and provided or generate this Excel file. And provided is there a way we could automate it? Things of those sorts, so if you can figure out duplications, pain points, across the whole gamut, that would really help. While you're doing that, it's super important to document because this isn't a process which is done in a day, it's done over a short period of time, depending on how well you set yourself, I would say a few weeks at the most, at the least. So absolutely start documenting, keep people involved and do your findings in a proper way interviewing your team, as well as anyone who touches any piece of content, which the website provides.

As I always say, this is something which has to be this effort needs to be from the bottom all the way to the top, everyone needs to know why we're doing it. Why are we doing it, we're doing it to improve our process. We're doing it to stop duplication of effort, we're doing it so we can find efficiencies in our processes. We're doing it so that we can get best in breed or reuse or adapt using what we already use or find other technologies which might help things better. So, for instance, maybe your orders are not flowing back into your SAP system. Maybe there's automation there which we can do maybe the digital asset management isn't in place maybe we can put a dam in place so that not just your web channel, but every other channel including print can utilize these assets. So, but in order for us to do that everyone on the team and when I say team, anyone and everyone indirectly, who affects content in these different channels, which we are interested in, they need to be bought into why we are doing it. The leadership needs to provide ample support to everyone involved. So, everyone knows that this is something which is super serious. This is something which we have to do, and everyone does it because it's a common goal. So, the why is super important. Again, Any questions Do feel free to reach out to us we are doing this video series. So, this is the second one. We'll be going into the next phases once we're done with the auditing. Now it's time to look at how exactly are we going to look at our pain points and look at the current business architecture and in a web IT architecture and figure out how exactly to solve these pain points. I hope you enjoyed this video. Thanks again.

If you have any questions, please get in touch with me. @akshaysura13 on Twitter or on Slack.

Sign up to our newsletter

Share on social media

Akshay Sura

Akshay is a nine-time Sitecore MVP and a two-time Kontent.ai. In addition to his work as a solution architect, Akshay is also one of the founders of SUGCON North America 2015, SUGCON India 2018 & 2019, Unofficial Sitecore Training, and Sitecore Slack.

Akshay founded and continues to run the Sitecore Hackathon. As one of the founding partners of Konabos Consulting, Akshay will continue to work with clients to lead projects and mentor their existing teams.

Subscribe to newsletter