Muhammad Ismail Khalid

HubSpot to WordPress Migration: A Step-by-Step Guide That Protects Your SEO

By , Full Stack Developer and AI Automation Engineer. . 6 min read.

Topic: Website Migration

On this page
  1. Before you start: decide what moves
  2. Step 1: Inventory every URL
  3. Step 2: Export your content from HubSpot
  4. Step 3: Build the new site on staging
  5. Step 4: Import blog posts and images
  6. Step 5: Reconnect forms and tracking
  7. Step 6: Map every redirect
  8. Step 7: Test, then switch DNS
  9. Step 8: Watch the first weeks closely
  10. Common mistakes to avoid
  11. The short answer
  12. Frequently asked questions

Moving a site from HubSpot to WordPress is mostly a rebuild, not a copy. HubSpot exports your content, but not in a form WordPress can import directly. The risk isn't losing the text. It's losing rankings, form submissions and tracking along the way.

This is the order I follow for WordPress migrations: inventory first, build on staging, map every redirect, then switch. I've run host and platform migrations for treatment centers, healthcare clinics and marketing agencies for years, and the steps below apply the same process to HubSpot.

HubSpot to WordPress migration in 8 steps, from URL inventory to watching Search Console
The 8 steps of a HubSpot to WordPress migration.

Before you start: decide what moves

Many businesses leave HubSpot's CMS but keep HubSpot as their CRM. Decide this first, because it changes the plan.

Keep in HubSpot Move to WordPress
Contacts, deals and pipelines Pages and landing pages
Email marketing and workflows Blog posts and authors
Forms (embedded on WordPress) Templates and design
Tracking and reporting Images and files

If you keep HubSpot for marketing, you still get its forms, tracking and email on the new WordPress site.

If you are also rethinking HubSpot as your CRM, our GoHighLevel pros and cons review covers one common alternative for service businesses.

HubSpot to WordPress migration: what stays in HubSpot and what moves to WordPress
What moves to WordPress and what stays in HubSpot.

Step 1: Inventory every URL

Make a spreadsheet of every page, landing page and blog post, with its URL. Add these columns:

  • Organic traffic and backlinks, from Google Search Console and your SEO tool
  • Title tag and meta description
  • Forms on the page and where each form's submissions go
  • Action: keep, merge or drop

This list becomes the contract for the whole project. Any URL missing from it is a page you might forget to redirect.

Also record your current results: organic clicks, indexed pages and form submissions per month. You'll compare against these after launch.

Step 2: Export your content from HubSpot

HubSpot's knowledge base describes two exports you'll use:

  1. All pages and blog posts as HTML. In your content tools, use the Actions dropdown and choose to export all pages and blog posts (HTML). Template files are in the Styles folder of the export. You need Super Admin or Publish permission.
  2. Blog post data as a spreadsheet. Export blog post data as CSV, XLS or XLSX. This gives you titles, URLs and other post fields in a form that's easier to import.

What you don't get is a WordPress-ready file. HubSpot themes, modules and HubL templates don't run on WordPress, so the design has to be rebuilt.

Separately, collect these by hand:

  • URL redirects already set up in HubSpot, so you can carry them over
  • Files and images from the file manager
  • Form embed codes if forms will stay in HubSpot
  • Any HubDB tables that feed pages, such as team or location listings

Step 3: Build the new site on staging

Never build on the live domain. Set up WordPress on a staging copy and build there.

Rebuild each HubSpot template as a WordPress template or block pattern: the homepage, service pages, landing pages, the blog index and the blog post. Keep the same content structure on pages that already rank, so the headings and copy Google knows stay in place. If you need custom post types, blocks or CRM integrations rather than a theme from a marketplace, our guide to custom WordPress web development explains what that work includes and what drives the cost.

Stop the staging site from being indexed. Turn on WordPress's search engine visibility setting or add password protection, and remember to undo it at launch.

Step 4: Import blog posts and images

You have three realistic options for moving blog posts:

  • CSV import. Use the exported blog post data with an import plugin such as WP All Import, mapping title, content, date, author and URL slug.
  • The RSS importer. WordPress can import from your HubSpot blog's RSS feed, but you only get what's in the feed. Check whether every post came across.
  • Manual copy. For a small blog, copying posts by hand is often the most reliable way, and it lets you fix formatting as you go.

