Most website migrations to HubSpot go wrong in the same two places. Teams expect HubSpot to copy their whole site, then discover that pages have to be rebuilt. Or they switch the domain before every old URL has a new home, and search traffic drops for months. Both are avoidable with a plan made before anyone touches DNS.
This guide covers moving a site from WordPress or any other CMS into HubSpot's Content Hub. Every step and limit comes from HubSpot's knowledge base, read on 19 November 2026, with the date each article was last updated.
What does HubSpot import when you migrate a website?
Your blog posts, and an inventory of your pages. HubSpot's blog import tools bring in post content, and its website structure import brings in each page's title, URL and meta description along with your navigation menus. Page content itself is not imported, so pages are rebuilt in HubSpot templates.
That split comes from HubSpot's article Import web content into HubSpot, last updated 22 September 2026. The page import is still useful: it gives you a list of every external page to plan around. Knowledge base articles from Freshdesk, Help Scout, Intercom or Zendesk can also be imported, which needs Service Hub Professional or Enterprise.
Which blog import method should you use?
If the blog is on WordPress, start with WordPress connect, which reads your posts through the WordPress REST API from the blog's homepage URL. If it fails, use smart copy, then a CSV or XML file. For any other CMS, start with smart copy, which scans a live post to learn the template, and fall back to a CSV file.
The order is HubSpot's own recommendation in the import article, and every method needs Edit and Publish permission for the blog. Some WordPress blogs are not compatible with WordPress connect. Smart copy supports every blog type but may need mapping work if your template is unusual.
The XML route is the last resort, but it is the most predictable about what moves. HubSpot's XML import article, last updated 22 September 2026, lists what comes across: title, body with inline images, URL, publish date, author, tags and categories, status, meta description and featured image. PDF files linked in posts and images in gallery tags are left behind. Before any import, make internal links and image paths absolute URLs, or they break in the imported posts.
How do you move website pages to HubSpot?
Run the website structure import to get the page list, then rebuild each page in a HubSpot theme. In settings, under Content, then Blog, choose Import blog, start a new import of website pages and enter your homepage URL. The scan can take up to six hours, and each import holds up to 400 pages.
Those details are in HubSpot's website structure import article, last updated 27 August 2025, so check the current menu names before you start. The import gives each page a placeholder with the right URL, title and meta description. Rebuilding is the real work: choosing a theme, turning page layouts into reusable modules and moving content across. Most sites shrink in the process, because pages nobody visits are merged or dropped.
How do you switch your domain to HubSpot without losing traffic?
Publish the HubSpot versions of your pages, back up the old site, then update DNS. A domain or subdomain can host content in only one place, so the moment it points to HubSpot, any page still on the old platform at that address stops loading. If WordPress and HubSpot must run together, give each its own subdomain.
That rule is in HubSpot's article Connect a domain to HubSpot, last updated 26 June 2026, which also suggests using domain verification to pre-provision the SSL certificate so the site loads securely from the first minute. A common pattern is to move the blog first on a subdomain such as blog.yourcompany.com, then move the main site once the pages are rebuilt.
How do you set up redirects for a HubSpot migration?
Make a spreadsheet of every old URL and the new URL it should go to, then load it into HubSpot's URL redirects tool. HubSpot can bulk upload up to 500 redirects at a time from a CSV file, and each URL can be up to 140 characters. Redirect old pages to their closest new page, not all to the homepage.
The limits are in HubSpot's bulk upload URL redirects article, last updated 23 September 2025, found in settings under Content, then Domains and URLs, then URL Redirects. The tool needs Content Hub Starter or above, or Marketing Hub Professional or Enterprise.
A sound redirect plan has four columns: old URL, new URL, monthly search clicks from Search Console, and owner. Sort by clicks so the pages that bring traffic get checked first. After launch, crawl the old URL list and confirm every one returns a single permanent redirect to a live page.
| Step | Owner | When |
|---|---|---|
| Export Search Console pages and inventory every URL | SEO or marketing | Before design |
| Import blog and page structure into HubSpot | HubSpot admin | Early in the project |
| Rebuild pages in the HubSpot theme | Developer and content | Middle of the project |
| Map old URLs to new and load redirects | SEO | Before DNS change |
| Publish, back up the old site, switch DNS | HubSpot admin and IT | Launch day |
| Check redirects, forms and tracking | Whole team | First week after launch |
Should you move from WordPress to HubSpot at all?
Move when marketing wants pages, forms, emails and contact data in one system, and editors should publish without a developer. Stay on WordPress when the site depends on deep plugin ecosystems such as WooCommerce, or years of custom themes and blocks. The HubSpot vs WordPress comparison goes through the trade-offs.
If the CMS question is still open, the CMS Hub guide explains what Content Hub includes at each tier. Neither platform is wrong; the cost of a migration only pays back when the team will use what HubSpot adds.
INSIDEA
Ready to get more out of HubSpot?
We are an Elite HubSpot Partner rated 4.99 across 500+ verified reviews. Let's make your portal work harder.
How INSIDEA runs website migrations to HubSpot
INSIDEA is an Elite HubSpot Partner, rated 4.99 across 500+ verified reviews. Our Content Hub service plans the architecture and redirect map before anything is built, builds in sandbox sprints, then moves posts, images and redirects and rebuilds internal links, with a CMS typically running in 6 to 10 weeks. We also build on WordPress and Webflow, so if moving is not right for you, we will say so.




