Migrating to HubSpot CMS: a step-by-step guide for B2B companies

Overview

Most HubSpot CMS migrations start the same way: a company adopts HubSpot CRM, realises the plugin connection between their existing website and HubSpot is an imperfect substitute for a native solution, and decides to move the website to HubSpot CMS. The question then becomes how to do it without losing search rankings, breaking existing integrations, or spending more time and money than necessary.

This guide covers everything a B2B company needs to know about migrating to HubSpot CMS: what to audit before starting, how to protect SEO during the move, what the process involves, and how to use the migration as an opportunity to improve the website rather than simply reproduce it on a new platform.

In this article:

1. Should you migrate or rebuild?
2. Pre-migration audit: what to do before you start
3. The migration process phase by phase
4. Protecting your SEO rankings during migration
5. CRM and workflow setup during migration
6. The redesign opportunity: making the most of your migration
7. Common migration mistakes
8. Frequently asked questions

This article is part of the complete guide to HubSpot CMS for B2B websites.

1. Should you migrate or rebuild?

The first decision in any HubSpot migration is whether you are lifting and shifting your existing site onto HubSpot CMS, or using the migration as an opportunity for a strategic redesign. These are meaningfully different projects with different costs, timelines, and outcomes.

Lift and shift: when it makes sense

A lift and shift migration moves your existing content, structure, and design into HubSpot's architecture with minimal changes. It makes sense when: your current site's information architecture is sound and your positioning is clear; your design is recent and still reflects where the business is; your primary goal is to connect the website to HubSpot CRM as quickly as possible; and your budget or timeline does not accommodate a full redesign.

A lift and shift is faster and cheaper than a redesign, but it carries all the structural problems of your existing site into the new platform. If those problems include unclear positioning, poor conversion architecture, or outdated content, they will remain after migration.

Migration with redesign: when it makes sense

A migration with redesign rebuilds the site from strategy through to design and development on HubSpot CMS. It makes sense when: your positioning or audience has changed since the current site was built; your site's conversion rate is structurally broken; the current site's design no longer reflects the business; or the information architecture needs a fundamental rethink.

The marginal cost of redesigning during a migration is smaller than the cost of a standalone redesign later. You are already paying to rebuild every template and migrate every page: doing that work strategically costs incrementally more but produces substantially better outcomes.

2. Pre-migration audit: what to do before you start

The most important work in a HubSpot migration happens before development begins. A thorough pre-migration audit determines what gets migrated, what gets improved, and what gets removed.

Content audit

Review every page on your current site and categorise each one:

• Migrate as-is: pages with strong content, good rankings, and clear purpose that need no structural changes
• Migrate and improve: pages with good rankings but thin content, outdated copy, or poor structure that should be refreshed during migration
• Consolidate: multiple pages covering the same topic that should be merged into a single, stronger page
• Remove: pages with no traffic, no rankings, no commercial purpose, and no content worth salvaging

Removing pages from a site during migration is one of the most impactful SEO improvements available. Thin, low-quality pages dilute your site's overall authority. Consolidating them into fewer, stronger pages consistently improves rankings.

SEO audit

Before migration, document: every URL on your current site and its current ranking position for any keywords; which pages are generating organic traffic and from which queries; any pages with significant inbound links from external sites; your current Core Web Vitals scores; and your current XML sitemap structure.

This data is your baseline. Every decision during the migration can be evaluated against it. Any URL that currently ranks or receives traffic needs to be handled carefully in the migration.

HubSpot portal audit

Review your existing HubSpot portal configuration: which properties are populated on contact records and how consistently; which lists exist and how they are used; which workflows are live and what triggers them; how your forms are currently structured and what they feed into. The website migration is an opportunity to tidy and improve the portal configuration alongside the site.

3. The migration process phase by phase

Discovery and strategy: weeks 1 to 2

Stakeholder interviews, content audit completion, SEO baseline documentation, HubSpot portal review, and new sitemap development. For migration projects, this phase also produces a redirect mapping document: a complete list of every current URL and its equivalent new URL, which will be used to configure 301 redirects at launch.

Copywriting: parallel workstream

If the migration includes content improvements or a full redesign, copywriting begins during discovery and runs in parallel with design. Rudo offers three tiers: strategic guidance (agency outlines, client writes), hybrid (Rudo writes core pages), or full copywriting. For migration projects involving significant content improvement, the hybrid option is most commonly chosen.

Design: weeks 3 to 6

If the migration includes a redesign, UX and wireframing precede visual design. For a lift and shift, this phase involves translating the existing design into HubSpot's module architecture: creating the template and module library that will underpin the new site.

HubSpot development: weeks 7 to 12

Template and module development in HubSpot's HubL templating language. Content migration into the new templates. CRM property mapping: ensuring all form fields connect to the correct CRM properties. Workflow setup and testing. Smart content configuration if included in scope. Redirect implementation: all 301 redirects must be configured before launch.

QA and launch: weeks 13 to 14

Full QA across all pages, forms, integrations, and redirects. Pre-launch SEO check: verify all redirects are correct, all meta titles and descriptions are in place, XML sitemap is submitted, and canonical tags are configured. Staged launch followed by post-launch monitoring during the first 30 days.

For a detailed week-by-week breakdown of project timelines, read our B2B website project timeline guide.

4. Protecting your SEO rankings during migration

SEO protection is the most technically critical aspect of any website migration. Done correctly, a migration preserves existing rankings and creates conditions for improvement. Done incorrectly, it can cause lasting damage that takes months to recover from.

301 redirect mapping: non-negotiable