Then move the images. Download them from HubSpot's file manager, upload them to the WordPress media library, and update the image links in each post. Don't leave posts pointing at HubSpot-hosted files you plan to stop paying for.

Carry over each post's title tag, meta description and publish date. An SEO plugin such as Yoast or Rank Math gives you fields for the first two.

Step 5: Reconnect forms and tracking

This is the step that quietly costs leads when it's skipped.

  • HubSpot forms: add them to WordPress with HubSpot's official WordPress plugin or the form embed code. Then submit a test on every form and confirm the contact appears in HubSpot with the right properties.
  • HubSpot tracking code: install it on every page, or the plugin does this for you. Without it, HubSpot can't attribute visits to contacts.
  • Google Analytics 4 and Google Tag Manager: reinstall them and check that conversion events still fire when a form is submitted. A new form often has a new ID, and a trigger tied to the old one stops firing without any error.
  • Call tracking numbers: check they appear on the new pages exactly as before.

Step 6: Map every redirect

Every old URL that changes needs a 301 redirect to its closest new page. HubSpot and WordPress often use different URL patterns for blog posts, so expect a lot of these.

Rules I follow:

  • Map one to one. Never redirect everything to the homepage.
  • Redirect to the final URL. Avoid chains where one redirect points to another.
  • Keep the slugs the same where you can, so fewer redirects are needed.
  • Test the whole list before launch, checking that each old URL returns a 301 and lands on the right page.

Google's site move guidance says to keep redirects in place for as long as possible, generally at least a year.

Step 7: Test, then switch DNS

Before launch, check on staging:

  • Every page in your inventory exists, or redirects
  • All forms submit and reach HubSpot
  • Titles, meta descriptions and headings match the old pages
  • Images load and no links point to the old domain or HubSpot file URLs
  • Page speed on mobile is at least as good as before

Then switch DNS to your WordPress host, disconnect the domain from HubSpot's website settings, turn off the staging no-index setting, and submit the new XML sitemap in Google Search Console.

Step 8: Watch the first weeks closely

Check Search Console and form submissions daily for the first two weeks, then weekly. Look for:

  • 404 errors from URLs you missed in the redirect map
  • Pages dropping out of the index
  • A fall in form submissions or conversions

A temporary ranking dip after a migration is normal, and Google says a site move can take a while to be fully processed. A drop in form submissions is not normal, and usually means a form or tracking tag broke.

Once the new site has settled, put it on a regular routine. Our WordPress website maintenance checklist covers the weekly, monthly, quarterly and yearly tasks.

Common mistakes to avoid

  • Redirecting everything to the homepage, which throws away the value of each page
  • Launching with the staging no-index setting still on
  • Forgetting landing pages used in ads or emails
  • Leaving images on HubSpot's servers after you cancel the CMS
  • Not testing forms end to end, including who actually receives the submission

The short answer

Export your pages and blog posts from HubSpot, rebuild the templates in WordPress on staging, import the content and images, reconnect forms and tracking, and add a 301 redirect for every changed URL. Test everything before switching DNS, and watch Search Console for the first few weeks.

Sources: HubSpot: export web content and data, Google: site moves with URL changes.

Frequently asked questions

Can you export a HubSpot website to WordPress?

Partly. HubSpot lets you export all pages and blog posts as HTML, and blog post data as a CSV, XLS or XLSX file. There is no one-click import into WordPress, so templates have to be rebuilt and content has to be imported or recreated.

Will I lose SEO when moving from HubSpot to WordPress?

A short dip is common after any site move. You protect rankings by keeping page content, titles and meta descriptions, and by adding a 301 redirect from every old URL that changes to its closest new page.

Can I keep using HubSpot CRM and forms on WordPress?

Yes. Many businesses move only the website and keep HubSpot as their CRM. HubSpot forms and the tracking code can be added to WordPress with HubSpot's official WordPress plugin or by embedding the form code.

How long does a HubSpot to WordPress migration take?

It depends on the number of pages, templates and posts. A small brochure site can move in days, while a site with hundreds of posts and custom modules takes longer because each template has to be rebuilt and tested.

What happens to images hosted on HubSpot?

Images in HubSpot's file manager are served from HubSpot. Download them, upload them to the WordPress media library and update the links, rather than relying on HubSpot-hosted file URLs after you leave.

Get in touch

Have a question about my work or something I wrote? Send me an email.