Website and landing pages
Accessible page identity, names, slugs, state, dates, metadata, rendered or structured content values, and public URLs.
Available migration objects and capabilities depend on the selected source and target systems. Check current integration status before using this planning guide.
What the migration covers
HubSpot is testing and source-only in the capability catalog. Standard planning centers on accessible CMS pages, blog posts, authors, tags, files, metadata, publication values, and source URLs.
Blog publishing
Blog posts, blog membership, authors, tags, publication data, excerpts, featured images, and source identifiers.
Files and media
File Manager assets and inline references that are accessible, approved, transferable, and traceable to their owners.
SEO and routing
Titles, descriptions, canonicals, language paths, redirects, internal links, and final destination mappings.
What requires separate scope
HubL templates, themes, modules, drag-and-drop areas, forms, submissions, contacts, companies, deals, lists, workflows, email, subscriptions, consent history, scoring, tracking, and private app behavior are not assumed to migrate with CMS content.
Separate CMS APIs from CRM scope
The HubSpot portal joins content, marketing, sales, service, identity, consent, and analytics; access to one layer does not authorize migration of the others.
Inventory content endpoints
Confirm website pages, landing pages, blogs, posts, authors, tags, files, HubDB, languages, domains, and archived records in scope.
Create a data boundary
List CRM objects, form submissions, subscriptions, consent records, workflows, email, analytics, and private app data as separate or excluded.
Use least privilege
Request only the private-app scopes required for approved CMS entities, then test pagination, archival state, rate limits, and file access.
Preserve source identity
Retain object IDs, blog membership, language, public URLs, and exception evidence for reconciliation and reruns.
Translate content, not HubL rendering
HubSpot page output can depend on templates, modules, theme fields, smart rules, and drag-and-drop configuration that do not become destination components automatically.
Profile every page family
Sample standard pages, landing pages, blogs, modules, dynamic pages, HubDB-backed views, multilingual variants, and gated routes.
Select extraction per type
Use structured fields where meaningful and reviewed rendered output where needed, with sanitization and embedded-dependency rules.
Prepare the destination model
Define page/post types, fields, taxonomy, authors, media, language, SEO storage, forms, and components before loading.
Assign functionality
Route modules, forms, personalization, chat, search, tracking, and CRM-driven behavior to reconstruction or an approved replacement.
Validate domains, consent, and launch ownership
A successful content load does not prove that forms, tracking, language routes, or CRM-connected journeys still work.
Reconcile CMS entities
Compare source, extracted, transformed, loaded, skipped, failed, archived, language, and accepted totals.
Inspect representative pages
Review rich content, authors, tags, images, modules, metadata, forms placeholders, links, language, and destination rendering.
Test public routes
Validate redirects, canonicals, hreflang, metadata, internal links, sitemap entries, file URLs, and priority conversions.
Assign operational changes
Document ownership for domains, forms, consent, tracking, CRM integrations, automation, analytics, and post-launch monitoring.
How the workflow works
- 1. Discover: Confirm portal access, CMS scopes, content types, blogs, domains, languages, HubDB, files, CRM boundaries, and destination readiness.
- 2. Map: Approve destination types, content extraction rules, authors, tags, media, languages, SEO, URLs, rebuild work, and exclusions.
- 3. Dry run: Load representative page families and blog posts into staging and resolve systematic template or module exceptions.
- 4. Validate: Reconcile CMS records and inspect content, assets, metadata, languages, links, rendering, and documented functional gaps.
- 5. Cut over: Run the approved final or delta transfer and coordinate domains, redirects, forms, tracking, and launch checks with their owners.
Technical references
Scope is reviewed against the source and destination documentation available for the project.