Every URL that changes during the migration needs a 301 redirect to its new equivalent. A 301 redirect tells search engines that the page has permanently moved and transfers the ranking authority of the old URL to the new one. Without it, you lose that authority permanently.

Common redirect mistakes: redirecting all old URLs to the homepage (search engines treat this as a soft 404); missing redirects for secondary pages that have some authority; and redirecting old blog posts to the new blog index page rather than to equivalent posts.

Canonical tag configuration

HubSpot CMS supports canonical tags natively. Configure them during the build phase to ensure that any pages accessible from multiple URLs (www and non-www, HTTP and HTTPS, trailing slash and no trailing slash) consistently signal the preferred URL to search engines.

XML sitemap submission

HubSpot automatically generates and maintains an XML sitemap for your site. After launch, submit the new sitemap to Google Search Console and Bing Webmaster Tools. Monitor the index status of your migrated pages in Search Console during the first 30 days.

Monitoring the first 30 days

Set up weekly ranking checks for your most important keywords in the first month after launch. Some fluctuation is normal as search engines process the migration. Significant, sustained drops in rankings for pages with correct redirects in place should trigger a technical SEO investigation.

Find out more about our HubSpot CMS development services.

5. CRM and workflow setup during migration

The HubSpot CMS migration is an opportunity to improve your portal configuration alongside the website. Many companies who have been using HubSpot CRM without a native website integration have messy portal setups: inconsistent property usage, outdated workflows, and form structures that do not connect cleanly to their pipeline.

Form and property mapping

Every form on the new HubSpot CMS site needs to be mapped to the correct CRM properties. This means reviewing each form, confirming which properties each field should populate, and ensuring the data model is consistent. If your portal has multiple forms collecting the same information into different properties, the migration is the time to standardise.

Workflow review and rebuild

Existing workflows that were triggered by plugin-connected form submissions need to be reviewed and often rebuilt to work with the native HubSpot CMS connection. Website-triggered workflows, such as notifications when a contact visits the pricing page, can now be set up natively without the limitations of the plugin approach.

Lead routing and assignment

With a native HubSpot CMS connection, form submissions can be routed to the correct sales rep or team based on any CRM property: company size, industry, geography, or product interest. Set up lead routing rules during the migration rather than relying on manual assignment after launch.

6. The redesign opportunity: making the most of your migration

The most valuable migration projects treat the platform move as a strategic reset, not just a technical exercise. Here is what to address alongside the migration to maximise the long-term value of the investment.

• Improve the information architecture. Restructure the navigation and sitemap around the buyer journey rather than reproducing the existing structure. This is most impactful for sites that have grown organically and accumulated structural inconsistencies.
• Refresh thin content. Any page being migrated that has thin or outdated content should be updated during migration rather than migrated as-is. This is particularly impactful for pages with some organic visibility that are underperforming relative to their ranking potential.
• Implement smart content from day one. Set up your first smart content rules during the build phase rather than adding them later. Starting with lifecycle stage personalisation on the homepage hero takes a few hours to configure and delivers immediate conversion improvement for known contacts.
• Configure attribution reporting. Set up HubSpot's revenue attribution reporting during migration so you have a baseline from which to measure the website's commercial contribution from launch day.

For more on using migration as a redesign opportunity, read our HubSpot CMS vs WordPress guide and our section on migration in the pillar page.

7. Common migration mistakes

• Treating migration as a technical exercise only. Moving existing content to a new platform without improving it is a missed opportunity. The incremental effort to improve content during migration is small compared to doing it as a separate project later.
• Incomplete redirect mapping. Missing redirects for secondary pages, blog posts, or tag pages. Every URL with any organic traffic or ranking position needs a redirect.
• Not configuring CRM integrations before launch. Launching the site and then figuring out the CRM connection creates a gap in your lead data and workflow coverage. Configure integrations before the site goes live.
• Launching without submitting the new sitemap. Google needs to be told about the new site structure. Submit the sitemap to Search Console on launch day.
• Not monitoring rankings in the first 30 days. Ranking fluctuations after migration are normal, but significant sustained drops need to be investigated and addressed quickly. Set up weekly rank tracking before launch.

8. Frequently asked questions

How long does a HubSpot CMS migration take?

A lift and shift migration of a mid-size B2B website typically takes 8 to 12 weeks. A migration with a redesign typically takes 12 to 16 weeks. The most variable factor is the content improvement workstream: how much content is being refreshed, and who is doing the writing.

Will migrating to HubSpot CMS affect my SEO rankings?

A migration handled correctly should not negatively affect your rankings and may improve them. The critical requirement is comprehensive 301 redirect mapping for every URL that changes. Missing redirects are the most common cause of post-migration ranking drops.

Can I migrate from WordPress to HubSpot CMS?

Yes. A WordPress to HubSpot migration involves rebuilding all page templates in HubSpot's HubL architecture, migrating content and media assets, configuring CRM integrations natively, and mapping all changed URLs to 301 redirects. It is one of the most common migrations Rudo executes.

Should I redesign during migration or migrate first and redesign later?

We recommend redesigning during migration in most cases. The marginal cost of doing the strategic and design work during a migration is smaller than doing it as a separate project later, and you avoid the risk of launching a migrated site that has the same structural and conversion problems as the original.

How much does a HubSpot CMS migration cost?

A lift and shift migration typically costs £8,000 to £18,000 depending on site size and complexity. A migration with redesign typically costs £18,000 to 45,000. The HubSpot Content Hub subscription adds approximately £400 per month (Professional tier) to ongoing costs.

Back to the complete guide to HubSpot CMS for B2B websites.