On 7 October 2026 HubSpot stopped offering its own website migration service. Its knowledge base, updated 6 November 2026, now carries a one-line notice that website migrations were sunset. For a team leaving WordPress, that removes the one route where the destination platform did the rebuild for you. Both moves are now the same kind of project: you, an agency or a freelancer rebuild the templates, and the platform's importer carries some of the content across.
This page compares the two moves from the WordPress side: what each importer actually moves, what has to be rebuilt, what each platform costs to run, and how fast the result is likely to be. Figures come from HubSpot's knowledge base and product catalog, Webflow's help centre and pricing page, the HTTP Archive and published agency rate cards, all opened on 13 November 2026. We build marketing sites in Webflow, so read the comparison with that bias in mind.
The decision in four questions
Most teams frame this as a platform choice. It is really a question about where your marketing data lives. Answer these four before you price anything:
- Is HubSpot already your CRM, on Marketing Hub Professional or above? If yes, HubSpot's CMS puts the website on the same contact records your sales team uses. If no, buying Content Hub to get a website is the expensive way to get a CRM.
- Will pages change by visitor data within a year? HubSpot's catalog lists advanced personalisation from Content Hub Professional, in limited form, with full functionality on Enterprise. If nobody has a plan for it, you will pay for a feature you do not use.
- Who builds new pages after launch? A designer comfortable with a visual canvas will be faster in Webflow. A marketer who already works in HubSpot's editors will be faster there.
- How much of your WordPress site is custom post types? Case studies, resources, team members and locations are usually custom post types. HubSpot's WordPress importer skips them; Webflow imports them only through CSV, one Collection at a time.
Two or three answers pointing the same way is usually the decision. Our earlier comparison, Webflow vs HubSpot CMS: When the CRM Should Own the Website and When It Should Not, covers the platform question in depth. This page is about the move.
What each importer moves, and what you rebuild
Neither platform converts a WordPress theme. HubSpot builds sites from themes, templates and modules written in its HubL templating language. Webflow builds them visually in the Designer. Either way, the header, footer, page templates and forms are new work. The difference is how much content arrives without hand work.
| Content | To Webflow | To HubSpot Content Hub |
|---|---|---|
| Blog posts | CSV import into a CMS Collection after converting the WordPress XML export; third-party apps also exist | WordPress connect via the REST API: title, SEO title, author, publish date, featured image, categories, tags, meta description, body |
| Custom post types | CSV import into their own Collections | Not supported by WordPress connect; XML or CSV blog import, or a developer task |
| Pages | Rebuilt by hand; nothing imports | Structure import: slug, title, meta description and navigation only, up to 400 pages per import |
| Images in posts | Image fields take direct URLs; imported images get no responsive variants | Featured image imported; author images only if inside the post body |
| Theme and templates | Rebuilt in the Designer | Rebuilt as a HubSpot theme in HubL, or a Marketplace theme |
| Redirects | 301 rules in site settings, bulk CSV import, capture groups for folders | URL redirects with CSV upload and flexible pattern redirects |
| Managed service by the platform | None | Sunset on 7 October 2026 |
Sources: HubSpot knowledge base, import, WordPress connect, structure import, redirects and migration articles; Webflow help centre, WordPress migration, CMS import and redirects articles
HubSpot's blog import is the stronger tool. WordPress connect reads your blog from its homepage URL and lets you review every post before import, as drafts or as live posts. It fails when security plugins block the WordPress API, or on an expired SSL certificate, and then HubSpot sends you to the XML or CSV route.
Webflow's import is more manual but more flexible. The CSV route works for every content type, including custom post types, as long as you build the Collection first. Reference fields match on slugs, so categories and authors need their own Collections before posts arrive. Webflow's CMS import article also warns that images imported by URL get no srcset, so large archives should be resized first.
Pages are a rebuild on both. HubSpot's structure import gives you an inventory of URLs, titles and meta descriptions, which is useful, but its own article says page content cannot be imported. A scan can take up to six hours.
What each costs to run after the move
HubSpot prices Content Hub by edition and Core Seat. Webflow prices a site plan, a Workspace and seats separately. Our illustration is a typical B2B marketing site: 40 pages, one blog, one admin and three marketing editors, one language.
| Line | Webflow | HubSpot Content Hub Professional |
|---|---|---|
| Platform | Premium site plan, $25 billed yearly | Content Hub Professional, from $500, three Core Seats included |
| Workspace | Core Workspace, $19 billed yearly, one full seat | Not applicable |
| Three more editors | Three Limited seats at $15: $45 | One extra Core Seat at $50 |
| Page and content limits | 20,000 CMS items, 40 Collections | 10,000 website pages, 100 blogs |
| Personalisation and A/B tests | Optimize add-on, priced separately | Included, personalisation limited on Professional |
| Monthly total | $89 | $550 |
| Yearly total | $1,068 | $6,600 |
Sources: Webflow pricing page; HubSpot Product and Services Catalog. Octo Agency illustration, before tax.
Content Hub Starter does not fit this site. HubSpot's catalog lists Starter at $20 a month per Core Seat with 30 website pages and one blog, so 40 pages need Professional.
The Webflow plan names changed this year. On 13 May 2026 Webflow merged its former CMS and Business site plans into Premium, at $25 a month billed yearly or $39 monthly, with 20,000 CMS items and 40 Collections. Sites inside Freelancer or Agency Workspaces move to the new pricing at their first renewal on or after 16 November 2026, so agency quotes written earlier in the year may show old plan names and prices.
WordPress was not free either. Hosting, premium plugins and a maintainer were real costs on the old site. If you already pay for HubSpot Marketing Hub Professional, the HubSpot column is the full incremental cost, and the gap shrinks to the Content Hub line alone.
What the move itself costs and how long it takes
There is no independent benchmark for either migration. The published numbers come from agencies and freelancers who sell the work, so treat them as price lists, not averages.
| Item | WordPress to Webflow | WordPress to HubSpot |
|---|---|---|
| Theme or design system setup | Quoted per project | $1,500 to $3,000 (Bootstrap Creative) |
| Standard pages | Quoted per project | $100 to $250 per page (Bootstrap Creative) |
| Blog posts | Quoted per project | $10 to $25 per post (Bootstrap Creative) |
| Custom integrations | Quoted per project | $500 or more per feature (Bootstrap Creative) |
| Timeline, under 50 pages | Four to six weeks (LowCode Agency) | Two to four weeks for most migrations, while HubSpot's own service ran |
| Timeline, 50 to 200 pages | Eight to fourteen weeks (LowCode Agency) | Set per migration agreement |
Sources: Bootstrap Creative, October 2026; LowCode Agency, October 2026; HubSpot knowledge base, November 2026
Applied to our 40-page site with 150 blog posts, Bootstrap Creative's rates give $7,000 to $16,750 for the HubSpot move: $1,500 to $3,000 for setup, $4,000 to $10,000 for pages and $1,500 to $3,750 for posts. That is one freelancer's card, not a market rate.
We have not found a comparable per-page rate card for Webflow migrations that we trust. We quote per project. For reference, our usual marketing-site process runs four weeks, and on our white-label work for Web Tonic each Webflow site took two to three weeks, the largest with a CMS of over 1,200 items. A migration with a large custom post type archive sits at the longer end.
HubSpot's sunset changes the comparison. While it ran, HubSpot's replatforming service was a cheaper route for teams happy to keep their design or use a Marketplace theme. It excluded database-driven content, gated pages, e-commerce, advanced forms and custom responsive design. With it gone, a WordPress to HubSpot move needs a HubSpot developer or Solutions Partner, just as a Webflow move needs a Webflow developer.
Speed after the move
The HTTP Archive's Technology Report pairs Chrome's real-user data with platform detection. An origin passes a metric when 75% of visits are good.
| Metric | Webflow | HubSpot CMS Hub | WordPress |
|---|---|---|---|
| All three Core Web Vitals | 72.1% | 60.7% | 49.0% |
| Largest Contentful Paint | 79.6% | 79.1% | 56.3% |
| Cumulative Layout Shift | 93.8% | 82.0% | 87.6% |
| Interaction to Next Paint | 87.7% | 85.3% | 90.0% |
| Time to First Byte | 74.8% | 68.7% | 23.6% |
| Mobile origins tested | 56,474 | 13,848 | 2,513,839 |
Source: HTTP Archive Core Web Vitals Technology Report, October 2026 dataset, all geographies and ranks
Both moves are likely to make a typical WordPress site faster. Server response is the biggest gap: fewer than a quarter of WordPress origins pass Time to First Byte on mobile, against roughly seven in ten on either hosted platform. Loading speed is level between Webflow and HubSpot. Where they differ is layout shift, 11.8 points in Webflow's favour, which our reading attributes to elements injected after load such as pop-ups, chat widgets and embedded forms. The data shows the gap but not its cause.
These are averages across thousands of different sites. A heavy hero video or a pile of tracking scripts will undo either platform's advantage.
Protecting rankings: the same work on both
Google's site move guidance applies whichever platform you pick: map every old URL to a new one, use permanent server-side redirects, update internal links and submit a new sitemap. It says a medium-sized site can take a few weeks or more before Google shows the new URLs, and to expect ranking fluctuation in the meantime.
On Webflow, 301 redirects live in site settings and can be bulk-imported as CSV. Webflow sets no hard limit but recommends 1,000 rules at most, because every rule adds to a file visitors download. Wildcard rules with capture groups keep the count down, so WordPress date-based permalinks are worth flattening with one pattern rather than hundreds of lines.
On HubSpot, URL redirects support CSV upload and flexible pattern redirects. HubSpot notes that redirects only work for domains hosted in HubSpot, and that propagation can take up to 48 hours, so load them before the DNS change, not after.
Our WordPress to Webflow Migration: The 30-Step Checklist and What You Lose Along the Way covers the Webflow side step by step.
When each one wins
WordPress to HubSpot wins when HubSpot is already your system of record, your team already works in HubSpot's editors, personalisation by lifecycle stage or list is on this year's plan, and most of your WordPress content is a blog that WordPress connect can import. The higher running cost buys one login, native forms and reporting in the same dashboards.
WordPress to Webflow wins when the site is design-led, your content model has several custom post types that need their own templates, Core Web Vitals matter to you, or your CRM might change. If you keep HubSpot as the CRM behind a Webflow site, budget for the form connection. Our HubSpot CMS to Webflow: Keep the CRM, Move the Site, Lose Nothing in Attribution covers that wiring.
Neither wins when the WordPress site depends on WooCommerce, memberships or a complex plugin. Price that function on the destination first, because it decides the project more than the CMS does.
What this means for a team leaving WordPress
Start with the four questions, then count two things: your custom post types and the pages that bring in leads. If HubSpot is already your CRM and your content is mostly a blog, the HubSpot move is the shorter path, and the higher monthly bill is the price of keeping everything in one system. If your content model is richer, or the CRM decision is still open, Webflow costs less to run and gives you more control over the templates. Either way, the October sunset means you should price the rebuild with an independent developer from day one. Our marketing websites service page explains how we scope a WordPress to Webflow move.


