Analyze your Sitecore setup
The first step in migrating your Sitecore setup to WordPress is auditing your current Sitecore setup.
This audit lays the groundwork for a seamless Sitecore to WordPress transition, which you’ll realize as you read through the handbook.
However, this process is more than just a standard audit.
In addition to assessing your existing Sitecore setup, you also need to see WordPress in parallel. Doing so allows you to understand how the various components of your current Sitecore environment can be effectively recreated, redesigned, and seamlessly migrated to WordPress.
At rtCamp, we begin our migration projects with a “Discovery” stage, and auditing lies at the core of it.
Here’s how to conduct a step-by-step audit of your Sitecore setup.
Audit your overall Sitecore setup
There are two ways you could be using Sitecore: either (only) as a CMS or as a complete digital experience platform (or DXP).
So as the first step toward migrating your Sitecore site to WordPress, you need to audit your existing Sitecore setup and document everything you’re currently using Sitecore’s solutions for.
Here’s a quick list of Sitecore’s solutions for reference:
- XM Cloud (Alternatively, you may be using Sitecore’s other CMS solutions like Sitecore Content Hub One or its original CMS solution Sitecore Experience Manager.)
- Search (Sitecore’s search and discovery solution)
- CDP (Sitecore’s customer data management solution)
- Personalize (Sitecore’s personalization and testing solution)
- Content Hub (Sitecore’s DAM solution)
- Connect (Sitecore’s integration solution)
There’s more:
In addition to these solutions, Sitecore also offers apps to add to their DXP solutions. For example, with Sitecore Send, you can bring email automation to your Sitecore setup.
So factor in any Sitecore apps too that you may be using.
At the end of this step, you should know all the native Sitecore solutions and apps that you use in your existing Sitecore stack.
Once you list these, you need to find comparable alternatives to use with your new WordPress stack.
For example, if you’re using Sitecore’s Personalize, you’d need to find a comparable solution that will work with the CMS you’re migrating to—Uberflip, for instance.
Fill out this table with your current CMS features and functionalities and any solutions you can use on WordPress to recreate them:
| What Sitecore solutions does your current Sitecore setup use? | Notes | How you’ll be migrating them over to WordPress |
| The CMS | What Sitecore CMS are you using? 1) Sitecore Experience Manager 2) Content Hub One 3) Sitecore Experience Manager Cloud (XM Cloud) | There’s—thankfully—only one WordPress CMS! |
| Search | Are you using Sitecore Search? | Explore a comparable workaround on WordPress. |
| CDP | Are you using Sitecore CDP? | Explore a comparable workaround on WordPress. |
| Personalize | Are you using Sitecore Personalize? | Explore a comparable workaround on WordPress. |
| Content Hub | Are you using Sitecore Content Hub? | Explore a comparable workaround on WordPress. |
| Connect | Are you using Sitecore Connect? | Explore a comparable workaround on WordPress. |
Audit your third-party solutions
You might be using a number of third-party solutions too with your Sitecore setup. So after auditing all the native Sitecore solutions used in your setup, audit your setup for any third-party solutions you may be using.
Start by listing all the third-party solutions that you’ve integrated with your Sitecore instance, for example:
- Sales solutions like Salesforce
- Marketing automation solutions like HubSpot
- Collaboration solutions like Slack
- Analytics solutions like Google Analytics, Clicktale, Parse.ly, etc.
- Performance solutions like Cloudflare
Fill out this table with the third-party solutions you’ve identified in your current Sitecore setup. This will help you keep track of all your integrations as you plan your transition to WordPress:
| Sales solutions (for example, Salesforce Marketing Cloud) | Salesforce Marketing Cloud: Currently implemented through the Sitecore Connect™ for Salesforce Marketing Cloud. | You can go with WordPress VIP for Salesforce. (By the way, we’ve developed this solution! Check out more on this here.) | Outline your approach for managing any expected API challenges, authentication methods, or compatibility issues (among other stuff!). |
| Marketing automation solutions | What integrations are you using to bring your marketing automation solutions to Sitecore? | What are the comparable integrations in WordPress? | Notes, if any. |
| Collaboration solutions | What integrations are you using to bring your collaboration solutions to Sitecore? | What are the comparable integrations in WordPress? | Notes, if any. |
| Analytics solutions | What integrations are you using to bring your analytics solutions to Sitecore? | What are the comparable integrations in WordPress? | Notes, if any. |
| Performance solutions | What integrations are you using to bring your performance solutions to Sitecore? | What are the comparable integrations in WordPress? | Notes, if any. |
Also:
List any third-party integrations that you lack in your current setup and need to build on your new WordPress stack.
Audit every Sitecore function/feature you’re using (both built-in and custom)
Most of the key Sitecore CMS features will be available right out-of-the-box in WordPress.
Some, however, may not come built-in with WordPress.
Take Sitecore’s forms, for instance. Sitecore makes forms available as part of many of its solutions. So if you use Sitecore’s forms feature, you’d need to see how to recreate them on WordPress (as WordPress doesn’t ship with a form builder). That said, you’ve some really awesome forms plugins to bring forms to your WordPress stack.
Now, forms are an essential feature—but some may not be.
For example, Sitecore comes with a co-editing feature (essentially enabling Google Docs’ like collaboration on a Sitecore item). WordPress doesn’t bring this by default. So even if you’re using this now, it’s not a deal-breaker to not find it on WordPress.
Fill out this table with the key Sitecore features you’re currently using, noting which ones are available out-of-the-box in WordPress and which may require additional plugins or custom solutions. If you’ve extended Sitecore’s CMS’s functionalities through plugins or custom code, add those too. This will help you assess how to recreate essential functionalities during your migration to WordPress:
| Migrating features/functions from Sitecore to WordPress | How existing/desired features/functions work on Sitecore | How can these existing/desired features/functions be moved over to WordPress | Sitecore to WordPress: Migrating features/functions |
| Visual editing (WYSIWYG) | Comes built-in with Sitecore’s Pages editor (in Sitecore XM Cloud) | Comes built-in with WordPress’s Gutenberg editor | Already there! |
| Forms | Comes built-in in Sitecore XM Cloud | Available via plugins | You could go with, say, Gravity Forms on WordPress to recreate the forms system. |
| Co-editing | Comes built-in in Sitecore XM Cloud | Doesn’t ship with WordPress. | May be lost in the migration. |
| Any other feature(s) you may be using | – | – | – |
You get the drift.
Also:
List any features/functions that you lack in your current setup and need with your new WordPress stack.
Audit every workflow running between your Sitecore setup and the rest of your tech stack
Your CMS sits at the intersection of your business processes: sales, marketing, service, etc.
And so naturally, you may be having many workflows that might be running through your Sitecore CMS (and your Sitecore setup, in general).
For example, maybe you could be using Sitecore’s Send solution to power email automation. Perhaps this how your workflow goes this like:
- A user fills out a form on your Sitecore website
- The email gets sent to Sitecore Send’s database
- And the Sitecore Send delivers an automated (personalized) response
To successfully migrate from Sitecore to WordPress, you need to rebuild these workflows into your new WordPress stack.
Use this table to list all your existing Sitecore workflows or automations and how you’ll possibly move them over to WordPress:
| Workflows | How the workflow currently works inside your current Sitecore setup | How will you migrate these workflows from WordPress to Sitecore? |
| Workflow #1 | ||
| Workflow #2 | ||
| Workflow #3 |
Also:
List any workflows that you lack in your current setup and need to build on your new WordPress stack.
Audit your content
Once you’ve audited your overall Sitecore stack, it’s time to catalog all the content that lives on your Sitecore CMS. These would be:
- Pages
These are your Sitecore website’s pages like your homepage, about, contact, etc. Your landing pages also go here. Any personalized pages you may be having also belong here.
- Posts
These are all the posts published on your Sitecore website.
- Media
These are images, videos, audio files, and documents that you might have uploaded to your Sitecore CMS/DAM.
- Custom post types
These are any specialized content types created for specific needs (e.g., portfolios, testimonials, events, etc.).
- Taxonomies
Under taxonomies, you need to audit your Sitecore setup’s categories and tags that you use to organize your content.
- User data
This is all the information and settings associated with user accounts on your current Sitecore setup.
- Comments
This is any user-generated content on your different posts and pages.
- Metadata
This is data about data—for example, information like author, publish date, and SEO descriptions for a content asset.
- Forms
Your forms (e.g., contact forms, surveys) data too needs to be reviewed.
- Widgets/blocks
These would be the small content elements placed in various areas of your Sitecore site, often used inside sidebars or footers. These could also be content coming from legal disclaimer widgets and more.
Use the following table to track all the content that lives on your current CMS setup. Also, as you conduct your content audit, flag any obsolete content that won’t need to be transferred to your new WordPress site. To fill this table, refer to your sitemap or use an SEO crawler like Screaming Frog.
| Content type | Description | Current URL/Location | Notes/Comments |
| Pages (# of assets) | Homepage, About, Contact, Landing pages, Personalized pages. | A spreadsheet linking to all the individual links/data | Notes, if any. |
| Posts (# of assets) | All published posts on the Sitecore website. | A spreadsheet linking to all the individual links/data | Notes, if any. |
| Media (# of assets) | Images, videos, audio files, documents uploaded to the Sitecore CMS | A spreadsheet linking to all the individual links/data | Notes, if any. |
| Custom post types (# of assets) | Specialized content types (e.g., portfolios, testimonials, events). | A spreadsheet linking to all the individual links/data | Notes, if any. |
| Taxonomies (Categories and tags) | Categories and tags used to organize content. | A spreadsheet linking to all the individual links/data | Notes, if any. |
| User Data | Information and settings associated with user accounts. | A spreadsheet linking to all the individual links/data | Notes, if any. |
| Comments | User-generated feedback on posts and pages. | A spreadsheet linking to all the individual links/data | Notes, if any. |
| Metadata | Information about content (e.g., author, publish date, SEO data). | A spreadsheet linking to all the individual links/data | Notes, if any. |
| Forms | Any forms data you may be collecting from your contact forms, survey forms, etc. | A spreadsheet linking to all the individual links/data | Notes, if any. |
| Widgets/Blocks | The ad hoc content elements for various site areas (e.g., sidebars, footers). | A spreadsheet linking to all the individual links/data | Notes, if any. |
Audit your user profiles
Document your existing user roles along with access levels and capabilities in your Sitecore setup and see how they can be mapped to WordPress. The actual user data migration will be handled during the content migration stage.
| Existing user roles on Sitecore | Access levels | Notes about moving them to WordPress | |||||||
| Media upload | Media download | Media Publish | CMS Edit | CMS Delete | CMS/DAM View | Content Publish | Distributor Portal | ||
| Admin (Specify whether this is a default or custom role on Sitecore.) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | On WordPress, too, the admin user role will retain all the current capabilities. |
| Content Authors (A default Sitecore role) | No | Yes | No | Yes | No | Yes | No | No | On WordPress, you get a comparable default “Author” role. In WordPress, Authors by default have the permission to publish their own page/post. Customizations are required to revoke the publish capability. And so on. |
| Contributor (A default Sitecore role that can be granted various access levels/capabilities) | No | Yes | No | No | No | Yes | No | No | This, too, is a default WordPress Role. In WordPress, Contributors can add new posts but can’t publish them. The bespoke access levels/capabilities will need to be custom coded. |
Audit your media management
A lot of times when we work on migration projects, we see our clients using a third-party Digital Asset Management (DAM) system for managing their media files.
A DAM simplifies the entire asset management process—from uploading and organizing files to standardizing their usage and making them easily searchable. All this translates to a much higher productivity.
That’s why when migrating a website to WordPress, especially a Sitecore website to WordPress that may be using Sitecrore’s native DAM solution (Content Hub), it’s important to see what WordPress’s default media library is capable of.
In general, with custom coding and enhancements, you can effectively turn your WordPress media library into a powerful DAM system that meets your organization’s unique media management needs—all without relying on third-party DAM solutions. From enforcing a certain kind of file names to setting rules for auto-resizing and enhancing search, a lot is possible with the default WordPress media library.
That said, you can always integrate your WordPress stack with a third-party DAM of your choice.
Use this table to document your current DAM usage and if the WordPress media library, with custom enhancements, can meet your needs:
| Features | What’s available by default with the WordPress media library | Enhancements that may be needed on WordPress |
| Advanced organization | Categories and tags | Custom taxonomies, metadata fields |
| Custom metadata | Not supported by default | Custom fields for copyright, usage rights, etc. |
| Enhanced search | Basic search by title | Custom search features using metadata, faceted search |
| Automated workflows | None by default | Customizations for automated resizing, format conversion, etc. |
| User permissions | Basic role-based permissions | Customizations for granular control over specific files and actions |
| Version control | Basic media replacement | Customizations for file versioning with history |
| Bulk actions | Basic bulk actions | Customizations for bulk downloads, advanced bulk editing, etc. |
| Analytics and reporting | None by default | Customizations for custom analytics and reporting tools |
| Access control | Tied to user roles | Customizations for permission controls by asset or category |
| Asset previews and thumbnails | Basic previews | Customizations for enhanced preview options for various file types |
Audit for SEO
Finally, as the last step of your auditing process, audit your existing SEO scape. There are quite a few parts to this and to transfer your existing SEO equity to your new WordPress site (and even improve it).
Document your site structure
Create a sitemap if you don’t have one already. Depending on your Sitecore setup, there may be a Sitecore module that already provides a sitemap for your instance. Alternatively, you can generate one using Sitecore PowerShell (more on this in the content migration section). You could also use a third-party tool to create it.
Additionally, document your current content hierarchy, as this will need to be reflected on your new WordPress site. A visual representation of the site structure, highlighting key pages, categories, and navigation paths, can be helpful. If you’re planning a redesign, consider how you can improve the hierarchy for better SEO.
Also, document your navigation menus and breadcrumb trails—or redesign them to optimize user experience and search performance.
Inventory all URLs
Use tools like Sitecore PowerShell scripts (or others mentioned later in the migration section) to audit and document your website’s existing links. Additionally, perform a backlink analysis.
| Content asset | Sitecore URL | Backlinks to this content asset |
| Pages (# of assets) | /about-us Note: Use a spreadsheet to track all pages but list all the key ones in this table | A spreadsheet linking to all the backlink data |
| Blog posts (# of assets) | /content/blog/article-title Note: Use a spreadsheet to track all posts | A spreadsheet linking to all the backlink data |
| Service page | /content/service/service-abc | A spreadsheet linking to all the backlink data |
| Service page | /content/service/service-cdf | A spreadsheet linking to all the backlink data |
| General site page | /contact-us | A spreadsheet linking to all the backlink data |
| General site page | /privacy policy | A spreadsheet linking to all the backlink data |
Do a thorough content audit
Use your Analytics tools for reporting on how your content is currently doing.
- Take a report of your content assets as they rank for your target keywords. Also, see your backlinks (because if you change links but don’t use redirects, you may want to reach out to some third-party sites for rebuilding them).
- If you find any opportunities for improvement—for example, refreshing a piece of content, adding SEO-friendly meta descriptions for some, or simply optimizing some articles for more keywords—this is a good time to document them.
- If you find content gaps, again, this is a good time to work on them.
Audit for performance
Run a few performance tests to establish benchmarks for post-migration comparisons:
- PageSpeed testing
Use tools like Google PageSpeed Insights or Pingdom to measure loading times. You’d need to maintain or improve these with your new WordPress stack.
- Mobile friendliness
Check for mobile friendliness.
- Server Response Time
Monitor server response times to identify potential bottlenecks.
- Load testing
Simulate traffic spikes to evaluate how your site performs under stress—this data can be useful for benchmarking load handling post migration.
- User experience (UX) testing
If you’ve conducted any user testing on your website, document your findings on your overall Sitecore website usability. See how your findings can be implemented on WordPress. Also, monitor bounce rates and time on site to identify areas for improvement—usually these are indicators about usability.
- Crawlability and indexability
Also, use tools like Screaming Frog or Google Search Console to check for crawl errors, broken links, and redirects.
Review your SEO metadata
These are your meta titles, meta descriptions, alt texts, etc. Search engines use meta data to understand what a content asset (page or post) is about. They also use this data when they show you in the search results. To move over your SEO equity to your WordPress site, it’s important to move all your SEO metadata too.
Audit your SEO schema data
Your schema data is any structured data that you’ve implemented on your Sitecore website.
Search engines use structured data to understand your content asset’s specifics—for example, if it’s a product, to fetch its pricing. Search engines also use your schema implementation to display rich snippets and rich results, which can, in turn, influence search clicks.
Technically, your schema markup/structured data is part of SEO metadata and a single plugin can take care of importing both on WordPress.
