Pages and templates
Rebuild core pages, landing pages, reusable modules, global sections, navigation, and footer patterns inside HubSpot CMS.
HubSpot CMS migration
HubSpot CMS Migration Scope
Define what needs to be rebuilt inside HubSpot CMS: page templates, editable modules, structured content, blog and forms. This scope guide covers the website build; a CRM data import needs a separate plan.
Scope
What a HubSpot CMS migration includes
A HubSpot CMS migration is broader than copying pages. The destination needs templates, modules, navigation, blog structure, forms, tracking, redirects, and a launch process that protects existing search and conversion paths.
Content and blog
Move approved copy, blog posts, authors, media assets, downloads, internal links, and content relationships that should survive the move.
Forms and CRM paths
Reconnect forms, CTAs, thank-you pages, meeting links, routing rules, and tracking so the website works with HubSpot after launch.
CMS build decisions
Choose a destination for each content type
Pages and reusable modules
Group source pages by layout and editing needs. Specify reusable components, global navigation and editable fields rather than commissioning a separate template for every URL.
Blog and structured content
Map posts, authors, dates and tags separately from product directories or other structured entries. Verify plan requirements and relationships before choosing dynamic pages, HubDB or a simpler page-based model.
Functionality and acceptance
Document search, multilingual content, protected areas, forms and integrations. Give each requirement a test and an owner; flag custom functionality that cannot be transferred directly.
For the full project sequence, read the website migration planning guide. For an implementation quote, use the HubSpot website migration service. Source-specific mapping is covered in the Drupal content-type guide and WordPress migration checklist.
Decision point
Migration or integration?
Some teams only need a form or tracking connection. Others need the website itself rebuilt inside HubSpot CMS. The right choice depends on whether the current site is still a good operating system for marketing.
Use integration when
- The current CMS is easy to manage
- Only forms, tracking, or CRM sync need improvement
- There is no major SEO or editing problem
Use migration when
- Editors depend on developers or fragile templates
- Forms and reporting are fragmented
- The site needs a cleaner HubSpot-native structure
Next step
Need help scoping a HubSpot CMS migration?
Start with the HubSpot website migration service, or compare platform-specific paths for WordPress, Webflow, Wix, and Squarespace.