HubSpot to Astro migration

Move from HubSpot CMS to Astro and keep your HubSpot CRM

We move your website out of Content Hub into Astro code you own, with content in Sanity. Forms, tracking and meetings keep feeding your HubSpot CRM and every URL has a plan before launch.

  • 50+ B2B SaaS teams trust us
  • 5.0 out of 5 stars
  • 5.0 out of 5 stars
  • 5.0 out of 5 stars
Timeline
8–12 weeksIncluding form and tracking tests in the CRM.
SEO risk
MediumHubSpot redirects only work on HubSpot. We transfer them to your new hosting.
Content
Carried overBlog posts, page content, HubDB tables, images, metadata
Design and features
RebuiltTheme, HubL modules, drag and drop layouts, smart content
Price
Fixed priceSet once we have checked every URL.

Why teams switch

Why SaaS teams leave HubSpot CMS

01

The site should show product data

Integrations, changelog entries or plan features come from your product. In Astro, the site reads that data from your API or from Sanity, instead of someone copying it into HubDB rows by hand.

02

Content is locked inside single pages

In drag and drop areas, the copy belongs to one page. In Sanity, use cases, integrations and customer quotes are documents of their own that you reuse across many pages.

03

Your team wants to work with AI agents

Claude and Codex work in your repository and in Sanity. Your team describes a change, checks the preview and approves it. A theme in the design manager is a detour for that.

04

Content Hub mostly pays for the website

If the CRM and Marketing Hub stay, it's worth asking which Content Hub tier you still need afterwards. That depends on what you use it for beyond the website.

HubSpot CMS vs. Astro

What changes in your marketing week

CriterionHubSpot CMSAstro
Editing pagesPage editor with drag and drop areas and modules from the theme.Fields in Sanity Studio, new pages built from existing components through the AI workflow, with a preview.
Forms and trackingIncluded on every HubSpot page automatically.Tracking code added once in the layout, forms via embed code or the Forms API. Data lands in the same CRM.
Structured dataHubDB tables that generate dynamic pages.Sanity documents, plus data from your product API or HubSpot's APIs.
Personalization and testsSmart content and A/B tests right in the page editor.Not built in. Added with code or a testing tool when you need it.
New featuresCustom HubL modules or ready-made modules from a theme.Built as code, with a development partner or your own tech team.

HubSpot CMS

  • Page editor with drag and drop areas and modules from the theme.
  • Included on every HubSpot page automatically.
  • HubDB tables that generate dynamic pages.
  • Smart content and A/B tests right in the page editor.
  • Custom HubL modules or ready-made modules from a theme.

Astro

  • Fields in Sanity Studio, new pages built from existing components through the AI workflow, with a preview.
  • Tracking code added once in the layout, forms via embed code or the Forms API. Data lands in the same CRM.
  • Sanity documents, plus data from your product API or HubSpot's APIs.
  • Not built in. Added with code or a testing tool when you need it.
  • Built as code, with a development partner or your own tech team.

What moves

What comes over from HubSpot

Content moves to Sanity and the CRM connection stays. Anything tied to HubL or to HubSpot-hosted pages is rebuilt or replaced.

  • Migrated
  • Partly
  • Rebuilt
  • Replaced
  • Blog posts

    Migrated

    We read them through the blog APIs, with author, tags, publish date and slug and create them as documents in Sanity.

  • Website and landing pages

    Partly

    The Pages API returns copy and module data for each page. Layouts that were assembled freely in drag and drop areas get mapped to fixed sections, page by page.

  • HubDB tables

    Migrated

    Each table becomes a document type in Sanity and each row a document. Dynamic pages built on HubDB become Astro routes with the same paths.

  • Forms, meetings and chat

    Migrated

    Forms stay in HubSpot and appear on the site via embed code or as your own component that posts to the Forms API. The meetings widget and chat keep running via embed and tracking code.

  • Images and files

    Migrated

    Images from the files tool go to Sanity with their alt text. We list files that emails or campaigns link to up front, so no link ends up broken.

  • Theme and HubL modules

    Rebuilt

    Templates, modules and drag and drop areas are HubL and only run in HubSpot. We rebuild them as Astro components that Sanity fills with content.

  • Smart content and page tests

    Replaced

    Smart modules and page A/B tests only exist on HubSpot pages. Smart CTAs work externally with the tracking code. The rest we rebuild in code or drop.

  • Members-only content

    Replaced

    Private content for access groups is tied to HubSpot pages. It either stays on a HubSpot subdomain or becomes a separate project with its own login.

For your marketing

What keeps running for your marketing

Rankings are only one part. We also protect everything your team uses to measure leads and pipeline.

