
Short answer: Move to HubSpot CMS when your marketing team lives in HubSpot and wants to build and change pages without a developer. Stay put when the site is mainly ecommerce or app-like, or when a well-integrated WordPress site is doing the job. If you move, build a custom theme your team can actually edit, keep every URL that earns traffic, redirect the rest one to one, and watch Search Console for a month. A HubSpot CMS migration with us starts at £7,500, $10,000 or €8,650, and a full design and build from £10,500, $14,000 or €12,100.
We’ve delivered 40+ HubSpot CMS website builds. The questions are always the same. Should we move at all? Template or custom? Will we lose our rankings? Can we edit it ourselves afterwards?
Here are the honest answers, with what we’ve seen go right and wrong.
Should your site move to HubSpot CMS at all?
Good reasons to move:
- Marketing runs campaigns, forms and emails in HubSpot already
- You want to build and edit pages without waiting on a developer
- You want hosting, security and updates handled
- You want personalised content and reporting tied to the CRM
Good reasons not to:
- Ecommerce first. If the site exists to sell products online, Shopify connected to HubSpot is usually better.
- App-like functionality. Complex booking engines or logged-in tools may belong elsewhere.
- A WordPress site that works. HubSpot’s tracking code plus HubSpot forms on WordPress gives you most of the reporting benefit. On a scoping call this year I told a prospect exactly that: integrate first, move later if it’s still worth it.
You can stage it too. One client is moving just their blog into HubSpot first and leaving the rest of the site where it is.
Custom theme or marketplace template?
This is the decision that most affects how you’ll feel about the site in two years.
A head of marketing at a construction software company asked us this year whether to buy a marketplace theme and fit their new brand to it. Their existing site was built on an old theme with over 100 modules, many of them unclear and some “built for old HubSpot, not new HubSpot”. The day-to-day problems were exactly what you’d expect:
- Modules were locked: “what you get is what you get”
- Only preset colours, with no way to add new brand colours
- Sections couldn’t be saved and reused, so every logo slider meant re-uploading and resizing logos by hand
- Anchor links on buttons meant editing source code, for someone who said plainly “I’m not a coder”
That’s what a generic theme turns into over time. Marketplace themes are built to suit everyone, which means lots of options nobody needs and limits on the ones you do.
We recommended a custom theme instead. Their plan came out at around 15 templates and 40 to 45 modules, with a reusable section library, drag-and-drop layouts, brand colour controls, no-code anchors and schema built into the modules. There was no real time or cost saving in starting from a marketplace theme, once you account for bending it to the brand.
| Marketplace template | Custom theme | |
|---|---|---|
| Upfront cost | Lower | Higher |
| Looks like | Lots of other sites | Your brand |
| Editing | Often clunky, many unused options | Built around your pages |
| Long-term | Gets brittle as HubSpot changes | Designed to be maintained |
Can we edit it ourselves after launch?
You should be able to. If you can’t, the build was done wrong.
We’ve seen migrations elsewhere delivered as hard-coded HTML, which means nobody on the client side can edit anything without a developer. We’ve rebuilt more than one of those.
Our rules:
- No hardcoded content. Every page is built from modules your team can edit.
- A reusable section library, so common blocks are built once.
- Global modules for anything repeated across pages (like a form used on 40 product pages), so one change updates them all.
- A written training guide with screenshots, plus live training before handover.
One client’s new marketer had never used HubSpot before, and the person who knew their old CMS had left. Training plus a step-by-step guide covering staging, URLs, modules, building and editing pages is what made the handover work.
How to move without losing SEO
Most ranking losses after a migration come from missed redirects. A buyer told us this year about a previous migration where “they didn’t move any of the SEO across” and added no redirects. They lost years of history.
Before you build
- Crawl the current site. Every URL, title, meta description, heading and canonical.
- Pull the pages that matter. From Search Console and analytics (clicks, impressions, conversions) and from a backlink tool (what gets linked to).
- Decide keep, merge or drop for every page. Not every page needs to survive. The ones that earn traffic or links do.
- Build the redirect map. One row per old URL with its new destination, one to one wherever possible. Redirecting everything to the homepage throws away the value those pages built.
On the construction software rebuild, cleaning up a messy URL structure would have created “a thousand redirects”. So the page inventory captured metadata and target URLs from day one, and became the redirect map.
During the build
- Keep high-value URLs unchanged where the new structure allows. On that same rebuild, keeping the regional URL paths meant most pages simply replaced their old versions with no redirect needed.
- Use HubSpot’s content staging when rebuilding existing HubSpot pages. A staged page replaces the live one on publish and keeps its URL.
- Carry across titles, meta descriptions and headings, then improve them. Many old pages we audit have no meta description at all.
- Rebuild schema (organisation, FAQ, product or service) and test it.
- Handle languages properly. Language variants and hreflang need setting up, not just cloned pages.
- Watch page speed. We promise 90+ desktop and 70+ mobile PageSpeed at go-live, because a slower new site gives back what it should have gained.
Forms: audit first
One client had 105+ forms in HubSpot. Filtering by where each form appears showed plenty with zero submissions. Those go to draft before the rebuild, so nobody links a new page to a dead workflow. Existing HubSpot forms keep their workflows when placed on new pages, and pick up the new site’s styling automatically.
Moving to a new domain
A rebrand onto a new domain is the riskiest version. We advised an events business with around 1,000 referring domains on exactly this. Our advice: a full page-by-page 301 redirect plus Google Search Console’s Change of Address tool. Done well, expect to lose somewhere between 10% and 20% of organic value while Google catches up. Keep the old homepage live and redirect only some pages, and you risk losing most of it, and you can’t use Change of Address.
Before launch
- Test every form, including where the data lands in HubSpot
- Check tracking codes and cookie consent
- Check for broken links, missing images and empty buttons
- Make sure staging isn’t indexed, and the live site is
After launch
Submit the new sitemap. Watch Search Console for 404s and coverage errors every few days for the first month, and fix anything missed the same day. A dip in the first couple of weeks is normal. A steady fall isn’t.
AI search too
Answer engines quote pages that are easy to read: clear headings, direct answers, FAQ blocks with schema, and consistent facts about your business. A migration is the best time to build that in.
What good looks like
Before Imagine Growth, Rikki and Mark founded the agency that became the UK’s largest HubSpot partner. There, after nShift’s acquisition, we merged four multilingual websites into one and two CRMs into one HubSpot, keeping organic traffic through the move. Domain authority rose 42 points, with 62,346 organic sessions and 7,000+ ranking keywords.
At Imagine Growth, Action Insurance Repair came to us with a site that had lost 76% of its monthly users. After a full HubSpot CMS rebuild with clear paths for five audiences, engagement rose 250%. It’s in our Action Insurance Repair case study.
What it costs
| Service | Starting price |
|---|---|
| HubSpot CMS migration | £7,500 / $10,000 / €8,650 |
| HubSpot website design and build | £10,500 / $14,000 / €12,100 |
| Website support and optimisation | £1,500 / $2,000 / €1,750 a month |
The price moves with the number of templates and modules, how many pages are rolled out and in how many languages, and anything interactive (calculators, maps, database-driven pages). A theme plus templates with your team rolling out the remaining pages costs much less than us building every page.
Frequently asked questions
Should we move our website to HubSpot CMS? Move if marketing works in HubSpot and wants to edit pages without developers. Stay put if the site is ecommerce-first, app-like, or a WordPress site that integrates well with HubSpot.
Is a HubSpot marketplace theme good enough? For a small, simple site, sometimes. For a site your team will grow and edit for years, a custom theme built around your pages is easier to live with and doesn’t look like everyone else’s.
Will we lose SEO if we move to HubSpot CMS? Not if the move is planned. Keep valuable URLs, redirect the rest one to one, carry metadata and schema across, and monitor Search Console after launch.
What is a redirect map? A list of every old URL and its new destination, so visitors and search engines land on the right page after the move.
How much SEO do you lose when changing domain? With a full page-by-page 301 redirect and Search Console’s Change of Address, a 10% to 20% temporary loss is a reasonable expectation. Partial redirects risk losing most of it.
Can we edit a HubSpot website ourselves? Yes, if it’s built from editable modules rather than hard-coded HTML. Ask for a reusable section library and training before handover.
How much does a HubSpot CMS migration cost? With Imagine Growth, from £7,500, $10,000 or €8,650. A full design and build starts from £10,500, $14,000 or €12,100.
Next: see how we handle HubSpot CMS migration and website design and build.


