Decide if you want to retain or switch your existing Sitecore architecture
Depending on the Sitecore CMS you’re using, you may be using Sitecore as one of the following:
- a traditional CMS solution
- a headless CMS solution
- a hybrid CMS solution
Sitecore offers a bunch of CMS solutions, all of which offer different architectures.
| On a side note: You’d expect migrating between Sitecore’s CMSs to be seamless—hey they’re all coming from Sitecore after all!—but you’re looking at complete (and some very resource-intensive) replatforming if you want to switch between them. For example, if you wanted to migrate from Sitecore’s traditional CMS to Sitecore’s (latest cloud-native, headless, SaaS content management solution) XM Cloud, you’re looking at complete replatforming. |
But WordPress is an “agile CMS.”
Which means it offers you implementation in all three ways: traditionally (in a monolithic setup), headlessly (by separating the content management and content delivery aspects), and in a hybrid setup (by separating the content management and content delivery aspects but while still supporting web experiences through the WordPress environment).
Not just that, with WordPress, you can even switch between the different architectures if your needs change.
That said, migrating is a great time to reevaluate how you want to build your new CMS architecture.
If you decide to implement WordPress in a headless or hybrid setup, you’re looking at some more planning. That’s because you may be looking at multiple “heads” now and that means additional frontend logistics to work out. You’ll also need to consider frontend hosting (a service like Vercel, for example).
You can read more about how Sitecore and WordPress compare in their approach to headless architecture in our Sitecore vs WordPress handbook.
