How to migrate your site into the HubSpot CMS

Most people interested in migrating from their current platform to HubSpot typically want a single price and solution. In reality, the cost of a website migration isn't driven by the CMS licence or the number of pages, but by risk and complexity.

Think about how much needs to be preserved, from SEO equity and tracking to forms and workflows. How many teams will be involved? How tightly the website connects to your CRM and commercial reporting, and so on.

Today, HubSpot's website platform is packaged as Content Hub, which is what many people still call HubSpot CMS. If you're moving from a legacy system into Content Hub, you're moving a part of your growth infrastructure, not just content.

What are you actually migrating?

A website migration usually includes more than just pages. It involves:

• Content: Pages, blogs, premium downloads, media, landing pages

• Templates and modules: How pages are built and edited

• SEO equity: URLs, redirects, metadata, internal linking, indexation

• Tracking and consent: Analytics, tag manager, cookie banners, event tracking

• Forms and data capture: Form logic, spam controls, CRM property mapping

• Workflows and lifecycle logic: Notifications routing, follow-ups, segmentation if the site is CRM-connected

The more of these your website relies on, the more the migration is an operational project, not a simple copy-and-paste exercise.

The three main cost drivers

1. Complexity

Page count matters, but complexity is more important. A 50-page brochure website can be simple, but a 20-page website with multiple languages, gated content, dynamic modules, integrations, and strict governance can be complex.

2. What you're trying to protect

The cost rises when you need to protect:

• Existing ranking and traffic
• Conversion tracking and attribution
• CRM data integrity and reporting
• Internal publishing processes and governance

3. How much you want to change at the same time

Combining a platform move with a redesign, content overhaul, IA change, rebrand, or new governance model increases scope and cost because you're doing multiple high-impact changes at once.

Migration options

Most teams choose the wrong migration route because they decide based on what the tool can do or optimising for the lowest-cost move, rather than focusing on the lowest-risk outcome.

Option 1: Lowest friction replatforming

Choose this if: Your website is relatively simple, you aren't making many structural changes, and you mainly want to move onto Content Hub quickly.

What this typically looks like: Your existing site is recreated in Content Hub using an existing theme approach rather than a fully bespoke build. HubSpot’s own Website Migration service describes recreating website content in Content Hub using a theme, which involves templates and modules.

What you still need to own: Redirects, tracking validation, and post-launch checks. Even in a simple migration, these are the things that create avoidable problems if left until launch week.

Best for: Brochure sites, lean marketing teams, and minimal integrations.

Option 2: Theme/template-led rebuild

Choose this if: Your team wants the migration to result in a website that’s easier to operate, faster to launch pages, easier to maintain, and less dependent on developers.

What this typically looks like: You migrate to a defined theme/template system so your team can build and iterate without constantly rebuilding layouts. HubSpot’s migration and template setup process is documented in its Knowledge Base and is commonly used as a structured starting point.

Trade-off: You’ll spend more time upfront getting the foundations right, but you reduce friction after launch.

Best for: Teams publishing regularly, multi-stakeholder approval flows, and sites that need consistent UX and governance.

Option 3: Partner-led migration

Choose this if: Your website is part of a complex stack, a regulated environment, multi-language delivery, or it’s tightly connected to CRM workflows and reporting.

What this typically includes: An audit-led plan, controlled cutover, and post-launch stabilisation, with ownership across redirects, tracking, forms, CRM data mapping, and governance. This is the route teams choose when they want a migration that holds up operationally, not just visually.

Why it often costs more: As you’re paying for risk management, not just for building hours. The cost difference usually shows up in what doesn’t happen, such as traffic loss, broken tracking, broken forms, and internal confidence dropping after go-live.

Best for: Enterprise environments, complex integrations, multi-country teams, high-volume lead capture and lifecycle automation.

What usually breaks in a website migration

This is where most migrations go wrong. It isn't because HubSpot has failed. It's because the migration is typically treated as a content move instead of a systems cutover.

Forms and the data behind them

• For logic changes, such as required fields, progressive profiling, and spam controls
• CRM property mapping breaks or becomes inconsistent
• Routing and notifications don't match the intended workflow

Tracking and attribution

• Tracking scripts fire twice, not at all, or inconsistently across templates
• Cookie consent unexpectedly blocks events
• Conversions no longer match CRM outcomes, reducing confidence quickly

Redirects and SEO equity

• Missing redirect coverage, especially for legacy content
• Redirect chains and loops
• Canonical tags and internal linking aren't rebuilt cleanly

Modules, templates, and how pages are built

• Legacy layouts don't map neatly into the new page-building system
• Components behave differently across breakpoints
• Teams lose editing autonomy if the component model isn't planned

Workflows and lifecycle automation

• Lifecycle logic is misaligned, even if lead capture is live
• Nurturing triggers don't match intent
• Reporting becomes noisier because definitions weren't governed

A good rule to follow is that your website migration isn't finished when pages load. It's only truly finished when tracking, forms, and CRM reporting can be trusted again.

The cost of your website migration depends on the option you choose and the level of complexity you need to manage. A low-risk, simple migration will be cheaper than an enterprise, multi-language, CRM-connected migration with governance, tracking validation, and a controlled cutover.

When focusing on the cost, ask how much it would cost you if the migration went wrong. In reality, the most expensive migrations are the ones you have to fix after launch.