Loading...
Loading...
HubSpot CMS → Sanity port
Move the website, blog and landing pages to Sanity on Vercel. CRM data, workflows and standard embedded forms remain in HubSpot. The inventory identifies CMS-only features that need replacement.
Three routes
The smallest change that takes the licence off your budget is the right one. I will tell you which one I think it is after I look at your portal.
The licence is not the real cost. What you have needs a tidy-up, not a move. If the inventory says that, I tell you and the job stops there.
Inventory only.
Your design is fine and the licence is the problem. Move the pages, blog and HubDB content onto Sanity and Vercel, then reconnect HubSpot.
Scoped in writing after the inventory.
You need new pages, a block system, permissions and rebuilt personalisation, not a copy of what you have. This is a project, not a move.
Scoped as a project, in writing, after the inventory.
Who does the work
Scope
The process
Start the inventory well before your Content Hub renewal date. The written scope comes after the inventory, and it carries the dates. You approve it before the build starts.
You and I agree the pages in scope, the HubSpot systems that stay, who decides, and what AI may do.
Output: A written scope and a set of control rules.
I list your pages, HubL modules, HubDB tables, forms, redirects, integrations and your renewal date. You mark what the business cannot lose.
Output: A migration map, a redirect list and my route recommendation. This is a standalone piece of work. You can take it and stop. You are not committed to the port until you approve step 3.
I set up the Sanity structure, the reusable blocks, the permissions, a preview site and a backup. You supply the access.
Output: A working system, ready for your content.
I move the approved content. I embed your HubSpot forms and install the tracking code. Then I wire up the CTAs and the chat.
Output: A complete preview site with HubSpot reconnected and a visible change log.
I test layouts, links, metadata and redirects. I submit a test form, then check the new contact and its source in HubSpot.
Output: An acceptance checklist plus a recorded test of the form and the attribution.
I record the rollback point, launch, and check the live site. Then I show your team how to edit, approve and restore a version.
Output: A live site, an editor guide, a rollback point and your wind-down dates for Content Hub.
If you want AI in it
The CMS works with AI switched off, and most teams start that way. If you include it, these controls become acceptance requirements in the written scope.
Safeguards
This move puts three things at risk: your search results, your forms and your lead attribution. Here is what holds each one down.
Questions
No. Only the website moves. Content Hub and the CRM are separate products, so contacts, deals, email, workflows and reports stay where they are. The CRM is not part of the move, and I do not write to it.
Standard HubSpot forms do. They are built to embed on pages outside HubSpot, and pop-up forms work the same way. The fields, the validation and the list they feed carry over. Smart forms are the exception, because HubSpot runs those on HubSpot pages only. Your submission history stays in your portal.
I test a real form submission on the preview site. I then confirm that the contact, consent, source and workflow outcome appear correctly in HubSpot. The acceptance checklist records the result before launch.
Smart CTAs keep working on the new site. Smart forms and smart modules do not, because HubSpot runs those on HubSpot pages only. Memberships and gated content also need a HubSpot subdomain. Rebuilt personalisation and a login area are separate work, and I scope them separately.
No. Read this before you pick a launch date. HubSpot does not allow a mid-contract downgrade, so the change takes effect at renewal. HubSpot also unpublishes HubDB, dynamic and private pages after a downgrade, and the hosted subdomain goes with them. So the new site must own those pages first. I give you the date list at handover.
I compare the Sanity, hosting and retained HubSpot costs against your current bill in the written scope. Your HubSpot contract and bundle decide what actually changes.
It is the main risk, so it gets the most attention. I inventory the URLs, metadata and redirects before the move. I test them on the preview site, and monitor search performance after launch. I cannot guarantee rankings. The scope controls the migration risk. It does not promise a search result.
Yes for day-to-day content: page copy, images, blog posts, landing pages, navigation and SEO fields. No for structural change, such as a new content type or a change to how a block looks. We agree the exact edit list in step 1, and it goes in the written scope.
You own the site, the code and the accounts. The repo sits in your organisation. The Sanity project is in your name, and the Vercel project is on your billing. The written scope states the defect warranty. After that you can send me work, or your team can self-serve on the repo. You can also hand it to any Next.js developer. That last point matters when you buy from one person. There is no lock-in and no subscription to me.
Send the site URL, the latest Content Hub invoice and the renewal date. I will identify what can leave, what must stay and whether a written inventory is justified.
Send the bill and renewal date