/handbook/sanity-to-wordpress-migration/process-timeline-team/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
OnePress
Unify multiple brands on one governed WordPress platform.
Design & UI/UX
Gutenberg-native UX, UI, and design systems for visitors and editors.
WordPress Modernization
Modernize WordPress for better performance, architecture, and AI readiness.
WordPress as a DXP
WordPress as a composable DXP when monolithic systems no longer cut it.
Headless WordPress
Omnichannel content delivery without sacrificing marketing autonomy.
Frappe/ERPNext
Build scalable ERP and custom applications, from implementation to ongoing support.
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 Sanity to WordPress migration guide Migration process, timeline & team
Topics
On this page
- Sanity to WordPress migration guide
- Business case for migration
- Migration process, timeline & team
- Planning the migration
- Pre-migration setup
- Frontend, backend & content migration
- Quality assurance
- Site launch
- Post-migration checks
- How can rtCamp help
Frontend migration
Setting up WordPress for frontend delivery
Recreating your design and interactivity
Choosing theme
Backend migration
Content Migration
Exporting content
Mapping and transforming
Handling media and SEO
Timeline
Discovery & analysis (W1–W2)
Application design (W2–W4)
Development & unit testing (W3–W8)
Migration script development (W2–W8)
SIT execution & support (W5–W11)
Content migration (W7–W12)
User acceptance testing (W10–W13)
Deployment to the live environment (W13–W15)
Post-production support (W15–W16)
Team
1) Project manager (PM)
2) Engineering Manager (EM)
3) UI/UX Designers
4) Backend engineers
5) Frontend engineers
6) QA engineers
Wrapping it up…
Last updated on Aug 19, 2026
Sanity to WordPress migration: Process, timeline and team
Planning a migration from Sanity to WordPress can feel complex, but breaking it down into clear phases makes it manageable. In this section, we outline a high-level snapshot of how the migration process works, focusing on the key stages and what you can expect. A detailed assessment of your current Sanity setup is essential for a smooth transition, but let’s first concentrate on the structured migration process itself.
Our migration approach is divided into three key stages – frontend, backend, and content migration that can advance in parallel. Here’s how it all works
Frontend migration
Migrating the frontend to WordPress is optional. If you plan to move your entire frontend to WordPress instead of keeping a separate front-end system, this stage is relevant. WordPress offers over 13,000 free themes and a wealth of customization options, making it a strong candidate for hosting your site’s design and user experience.
Setting up WordPress for frontend delivery
The process begins by configuring WordPress and integrating it with modern headless frameworks. This involves connecting WordPress’s APIs to your chosen frontend technology, whether using WordPress’s built-in theme system or a JavaScript framework that leverages WordPress as a backend. During this setup, we’ll need to adjust your frontend configurations by rewriting data-fetching logic that previously used Sanity’s GROQ queries to now use WordPress REST or GraphQL APIs. This ensures your site correctly retrieves content from WordPress once the migration is complete.
Recreating your design and interactivity
Our team will audit the existing Sanity-driven UI, map its structure and design elements to WordPress, and rebuild these elements using WordPress blocks, components, or themes. The goal is to recreate a responsive, user-friendly frontend that mirrors your original design and workflow.
Choosing theme
With over 13,000 free themes available, WordPress offers a vast array of design options. You can select an existing theme that closely matches your needs or create a custom theme for a more tailored approach. This flexibility ensures that migrating your frontend to WordPress can be adapted to your specific design goals and technical requirements.
Note: If you decide not to migrate your frontend to WordPress and prefer to continue using a separate front-end system, we can skip this stage. The core focus will then remain on backend and content migration, leveraging WordPress solely as a headless content management system.
Backend migration
The backend migration phase is about transforming WordPress into a robust content engine capable of serving content to any frontend. We begin by configuring WordPress in headless mode, focusing on optimizing API performance and security to handle your content efficiently.
Next, we map Sanity’s custom features such as unique content types, workflows, and integrations into the WordPress environment. This process often involves leveraging WordPress plugins, creating custom post types, and utilizing the WP REST API or GraphQL to replicate the functions and data structures previously managed by Sanity.
The primary goal is to rebuild all essential backend capabilities from Sanity within WordPress. By doing so, we create a system that not only stores and delivers content effectively but also integrates smoothly with your existing tools, systems, and workflows.
Content Migration
Content migration involves transferring your data from Sanity into WordPress while preserving its structure, relationships, and SEO value. This phase ensures that your content remains intact and continues to perform well after the switch.
Exporting content
We begin by exporting your content from Sanity using its available tools such as the Sanity CLI, APIs, and GROQ queries. This process gathers structured content in a format like JSON, along with media assets, metadata, and other relevant data. The structured export makes it easier to work with your content during the migration.
Mapping and transforming
Once exported, the next step is to map your Sanity content to the corresponding WordPress structures. This means translating Sanity documents into WordPress posts, pages, or custom post types, and converting rich text (Portable Text) into Gutenberg blocks or appropriate HTML fields. We also transfer metadata, categories, tags, and any custom fields, ensuring that relationships between pieces of content are maintained.
Handling media and SEO
Special care is taken to transfer media assets such as images and videos. These files are downloaded from Sanity and uploaded into the WordPress Media Library, and their URLs and metadata are updated accordingly. We also focus on SEO considerations like:
- Preserving URL structures
- Transferring meta descriptions, titles, and alt text
- Setting up proper redirects if URLs change
These steps ensure that your search rankings and user experience are maintained after the migration.
In summary, by systematically exporting, mapping, and transforming your content, and carefully handling media and SEO aspects, the content migration process remains organized and methodical.
Timeline
Every Sanity instance is unique, so there’s no one-size-fits-all timeline for migrating from Sanity to WordPress. Generally, most migrations take around three months, although the exact duration can vary based on the complexity of your setup and the specific Sanity features in use. Below is a typical migration timeline, broken down into key phases.
Discovery & analysis (W1–W2)
The first step is auditing your current Sanity environment and identifying everything that needs to be migrated. This phase also involves outlining the best approaches to recreate various aspects of the Sanity instance on WordPress and organizing project logistics such as setting up teams and managing access. Typically, this process takes about two weeks. By the end of this phase, rtCamp delivers a comprehensive blueprint for executing the migration.
You could book a paid consultation with us to receive a detailed handbook for in-house execution, to have us handle the migration, or to engage your preferred third-party vendor.
Application design (W2–W4)
During weeks 2 to 4, the focus shifts to designing the new WordPress application. This involves mapping Sanity features to WordPress components and planning the necessary coding, customizations, and integrations. This stage generally spans two weeks.
Development & unit testing (W3–W8)
Once the discovery report is finalized, coding begins around week 3. At rtCamp, we follow agile sprints for development. Depending on the project’s scope, several sprints may be required. The early development phases focus on building themes and developing new plugins for custom functionality, followed by integrating third-party backend systems. Unit testing is conducted throughout this phase to ensure stability and functionality.
Migration script development (W2–W8)
In parallel with development, migration scripts are crafted to transfer content from Sanity to WordPress. This effort, running from week 2 to week 8, involves automating the extraction, transformation, and loading (ETL) of data to ensure a smooth content transfer.
SIT execution & support (W5–W11)
As development progresses, System Integration Testing (SIT) begins around week 5 and continues through week 11. SIT runs alongside development sprints, ensuring that all components be it content, design, and functionality, integrate seamlessly into the WordPress environment.
Content migration (W7–W12)
Once the frontend and backend are nearly ready, content migration takes place between weeks 7 and 12. Content is transferred manually or via automated scripts, with a focus on accuracy, structure, and completeness. This step is critical for maintaining content integrity across the new site.
User acceptance testing (W10–W13)
During weeks 10 to 13, the migrated WordPress site undergoes User Acceptance Testing (UAT) to verify usability, functionality, and any gaps compared to the original Sanity setup. At this stage, with client sign-off, the focus shifts toward live deployment.
Deployment to the live environment (W13–W15)
From weeks 13 to 15, the focus moves to deploying the site to the live environment. This phase involves final preparations, migrating remaining data, configuring production settings, and launching the new WordPress site.
Post-production support (W15–W16)
In the weeks following deployment, post-production support addresses any performance, usability, or technical issues that arise. At rtCamp, we offer continued support for a few weeks after migration to ensure stability and resolve unexpected challenges.
Team
Here’s a generic structure for a Sanity to WordPress CMS migration project team. A well-organized team ensures that every aspect of the migration, from strategy and execution to testing, quality assurance, and ongoing support, is covered comprehensively.
1) Project manager (PM)
The project manager oversees the entire migration process. They coordinate communication, track progress, and manage resources to ensure the project stays on schedule and meets its objectives. The project manager also ensures that deliverables align with business goals and that all stakeholders are informed and engaged throughout the migration.
2) Engineering Manager (EM)
The engineering manager is responsible for the technical leadership of the migration. They guide the development team, solve complex technical issues, and ensure that best practices are followed across the project. From platform configuration to integrations and system architecture, they ensure the migration stays technically sound and future-ready.
3) UI/UX Designers
UI/UX designers lead the visual and interaction design of the new WordPress experience. They ensure brand consistency by translating existing styles into WordPress-compatible formats, designing reusable components like buttons, sections, and page layouts. Accessibility and performance are baked into their process, making sure the final experience is both inclusive and optimized.
4) Backend engineers
Lead backend development tasks such as platform configuration, plugin creation, custom coding, and building integrations. They also develop and refine migration scripts to transfer content from Sanity to WordPress while maintaining data integrity and functionality.
5) Frontend engineers
Focus on the user interface and experience. They handle theme development, responsive design, and ensure that the visual elements from the Sanity site are accurately replicated or improved in WordPress. Their work is especially important if the frontend is being migrated to WordPress.
6) QA engineers
Conduct thorough testing to identify and resolve issues related to functionality, performance, and user experience in the new WordPress CMS. They validate the accuracy of data migration, check that integrations work as intended, and ensure compliance with industry standards. QA engineers verify that deliverables meet the project requirements and maintain high quality.
Wrapping it up…
In summary, this structured team approach ensures that every critical aspect of the Sanity to WordPress migration is managed effectively. From high-level strategy and planning by the project manager to detailed execution by the core team and specialized support where needed, this organizational structure is designed to deliver a successful migration tailored to enterprise needs.
Business case for migration
PREVIOUS
Credits
Shreya Agarwal
Author
Shreya Agarwal
Author
Shreya Agarwal is a Growth Engineer at rtCamp, she brings active, hands-on WordPress development credentials to everything she writes and reviews. A WordPress Core Contributor with merged pull requ…
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 Campfire for fresh insights and stories from people behind rtCamp
Δ
Email(Required)
Submit
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
_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
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
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