/handbook/sitecore-to-wordpress-migration-guide/frontend-migration/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
Discovery
Strategic consultancy & project roadmap
Growth Services
On demand development & consultation
Site Maintenance
Annual maintenance. Done for you
QE Services
Testing across SDLC for assured quality
Hosting Migration
Move to a performant hosting with zero downtime
WooCommerce
Enterprise commerce delivered without lock-in
AI
Unlock real use cases and integrations
All Services
A suite of services for any need
Technology STACK
eCommerce
Scale your e-commerce with WooCommerce, integrations, and custom extensions for growth.
EasyEngine
Server management tool that makes using WordPress on Nginx easy.
Web Auditor
Performance Audit & Insights for your Website.
rtMedia
A complete media management plugin for WordPress.
Resources
About Us
CLEAR
Resources Sitecore to WordPress migration guide Frontend migration
Topics
On this page
- Sitecore to WordPress migration guide
- Audit your Sitecore setup
- Evaluate the right architecture
- Choose the right hosting
- Setup environments for migration
- Pre-migration backup
- Frontend migration
- Backend migration
- Content migration
- Preserve SEO equity
- Quality assurance
- Post-migration considerations
- How can rtCamp help
Auditing the frontend
The theme
Templates
Components
Migrating the frontend from Sitecore to WordPress
Set up a starter WordPress theme
Create the main navigation, header, and footer
Design Gutenberg blocks for core design elements
Create predefined layouts with regular Gutenberg blocks
Build out your pages and page templates
Integrate third-party plugins and APIs
Post-migration frontend considerations
Last updated on May 25, 2026
Migrating your Sitecore frontend to WordPress
With the key project logistics out of the way, let’s dive into the actual Sitecore to WordPress migration process.
To begin, you’ll start working on the frontend.
This process starts with evaluating the current design, assessing how it can be effectively recreated in WordPress, and identifying any opportunities for improvement along the way.
Auditing the frontend
After you’ve determined the architecture of your WordPress setup, it’s time to evaluate the frontend so it can be moved over to WordPress.
By the way, at this stage, you may also want to consider a redesign or refresh, since you’ll be recreating the frontend entirely from scratch anyway.
So let’s see you can rebuild your user-facing experiences as you move to WordPress from Sitecore.
The theme
If you want to retain your existing design, the best way to go about it is to create a custom WordPress theme.
In most cases, a custom WordPress theme can replicate the exact look of your existing Sitecore website’s frontend, down to the pixel.
In case you go with a redesign, again, you can create a WordPress theme from scratch.
Templates
It’s likely that you may have added or customized the existing Sitecore templates for setting up your marketing collaterals like product pages, landing pages, case studies, and more to your website.
With WordPress, you’ll need to recreate these templates using WordPress’s custom posts feature. WordPress’s support for custom posts combined with the Gutenberg editor gives you lots of design possibilities inside the CMS.
Finally, you’ve to think at the component level.
Components
In addition to templates, you’d probably also have components on your Sitecore website that would let you add quick design blocks to your blogs and pages. Think components for content like testimonials, pull quotes, FAQs, etc.
To move these design elements to WordPress, you’d have to think at the block level, components on Sitecore are blocks on WordPress.
Side note: When you get to the actual migration stage (as we will in just a bit), you can have a frontend team dedicated to just recreating your design. This team can focus on recreating your web front while the other teams work on the rest of the migration (the backend/integrations and the content).
In addition to these considerations:
Look at any design elements you’re currently adding to Sitecore through custom code or third-party design widgets (like sliders, timelines, pricing tables, and more). These may need custom coding on WordPress as well.
Similarly, any frontend elements rendered through third-party solutions—such as videos from Vimeo—should also be factored into the migration process.
Essentially, anything that appears on your frontend needs to be adapted for WordPress.
As you can see, this process is largely manual.
Since you’re moving to WordPress and building your website’s frontend from scratch—whether you’re redesigning or not—now’s the perfect time to think modularly about your design.
By doing this, you won’t just end up with a WordPress theme.
Instead, by recreating your design block by block, approaching your frontend with Gutenberg blocks, you create much more than a theme—you build a fully branded page builder that has all the blocks you need to create stunning pages and marketing collateral in minutes, without needing IT support.
So keep that in mind.
In fact, that’s exactly how we approach WordPress theme design: one block at a time.
Migrating the frontend from Sitecore to WordPress
Now that you have a clear picture of what you need to recreate your website (design) on Sitecore, it’s time to actually get to the work.
Set up a starter WordPress theme
Begin with a barebones theme skeleton that works your design foundation. This takes care of basic templating that you can build upon and style as you go.
Create the main navigation, header, and footer
Start by building out your WordPress site’s primary navigation menu, header, and footer. These elements give structure to your site and accelerate dev speed. Make sure the header and footer are dynamic, allowing you to adjust them easily through the WordPress customizer or within Gutenberg blocks.
Design Gutenberg blocks for core design elements
Refer back to your discovery documentation, which should detail all the Sitecore elements you’ll need to recreate. Use the Gutenberg editor to design custom blocks for all the components you documented such as headlines, copy blurbs, pull quotes, galleries, testimonials, and service sections, among others. Ensure these blocks are flexible and reusable, allowing for easy customization within the Block Editor.
Create predefined layouts with regular Gutenberg blocks
Assemble predefined layouts by combining your custom Gutenberg blocks into sections that are commonly used across your pages. This might include multi-column sections, CTAs, or image grids. These layouts streamline the page-building process, offering consistency and allowing content editors to quickly put together pages without needing design skills.
Build out your pages and page templates
With your Gutenberg blocks and layouts in place, start putting together your site’s pages. Use them to construct your new homepage, landing pages, and all the other core pages that you identified above.
Also, develop reusable page templates for the different types of pages you routinely create. This could include templates for landing pages, for example.
Integrate third-party plugins and APIs
Add any necessary third-party integrations, such as CRM forms, video hosting services, or social media platforms, that show up on the frontend. You’ll also need to style them so they align with your theme’s branding and design language.
By following these steps, you’ll effectively rebuild your Sitecore frontend in WordPress, tapping the flexibility of Gutenberg to create a dynamic and modular design that is easy to manage and scale.
Post-migration frontend considerations
We’ll dive into the details of frontend QA in a later chapter, covering essential checks to confirm that your new site is meeting your design and performance standards.
Credits
Disha Sharma
Author
Disha Sharma
Author
Disha Sharma is a Content Writer at rtCamp with over a decade of experience at the intersection of technology, digital marketing, and enterprise content strategy. Her WordPress roots run deep, her …
Salman Ravoof
Editor
Salman Ravoof
Editor
Salman Ravoof is a Senior Technical Content Writer at rtCamp. He’s a self-taught developer who switched to writing, which means he’s actually built the things he writes about and broken a few produ…
Good Work. Good People.
Industry partnerships
Compliance certifications
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Company
Solutions
Subscribe to our newsletter and get a few email updates every month.
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Cookie Consent
We value your privacy
We use cookies to give you the best possible experience. By clicking “Accept,” you consent to our use of cookies to improve site functionality, analyze usage, and personalize content and communications. Your privacy matters to us, and we are committed to handling your data responsibly and transparently. Please check our Privacy Policy for more details.
Manage PreferencesDon’t AllowAllow All
Why do we use cookies?
×
By clicking "Accept" or "Decline All" at the bottom, you consent to the use of cookies and other tools as described in our Cookie Policy in accordance with your settings and accept our Terms of Service.
Toggle EssentialEssential
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
30 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
Toggle CloudFlareCloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
Name
Description
Duration
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
Toggle CommentsComments
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Toggle GodamGodam
GoDAM" is primarily a specialized WordPress plugin and media management service designed to enhance video hosting, marketing, and asset management directly within the WordPress dashboard.
Service URL: godam.io (opens in a new window)
Name
Description
Duration
user_image
Temporarily stores the path to the user's avatar or profile picture for quick rendering in the website header.
session
user_id
Stores the numerical ID of the logged-in user to maintain session continuity and basic site operations.
session
full_name
Stores the logged-in user's display name to personalize the site interface without needing database queries.
session
system_user
First-party cookie used to store basic application state identifying the current system user role.
session
sid
A generic session ID cookie used to maintain user state and functionality as the visitor navigates through the site.
session
Toggle Google reCAPTCHAGoogle reCAPTCHA
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Toggle Google Tag ManagerGoogle Tag Manager
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
Toggle StatisticsStatistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Toggle Factors AIFactors AI
Factors.ai is a B2B account intelligence and marketing analytics platform that helps Go-To-Market (GTM) teams identify anonymous website visitors, track buyer journeys, and measure the ROI of marketing campaigns.
Service URL: www.factors.ai (opens in a new window)
Name
Description
Duration
_fuid
It is sent to capture session details and track user behavior across your website to provide behavioral data and intent signals.
1 Year
Toggle Google AnalyticsGoogle Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
Name
Description
Duration
FPGSID
Stores a session or user identifier to track how visitors interact with a website. This helps Google Analytics measure website performance, user engagement, and usage patterns.
Session
FPLC
Used by Google Analytics to link visitor interactions and sessions across multiple related domains.
20 hours
FPID
A server-side Google Analytics cookie used as an alternative user identifier when third-party cookies are restricted.
2 years
_ga
ID used to identify users
2 years
_ga_
ID used to identify users
2 years
Toggle Jetpack StatsJetpack Stats
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Service URL: automattic.com (opens in a new window)
Name
Description
Duration
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_qs
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
Toggle Microsoft ClarityMicrosoft Clarity
Clarity is a web analytics service that tracks and reports website traffic.
Service URL: clarity.microsoft.com (opens in a new window)
Name
Description
Duration
CLID
Identifies the first-time Clarity saw this user on any site using Clarity.
12 months
ANONCHK
Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.
Session
_clck
Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.
12 months
_clsk
Connects multiple page views by a user into a single Clarity session recording.
12 months
Toggle Parse.lyParse.ly
Parse.ly is a content analytics platform that helps publishers optimize audience engagement and content performance.
Name
Description
Duration
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
_parsely_session
JSON document storing information identifying a browsing session according to Parsely’s proprietary definition
30 minutes
_parsely_visitor
JSON document uniquely identifying a browser and counting its sessions
13 months
Toggle SalespanelSalespanel
Salespanel is a B2B marketing and sales software that identifies, tracks, and qualifies website visitors and leads in real-time using first-party data. It helps businesses monitor customer journeys, score leads based on behavior, and syncs this data with CRMs (like Pipedrive or HubSpot) to improve conversion rates.
Service URL: salespanel.io (opens in a new window)
Name
Description
Duration
track_uid
Identify and tracking a lead
12 moths
Toggle MarketingMarketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Toggle Bing / MicrosoftBing / Microsoft
Bing, powered by Microsoft, is a search engine providing web, image, video, and map search capabilities.
Name
Description
Duration
MR
Used to collect information for analytics purposes.
6 months
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
10 minutes
SM
Used by Microsoft in synchronizing the MUID across multiple Microsoft domains to track users for advertising.
session
MUID
Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.
1 year
Toggle DoubleClick/Google MarketingDoubleClick/Google Marketing
A comprehensive digital advertising platform for managing campaigns, optimizing performance, and analyzing audience data.
Name
Description
Duration
IDE
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite
2 years
ar_debug
Store and track conversions
Persistent
Toggle LinkedInLinkedIn
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
UserMatchHistory
Used by LinkedIn Ads to synchronize and match user IDs across different ad networks and data providers.
30 days
Toggle LinkedIn InsightLinkedIn Insight
LinkedIn Insight is a web analytics service that tracks and reports website traffic.
Service URL: www.linkedin.com (opens in a new window)
Name
Description
Duration
li_sugr
Used to make a probabilistic match of a user's identity.
90 days
lidc
Used for routing and session management.
24 hours
Toggle LiveIntentLiveIntent
LiveIntent provides a platform for email advertising and identity-driven marketing solutions.
Name
Description
Duration
_lc2_fpi_js
Companion cookie to _lc2_fpi used by JavaScript to facilitate cross-domain ad tracking and user identification.
1 year
_lc2_fpi
First-party tracking cookie usually associated with LiveRamp to identify users across devices for targeted advertising.
1 Year
_li_ss
Sets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
1 month
lidid
Collects data on visitors' behaviour and interaction - This is used to make advertisement on the website more relevant. The cookie also allows the website to detect any referrals from other websites.
2 years
Toggle Cookie PolicyCookie Policy
You can find more information in our Privacy Policy.
Allow AllDecline All
Accept