/handbook/hubspot-to-wordpress-migration/migrating-the-content/
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.google.com%2F
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 HubSpot to WordPress migration guide Content migration
Topics
On this page
- HubSpot to WordPress migration guide
- Planning the migration
- Pre-migration & discovery
- Frontend migration
- Content migration
- Backend migration
- Quality assurance
- Launch & post-migration
- How can rtCamp help
Start by auditing your existing HubSpot content
Map what you’re keeping (and where it lives next)
Exporting your HubSpot content
HubSpot’s built-in export tools
Custom scripts
Manual extraction
Preparing for WordPress import
SEO URL mapping
HubSpot to WordPress content migration is work… but it's quite an upgrade
Last updated on Apr 1, 2026
Migrating the Content from HubSpot CMS to WordPress
It’s easy to think that migrating a HubSpot blog to WordPress (content migration, basically!) is actually the easier part of a HubSpot to WordPress conversion, given HubSpot’s native content/data export tools. But it isn’t so.
HubSpot’s content ecosystem doesn’t map one-to-one with WordPress by default, and this becomes clear the moment you start planning your content migration. Your HubSpot instance likely uses dozens of “HubSpot” content elements (from smart modules and CTAs to special content formats) that simply don’t have direct equivalents in WordPress out of the box.
To handle this, your developers need to design the right foundation before any actual import happens. That means creating custom post types, defining custom fields, and building reusable blocks, patterns, and layouts so that when you do hit “Import,” every piece of content lands where it belongs, fully intact and functional.
The lift is real, but once your new WordPress content infrastructure is ready, the payoff is a site that’s easier to manage, more flexible to evolve, and free of HubSpot’s bundled constraints. Here’s how to go about your HubSpot to WordPress content migration.
Start by auditing your existing HubSpot content
For large enterprises, HubSpot content is often a patchwork of:
- Blog archives going back years
- Landing pages for old campaigns
- Downloadable assets
- Knowledge base sections
- Gated forms
- Smart CTAs
- SEO modules and redirects
So start by pulling everything into one source of truth (usually a spreadsheet or a simple database view) to see what’s there, who owns it, and whether it should move.
Your content audit table could look something like this:
**Content TypeVolumeOwner/StakeholderCurrent StatusKeep, Rewrite, Retire?**Blog Posts~1,500Content/SEO20% outdated1,200 keep, 300 rewriteLanding Pages300MarketingMixed150 keep, 50 rewrite, 100 retireKnowledge Base200SupportMostly validKeep allGated PDFs75Product/Lead GenSome obsolete50 keep, 25 retireCTAs & FormsDozensDemand GenMany tied to HubSpot formsRebuild all in WP
And here are some tools to help you:
- Screaming Frog: Crawl your entire HubSpot domain to inventory your content.
- Google Analytics & Search Console: Identify top pages driving traffic.
- Sitebulb: Advanced content audits.
Map what you’re keeping (and where it lives next)
Once you know what you have, the next question is: Where will it live in WordPress?
This is where the real design happens. HubSpot’s ecosystem is tightly bundled. WordPress is modular. In HubSpot, you might have blog posts, landing pages, knowledge base articles, and gated offers all created with the same drag-and-drop builder. In WordPress, you have posts, pages, reusable blocks, custom post types, taxonomies, and a universe of plugins.
So, a typical mapping conversation sounds like this:
- Those HubSpot blogs? They map cleanly to Posts.
- Standalone landing pages? Often Pages, but sometimes a dedicated Landing Page custom post type if you want reusable templates and easy tracking.
- CTAs? We usually recreate them as reusable Gutenberg blocks, shortcodes, or dynamic components managed through plugins like ACF.
- Knowledge bases? A custom post type with categories, related articles, and internal search.
- Forms? WordPress form plugins handle these: Gravity Forms or similar plugins are staples for most enterprise WordPress stacks.
At this stage, we also plan out your new URL structure. Should you replicate your HubSpot permalinks exactly to protect SEO? Do you want to flatten an old, deep folder structure? Which pages need 301s? These are the decisions that keep your traffic from tanking on day one.
Here’s an example mapping table you could use as a starting point:
HubSpot ElementMapped WordPress StructureTool/Plugin****NotesBlog PostsPostsCore WPUsually 1:1 mappingLanding PagesPages or CPTGutenberg, ACFOften with custom templatesCTAsReusable Blocks/PatternsACF, Block PluginsFlexible placementKnowledge BaseCustom Post TypeCould use a knowledge base theme or pluginFaceted search, breadcrumbsFormsEmbedded FormsGravity Forms, Formidable FormsCRM/API connectorsSEO MetadataSEO PluginsYoast, Rank MathValidate during import
Exporting your HubSpot content
For a large HubSpot site, you’ll need to use a combination of three export approaches, each tackling a different layer of your content and media ecosystem.
HubSpot’s built-in export tools
First, you’ll tap HubSpot’s built-in export tools to export the bulk of oyur simple data. For the parts of your site that follow simple, predictable patterns (like blog posts and standard site pages) these tools do a lot of the heavy lifting. Images stored in HubSpot’s File Manager can technically be bulk downloaded, for example. While HubSpot doesn’t give you a single “export all” button for everything in File Manager, you can export folders or run batch downloads. This covers the bulk of static assets: your logos, inline blog images, PDF downloads, or banners.
However, this out-of-the-box export only goes so far.
Custom scripts
If you’re looking for more advanced exports (for example, a complete dynamic, personalized landing page with different CTAs, modules, or content variations that change based on a visitor’s properties), you’re no longer looking at a simple, one-click export.
In these cases, the built-in tools just give you the static version or what an anonymous visitor would see by default. All the smart rules, embedded forms, gated files, and hidden modules that actually make the page work don’t come along for the ride automatically.
That’s exactly where custom scripts come in. Here, your dev team writes an API script that, let’s say, pulls the module definitions for the page, extracts the smart rules (e.g., geo rules, contact lists), downloads all variations of the CTA blocks, dumps the form definitions (fields, conditions, GDPR flags), and exports any gated files (like offer PDFs).
But getting the raw data/content is only half the job, you also need to plan how to rebuild that personalization on WordPress. That could mean using plugins, custom blocks, or third-party personalization tools to replicate HubSpot’s dynamic logic.
Manual extraction
Finally, there’s the unavoidable manual extraction. Even the best scripts miss edge cases. For these you need to go the manual route.
Preparing for WordPress import
Getting your content out from HubSpot is only half the job, the other half is building the right structure in WordPress to receive it.
This means your developers need to design Custom Post Types (CPTs). For example, a “case study” in HubSpot will become a CPT in WordPress. Likewise structured data will need configuring custom fields on WordPress.
Your developers will also need to use the Block Editor (Gutenberg) for building reusable blocks, block patterns, or custom blocks to mirror HubSpot’s modules or rich layouts. This work happens before you import (otherwise your content won’t display correctly).
Once you’ve all the content formats, fields, and blocks inside your WordPress dashboard, you’ll use a combination of methods to import your to WordPress. From WordPress import plugins and custom scripts to manually moving some assets, content import can look different for different assets.
The chapter on frontend migration covers these in detail, head over to it to get a clearer idea of how you can rebuild these.
When it’s time to actually bring your content in, you’ll lean on the same layered approach you used for export:
- WordPress import plugins for straightforward bulk imports (like blog posts and pages).
- Custom scripts for complex or dynamic content that needs precise mapping.
- Manual import for edge cases: one-off pages, for example.
SEO URL mapping
When you migrate a site (like HubSpot to WordPress), the content migration stage usually covers not just the text, images, and files, but also all the metadata and structural SEO elements that protect your search rankings.
SEO mapping specifically means:
- Crawling your existing site to inventory all URLs.
- Deciding where each old URL will point in the new WordPress structure (1:1 match or smart redirects).
- Creating 301 redirect maps to preserve SEO equity and link juice.
- Moving meta titles, descriptions, canonical tags, structured data (schema), alt text, and other on-page SEO assets.
- Ensuring internal links are updated so they don’t break or point back to old URLs.
In a good CMS migration plan, these steps sit inside the content migration track, because they’re directly tied to how pages and posts are rebuilt and published on the new CMS.
Here’s a table to help you conduct your SEO URL mapping: In it:
Old HubSpot URL: The exact path of the asset in your HubSpot site.
New WordPress URL: Where that page’s content will live on the new WordPress site.
Redirect Type: Almost always a 301 (permanent) redirect unless you’re retiring the page, then you’d plan a custom handling or let the 404 template catch it.
Notes: Any context, e.g., “merged into another page”, “slug cleaned”, “new taxonomy used”.
Old HubSpot URLNew WordPress URLRedirect Type****Notes/blog/marketing-strategy``/blog/marketing-strategyNoneBlog article: URL structure retained/blog/``/blog/NoneMain blog landing page: structure retained/resources/ebooks/guide-to-email``/downloads/guide-to-email-marketing301Moved to new “Downloads” section for gated content/resources/whitepapers/abc-whitepaper``/downloads/abc-whitepaper301Consolidated with other whitepapers under “Downloads”/about-us/our-team``/about/team301Cleaned up slug/webinar/2023-customer-experience``/events/2023-customer-experience-webinar301New events taxonomy/blog/old-post-retired``-410Low-value blog post not migrated: returning “gone”/404``/404NoneHandled by new WP 404 template
A few considerations:
- Bulk retention: Many blog articles often keep exactly the same slugs (
/blog/slug) if the URL structure works well. So for bulk blogs, you might map hundreds of rows with “No change” status. - Folder merges: Older nested folders like
/resources/whitepapers/or/resources/ebooks/might consolidate under/downloads/or/resources/so the redirect covers multiple old paths. - Retired content: Low-traffic, outdated, or duplicate pages can be intentionally retired with a 410 (“Gone”) response — telling Google not to keep crawling them.
- Slug cleanups: HubSpot sometimes adds extra slugs like
/about-us/that you might shorten to/about/. So even “minor” changes need explicit mapping to protect SEO.
Most enterprise teams generate a .htaccess or server config for Apache/Nginx using this URL mapping spreadsheet. When you do bulk redirection for a HubSpot to WordPress migration (or any CMS migration), you usually handle it server-side by generating a redirect configuration file.
HubSpot to WordPress content migration is work… but it’s quite an upgrade
A well-executed HubSpot-to-WordPress content migration isn’t just about moving text and images… it’s about translating years of marketing investment into a new, more flexible content management system. When your custom post types, fields, and blocks are thoughtfully planned, your content won’t just fit perfectly on WordPress but it will be easier to maintain, adapt, and scale for years to come.
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 …
Shreya Agarwal
Editor
Shreya Agarwal
Editor
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 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