Tracking and attribution

GA4, the tag manager, UTM parameters and conversion events keep running from day one. In Astro tracking scripts load only after consent and do not slow the page. Before launch we compare every event on staging with the old site.

Forms and CRM

We embed your HubSpot forms on the new site. They keep sending into your HubSpot CRM with the same lead source, lifecycle stage and workflows. We check test leads right in the CRM.

Demo booking

Demo and contact pages, calendars like HubSpot Meetings, Calendly or Chili Piper and your chat stay in place. Old demo URLs from ads, emails and sales decks redirect straight to the new page.

Visibility in AI search

Structured data, clear headings and an up-to-date sitemap are in place from launch. That helps Google and AI search like ChatGPT or Perplexity find your pages again quickly.

Content mapping

How HubSpot content maps to Sanity

In HubSpotIn Astro
Blog postsAn "Article" document type in Sanityauthors and tags as references, not free text
Rich text modulesPortable Textstructured text instead of HTML snippets from the editor
Drag and drop areasPages made of fixed sectionseach section is an Astro component with its own fields
HubDB tablesCustom document typesfor example integrations, partners or events
Language variantsTranslated documents in Sanityeach variant stays linked to its primary language
URL redirects (CSV)Redirects in the Astro config or at the hostchains resolved first, so every rule points straight to its target

Process

How we migrate
your HubSpot site

An example project: 10 weeks to launch. Afterwards we monitor rankings and redirects for four more weeks.

Migration from HubSpot, example project

path digitalYour team

Your team

Access, sign-offs

SEO

URLs, redirects, tests

Build

Pages, content in Astro

Point at a step to see what happens there.

  1. Week 1 · Your team

    Kickoff

  2. Week 1 · SEO

    Audit and inventory

  3. Weeks 1–2 · SEO

    Content model and redirect plan

  4. Weeks 2–6 · Build

    Components and HubSpot connection

  5. Week 2 · Your team

    Redirect plan sign-off

  6. Weeks 6–8 · Build

    Content migration

  7. Weeks 8–10 · SEO

    QA, CRM tests and AI workflow

  8. Week 10 · Your team

    Launch

  9. After launch · SEO

    Launch and monitoring

Pre-launch checklist

What we check before launch

Stage 1 of 4

Before the build

Stage 2 of 4

During the build

Stage 3 of 4

Before launch

Stage 4 of 4

After launch

To be honest

When you should stay on HubSpot CMS

  • Smart content and page tests drive your conversion

    If your team shows different content by lifecycle stage or list and tests pages all the time, you lose that in the move. Rebuilding it in code takes time.

  • You have no development partner

    Your team edits content in Sanity and builds new pages through the AI workflow. New components and integrations still need someone who writes code.

  • Logged-in areas run on HubSpot

    If a customer portal or members area relies on access groups, part of the site stays in HubSpot anyway. Then we check whether moving the rest is worth it.

  • Your team wants to build pages visually

    If marketers assemble landing pages with drag and drop and want to keep doing that, HubSpot or Webflow is a better fit than Astro.

Frequently asked questions about migrating from HubSpot to Astro

What B2B SaaS teams want to know before moving from HubSpot to Astro.

Do we have to leave HubSpot CRM if the website moves to Astro?

No. Contacts, deals, emails and workflows stay in HubSpot. The site keeps sending form submissions there and the tracking code records page views on the new site.

Do HubSpot forms work on an Astro site?

Yes. You either embed them with the embed code or use your own forms that post to the HubSpot Forms API. In that case we pass along the HubSpot cookie and the page URL, so the contact keeps its activity history.

What do we lose in the migration?

Smart modules, A/B tests in the page editor and members-only content only work on HubSpot pages. Smart CTAs keep working with the tracking code. For everything else we decide before the build: rebuild it, keep it in HubSpot or drop it.

Can campaign landing pages stay in HubSpot?

Yes. HubSpot can host content on a subdomain while your main site lives elsewhere. That works well if your team wants to keep building campaign pages in the HubSpot editor.

How do the blog and HubDB get out of HubSpot?

HubSpot exports pages and blog posts as HTML, blog data as CSV or Excel and HubDB tables as CSV. For the migration we usually use the CMS APIs, because they return authors, tags and fields in a structured form.

Will we need developers for changes again?

Not for copy, entries or new pages built from existing components. Your team handles those in Sanity or through the AI workflow, with a preview and approval. New components or connections to product data are built by a development partner, as with our AI-native websites.

Plan your migration
from HubSpot to Astro

Show us your site and which HubSpot features you use today. We'll tell you what moves to Sanity, what stays in HubSpot and what gets rebuilt.