Keep HubSpot. Move the website.
Your CRM, forms, and attribution stay exactly where they are. The website moves to a codebase your team updates by asking its AI agent, and every lead still lands where your sales team expects it.
In short
A HubSpot CMS migration moves the website, not your CRM. ZINC rebuilds your pages and blog on Astro or Next.js, keeps HubSpot forms, tracking, and lead routing working, and maps every URL before launch.
This website runs exactly that way: a Next.js site with HubSpot CRM behind it, governed through Dispatch.
25+ years of strategy, design, and digital delivery for brands including:
Your CRM is not the problem. The website is.
Stop paying for pages you could ask for.
Many teams pay for CMS tiers mainly to build pages. With an agent, a new landing page is a request and a preview.
Templates without the friction.
Modules and themes rebuilt as clean components your agent reuses, so new pages stay on brand.
Same leads, same reports.
HubSpot tracking and forms stay in place, so attribution and lead routing continue without a gap.
Every HubSpot feature gets a destination.
The CRM stays. Everything the website did gets an agreed replacement, an owner, and a test.
| On HubSpot CMS | After the move |
|---|---|
| HubSpot forms | Kept as embedded HubSpot forms, or rebuilt natively with delivery straight to the CRM. Both tested to the inbox. |
| Tracking code and attribution | Kept on every page, so contact timelines and campaign reports continue. |
| Website and blog pages | Exported, rebuilt page for page, with every URL kept or mapped one to one. |
| Themes, templates, and modules | Rebuilt as reusable components your agent works with. |
| Smart content and personalization | Assessed for what earns its keep, then rebuilt or retired with your sign-off. |
| Campaign landing pages | Moved, or left on HubSpot if marketing operations depends on them. Your call, not ours. |
Your design, content, and URLs come with you.
The site moves page for page onto Astro or Next.js on Cloudflare, Vercel, or Netlify. We recommend the stack because we sell none of them.
- HubSpot CRM, forms, tracking, and lead routing
- Design preserved and verified at representative pages and viewports
- Pages, posts, images, PDFs, and media
- URLs preserved where possible, every other one mapped with a 301
- Your code in your own repository, on your own hosting account
- Dispatch connected at cutover, so every agent change is previewed and approved
Nothing gets designed until every URL has a plan.
The same six steps on every move, written down while we moved our own website. The boring part comes first, because the boring part is what protects your traffic and your leads.
- Step 01
Inventory every URL.
We crawl the live site and list every page by template before anything is designed or built.
On our own moveOur site: 49 live URLs across six templates, each with a destination before a line of code.
- Step 02
Keep the URLs.
Same paths, same slugs. An address only changes when a 301 redirect is in place for it.
On our own move44 kept their exact address. 5 retired pages got 301s. Our highest-traffic page never moved.
- Step 03
Export everything.
CMS content, every file on the old platform’s CDN, and the rendered HTML of every page as the reference copy.
On our own move549 files moved off the old CDN. 4 CMS collections, 45 items, imported and checked.
- Step 04
Parity first. Then improve.
The first version is a faithful copy: same pages, same copy, same metadata. Changes come after sign-off, so any traffic shift has one cause to look at, not ten.
On our own moveOur first complete build took one day, compared page by page against the original by screenshot.
- Step 05
Prove the business paths.
Forms, CRM delivery, notifications, analytics, and consent are tested end to end, from the visitor’s click to the right person’s inbox.
On our own moveLesson we learned: a form that saves a lead is not a form that tells anyone. We test to the inbox now.
- Step 06
Govern, launch, and watch.
Dispatch is connected before the agent touches production. Redirects go live at cutover, the sitemap is submitted, and 404s and indexing are watched closely.
On our own moveSince our launch: 36 reviewed changes in six weeks, each one previewed before release.
We moved our own website first.
wearezinc.com moved from Webflow to Next.js in August 2026, using the same six steps. Here is what that looked like.
- live URLs kept or redirected
- 49 of 49
- files moved off the old CDN
- 549
- to the first complete build
- 1 day
- reviewed changes in the first six weeks
- 36
When staying on HubSpot CMS is the right call.
A move should pay for itself. Sometimes it will not, and we will tell you.
- Your marketers build landing pages in HubSpot every day
- Smart content and memberships are central to the experience
- Your HubSpot bundle makes the CMS effectively free
See your site off HubSpot CMS, with HubSpot still behind it.
Give us your URL. We rebuild two pages on an agent-ready stack with your HubSpot form connected, run one real change through Dispatch, and send back a migration map. No commitment.
Questions about leaving HubSpot CMS.
No. The HubSpot tracking code goes on every page of the new site, and forms either stay as HubSpot embeds or post straight to the CRM. Contact timelines and campaign reports continue without a gap.
Yes. wearezinc.com is a Next.js site. Every form submission is saved, sent to HubSpot, and emailed to our team, and we test that path to the inbox on every launch, because a lead nobody sees is not a lead.
Not if the move is done with discipline. Rankings slip after a migration for three reasons: URLs that break, page signals that get dropped, and crawl problems after launch. We keep URLs wherever we can, redirect the rest one to one, carry over every title, description, and heading before changing anything, and watch 404s and indexing closely after cutover. Some fluctuation while search engines re-crawl is normal, so we do not promise unchanged rankings. We do promise not to guess.
You do. The code lives in your own repository, the hosting account and domain stay in your name, and the content is yours. Turn Dispatch off and the website keeps running.