/resources/umbraco-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 Umbraco to WordPress migration guide: Costs, risks, and when it’s worth doing Migration process, timeline & team
Topics
On this page
- Umbraco to WordPress migration guide: Costs, risks, and when it's worth doing
- Migration process, timeline & team
- Pre-migration setup
The Umbraco to WordPress migration process
Frontend migration
Backend migration
Content migration
Media migration
Timeline
Discovery & analysis (Weeks 1–2)
Application design (Weeks 2–4)
Development & unit testing (Weeks 3–8)
Migration script development (Weeks 2–8)
System Integration Testing (SIT) (Weeks 5–11)
Content migration (Weeks 7–12)
User Acceptance Testing (UAT) (Weeks 10–13)
Deployment to the live environment (Weeks 13–15)
Post-production support (Weeks 15–16)
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 Sep 1, 2026
Umbraco to WordPress migration: Process, timeline, and team
We break the migration journey into three clear phases: Pre-Migration, Migration, and Post-Migration.
Each phase has a specific focus, starting with strategic discovery and ending with a high-performing WordPress site ready for scale.
The Umbraco to WordPress migration process
A successful migration isn’t just about moving platforms, it’s about making sure your website performs better, scales faster, and becomes easier for teams to manage. Here’s how we approach Umbraco to WordPress migrations at rtCamp, broken down into clear phases: frontend, backend, and content.
Frontend migration
Frontend migration focuses on everything your users see and interact with, including design, layout, and user experience.
In Umbraco, frontend templates are often built using Razor views and tightly coupled with .NET backend logic. Moving to WordPress means translating those designs into a decoupled, modern architecture, either using custom themes or WordPress’s block-based Full Site Editing (FSE) approach.
At rtCamp, we begin by auditing your existing Umbraco frontend:
- Layouts, templates, and navigation structures
- Global components like headers, footers, menus, and widgets
- Interactive elements (modals, sliders, accordions, etc.)
- Responsiveness, accessibility, and performance markers
Once mapped, we recreate your frontend using a custom WordPress theme or extend Gutenberg with pre-built blocks. If your team is planning a redesign, this is where we align on visual direction and brand identity.
To support ongoing agility, we go beyond just replicating layouts, we equip your WordPress build with:
- A branded design system
- A reusable block library
- Pre-configured page templates
That way, your marketing and content teams don’t just get a new site, they get a flexible toolkit they can run with.
Backend migration
Backend migration is about replicating the functional core of your Umbraco site, your content structure, custom features, and integrations, on WordPress.
Infrastructure setup
Umbraco sites are typically hosted on Windows servers or Azure with IIS. WordPress, in contrast, runs efficiently on a wide variety of platforms, ranging from managed WordPress enterprise hosts (like WordPress VIP, Pagely, or Pantheon) to self-hosted configurations.
We help you evaluate hosting options based on your scale, compliance needs, and DevOps preferences, then set up the right infrastructure with Git-based deployment workflows.
Custom features and functionality
Custom functionality built on Umbraco often lives inside .NET components or user controls. We re-engineer these as:
- Native WordPress features
- Custom plugins
- Or integrations with existing SaaS platforms
Examples might include
- Rebuilding Umbraco Forms via Gravity Forms or WPForms
- Replicating content approval workflows using plugins like Edit Flow
- Replacing custom dashboards or tools with block-based layouts and admin customizations
Where needed, we also build custom logic using WordPress hooks, REST API, or serverless endpoints.
Integration migration
Many enterprise Umbraco sites rely on external systems like CRMs, ERPs, analytics platforms, personalization engines, or DAMs.
We:
- Audit all existing integrations
- Map each to a WordPress-compatible alternative
- Recreate the integration via plugins, custom APIs, or WordPress-native tooling
Whether you’re using Azure AD, HubSpot, Salesforce, or bespoke tools, we ensure your connected systems stay intact through the migration.
Content migration
Migrating content from Umbraco is often one of the more complex steps, mainly due to how deeply structured the content can be.
We break it into four core steps:
Content inventorying and mapping
We perform a full audit of your current Umbraco content, including:
- Document types (content models)
- Pages, blocks, reusable content nodes
- Metadata, SEO fields, and redirects
- Media library assets (images, videos, PDFs)
Then, we map these to WordPress equivalents:
- Umbraco Document Types → WordPress Custom Post Types
- Umbraco Properties → WordPress Custom Fields (ACF or native)
- Umbraco Tags & Categories → WordPress Taxonomies
Automated and manual migration
We use a mix of scripts and custom tools to extract structured content from Umbraco and import it into WordPress while preserving relationships and hierarchies. This includes:
- Maintaining parent-child page structures
- Recreating internal linking between content pieces
- Mapping content blocks and modular components
For elements that can’t be cleanly scripted, we supplement with manual QA and editorial cleanup to ensure consistency and usability.
If you’d like to explore which approach best fits your setup, check out our blog: Manual vs Automated vs Hybrid: How to migrate to WordPress the right and safe way.
Media migration
Umbraco often stores media in its Media section, sometimes using CDN-based file storage or Azure Blob Storage.
We:
- Extract and migrate all media assets
- Optimize them for WordPress’s Media Library
- Preserve image metadata, alt text, and associations
- Re-embed media into relevant WordPress content blocks
SEO preservation and redirects
A platform switch can impact your SEO unless you take care of the details. We handle:
- Transferring meta titles, descriptions, and canonical URLs
- Migrating Open Graph and Twitter card data
- Moving over schema markup (if structured via Umbraco plugins)
- Setting up permanent 301 redirects from old Umbraco URLs to new WordPress equivalents
- Validating URLs to avoid crawl issues post-migration
This ensures you don’t lose organic visibility during the transition and may even improve it.
Up next, we’ll walk you through our typical migration timeline and team structure so you know what to expect in terms of delivery and roles.
Timeline
Every Umbraco implementation is different, shaped by your business logic, .NET customizations, and editorial workflows. Because of this, there’s no one-size-fits-all timeline for Umbraco to WordPress migrations. That said, most enterprise migrations typically span around three to four months, depending on complexity.
Here’s what a standard Umbraco to WordPress migration timeline looks like.
Discovery & analysis (Weeks 1–2)
The first step is a thorough audit of your existing Umbraco environment, covering frontend templates, backend logic, integrations, content types, and media structure.
At this stage, we:
- Map out technical and editorial dependencies
- Define migration scope and sequencing
- Evaluate hosting/infrastructure needs
- Align with your business and operational goals
By the end of this phase, we deliver a complete discovery report, a migration blueprint that can be executed by your in-house team, rtCamp, or your chosen partner.
Application design (Weeks 2–4)
With the discovery findings in hand, we begin mapping your Umbraco features to WordPress equivalents planning for:
- Theme architecture
- Plugin requirements (off-the-shelf or custom)
- Custom content models
- Workflow and integration mapping
This phase lays the foundation for frontend, backend, and editorial success.
Development & unit testing (Weeks 3–8)
Development kicks off once the discovery phase concludes.
In parallel agile sprints, our teams:
- Recreate the frontend using custom themes or block-based design
- Build and test custom plugins
- Configure role-based permissions and user workflows
- Integrate third-party tools and APIs
Each sprint includes unit testing to validate functional integrity.
Migration script development (Weeks 2–8)
Alongside application development, we begin building migration scripts to move structured content and assets from Umbraco to WordPress.
This includes:
- Mapping document types to post types
- Preserving parent-child hierarchies
- Transforming and migrating media and metadata
Scripts are tested in staging environments to ensure clean imports with no data loss.
System Integration Testing (SIT) (Weeks 5–11)
As the WordPress stack takes shape, we run System Integration Testing (SIT) to validate that frontend components, backend logic, and third-party integrations work together smoothly.
This helps us identify integration gaps and performance issues early, before content goes in.
Content migration (Weeks 7–12)
Once the environment is stable, we migrate content in bulk, with editorial support for reviewing:
- Page layouts
- Media embeds
- Internal linking and taxonomies
- SEO metadata and redirects
Our goal here is fidelity, not just moving data, but preserving structure and usability across your site.
User Acceptance Testing (UAT) (Weeks 10–13)
With the site nearly ready, we invite your internal stakeholders to test workflows, user journeys, and backend usability.
This ensures:
- Editorial comfort with the new block editor
- Marketing and analytics integrations function as expected
- Stakeholders sign off on frontend quality and brand consistency
Once UAT is complete, we prep for launch.
Deployment to the live environment (Weeks 13–15)
We move the new WordPress site from staging to production, coordinating DNS updates, launch windows, and fallback plans to minimize business impact.
If needed, we also sync delta content changes that happened between final UAT and go-live.
Post-production support (Weeks 15–16)
The first few weeks after launch are critical. We stay engaged to monitor performance, address live-site issues, and ensure smooth handover.
This includes:
- Regression testing
- Bug resolution
- Editorial support and documentation
- Optional performance or SEO audits
Team
Umbraco to WordPress migrations, especially at the enterprise level, require more than just technical execution. From strategy to rollout, each stage involves distinct expertise. Here’s a standard team structure we recommend to ensure every facet of your migration is handled efficiently and thoughtfully.
1) Project Manager (PM)
The Project Manager owns the end-to-end delivery of the migration. They ensure that planning, coordination, timelines, and stakeholder communication stay on track throughout the engagement. From discovery to deployment, the PM ensures alignment between business goals and technical execution, keeps all contributors informed, and removes blockers before they affect delivery.
2) Engineering Manager (EM)
The Engineering Manager leads the technical arm of the project. For Umbraco migrations, this means guiding the translation of a .NET-based CMS into a PHP-based WordPress architecture, without losing functionality or performance. The EM reviews code, oversees environment setup, handles infrastructure decisions, and ensures that each integration, plugin, and deployment meets both engineering and enterprise standards.
3) UI/UX Designers
UI/UX Designers are responsible for visually translating the Umbraco experience, or creating an entirely new one, within WordPress. They:
- Ensure consistency with existing brand guidelines
- Design reusable components (e.g., hero blocks, CTAs, templates)
- Build with accessibility, inclusivity, and mobile-first principles
- Deliver annotated design systems ready for WordPress development
Their work ensures that design and user experience aren’t just preserved, but elevated post-migration.
4) Backend Engineers
Backend Engineers rebuild the functional backbone of your Umbraco instance on WordPress. This includes:
- Recreating content types using WordPress custom post types and taxonomies
- Migrating custom workflows, forms, and backend logic
- Rebuilding integrations with CRMs, DAMs, marketing tools, and APIs
- Writing and validating content migration scripts
They also manage critical aspects like role-based permissions, performance configurations, and backend security.
5) Frontend Engineers
Frontend Engineers replicate or modernize the user-facing experience from Umbraco to WordPress. They develop the new WordPress theme either from your existing design system or a fresh redesign, and ensure it:
- Reflects the original layouts and interactions accurately
- Adapts seamlessly across breakpoints
- Is optimized for accessibility, performance, and SEO
They also extend the block editor experience with custom blocks where needed, empowering your content teams to own day-to-day page building.
6) QA Engineers
QA Engineers ensure everything works as expected, before and after launch. Their role includes:
- Verifying that functionality has parity with your original Umbraco site
- Validating migrated content for accuracy, completeness, and formatting
- Testing integrations, workflows, and backend logic
- Performing regression, security, and accessibility testing across staging and production environments
They support confidence at every major milestone, ensuring the final WordPress site is stable, secure, and ready for scale.
Wrapping it up…
Migrating from Umbraco to WordPress is a cross-functional effort. With the right team structure, from high-level strategy through technical execution and quality assurance, you can ensure the migration delivers not just a new platform but a stronger, more future-ready foundation for your business.
Umbraco to WordPress migration guide: Costs, risks, and when it's worth doing
PREVIOUS
Credits
Aviral Mittal
Author
Aviral Mittal
Author
Aviral Mittal is the Chief Marketing Officer at rtCamp, where he established and leads the marketing function, building and growing a team of 20+ specialists across content, SEO, design, and growth…
Contributions and Updates: Usama 
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
_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