Migrating to HubSpot Content Hub: How to Preserve URLs, SEO, Forms and Tracking

Key Takeaways

• Treat a move to HubSpot Content Hub as a website, data and marketing-system migration, not a page-copying exercise.
• Preserve useful URLs where possible. Where a URL must change, map it to the closest replacement and configure a permanent redirect on the system that receives the old request.
• Inventory forms, fields, consent wording, follow-up actions, workflows and integrations before rebuilding them. A form that looks the same can behave differently behind the screen.
• Define one analytics and attribution plan across HubSpot, Google Analytics, advertising platforms and any remaining external pages, then test real events and CRM records.
• Run a controlled launch with backups, a content freeze, acceptance checks, rollback decisions and several weeks of technical and commercial monitoring.

Migrating to HubSpot Content Hub safely means preserving four connected systems: the website people use, the URLs search engines know, the forms that create or update CRM records, and the tracking that explains where enquiries came from. Moving the visible pages without mapping those relationships can produce a tidy launch and a serious data problem.

Begin with an inventory of the current site and marketing setup. Decide what should remain, what should improve and what should be retired. Then build and test the HubSpot replacement against that record. Do not use the migration as an excuse to change the domain, URL structure, copy, design, forms and measurement plan without being able to separate their effects.

Confirm Why You Are Moving to Content Hub

Write down the operational problem before choosing the migration scope. A business may want marketers to publish without a developer, connect pages with CRM activity, manage campaigns in fewer systems or standardise brand components. Those are different goals and need different acceptance checks.

Also name what HubSpot will not replace. The organisation may keep a separate ecommerce platform, product database, application, learning system or support portal. Draw the future architecture so domains, tracking and ownership are clear.

Use the existing WordPress versus HubSpot CMS comparison to revisit platform fit. A migration is difficult to reverse, so validate users, permissions, features, subscription limits, integration needs and expected ongoing costs against current HubSpot terms before committing.

A CMS development consultation can turn these requirements into a technical scope without assuming that every page must live on the same platform.

Build a Complete Current-State Inventory

Crawl and export the existing site before development begins. Include pages, posts, resources, landing pages, campaign paths, images, PDFs, forms and important error or confirmation states.

For each URL, record:

• response status and final destination;
• title, meta description, headings and canonical;
• indexability and sitemap inclusion;
• organic visits, impressions, clicks and conversions;
• internal and external links;
• content owner and last useful update;
• template and reusable components;
• forms, calls to action and tracking events;
• proposed action: retain, improve, merge, redirect or remove.

Inventory the systems around the pages as well: DNS, CDN, hosting, cookie controls, tag manager, analytics, advertising pixels, chat, CRM, email, meeting tools, payment links and automation. Record account owners and access without putting secrets into the migration document.

Our website migration SEO checklist provides a detailed baseline. If current data is incomplete, label the gap rather than inventing a clean history.

Preserve the URL Structure Where It Still Makes Sense

Keeping established, useful URLs reduces change for users, search engines, advertising and external links. Match the current path in HubSpot where practical. Do not change every slug to demonstrate that the site has moved.

Where a URL must change, map it to the closest relevant replacement. Avoid sending many unrelated pages to the homepage. If content has no replacement and no continuing value, a truthful not-found response can be better than a misleading redirect.

Google's current site move guidance recommends testing the new site, preparing a URL map, implementing redirects and monitoring old and new URLs. It also advises changing one major thing at a time where practical and warns that rankings may fluctuate during reprocessing.

HubSpot's current URL redirect documentation supports standard and flexible redirects, including CSV upload for bulk work, but notes that its redirects work only for domains connected to and hosted in HubSpot. If the old request still reaches another host, CDN or platform, configure the redirect there.

Test the complete old URL, not only the rule inside HubSpot. Check status, destination, chains, query strings and regional variants. Retain a versioned copy of the approved map.

Rebuild SEO Signals Deliberately

Do not rely on a generic SEO-friendly setting. Check each important HubSpot template and representative page for:

• a unique, descriptive title;
• a useful meta description;
• one clear main heading;
• an absolute canonical URL;
• appropriate robots directives;
• accurate language and alternate annotations where used;
• meaningful image alternative text;
• crawlable navigation and internal links;
• valid structured data that reflects visible content;
• a correct sitemap entry;
• a genuine status code.

Compare the visible and rendered content with the existing page. Migration is a common time to lose FAQs, evidence, author information, tables, captions or specialist explanations because the new component set does not support them. Make a deliberate editorial decision instead of silently shortening the page.

If the site is also being redesigned, use a website redesign service that includes migration acceptance checks. Visual approval alone does not prove that search signals survived.

Design the HubSpot Content Model for Editors

A safe migration is not only about matching the old front-end. Content Hub should give the team clear templates, modules, global content and permissions without letting every page drift apart.

Define:

• page and article types;
• required and optional fields;
• reusable sections and module settings;
• global header, footer and calls to action;
• campaign landing-page rules;
• author, category and topic structures;
• image dimensions and alt-text responsibilities;
• preview and approval steps;
• roles for marketers, editors, developers and administrators;
• archive and deletion processes.

Create representative content, not only an ideal short page. Test a long title, detailed service copy, several authors, large resource library and unusual image proportions. Confirm editors can update content without changing technical SEO fields accidentally.

Inventory Every Form Before Rebuilding It

List every form, not only those visible in main navigation. Include downloads, event registrations, newsletter forms, contact forms, demo requests, meeting routes and forms embedded on external pages.

For each one, document:

HubSpot's current forms documentation explains that forms can create or update CRM records and trigger follow-up actions. That makes property mapping and workflow testing as important as visual styling.

Keep a copy of historical submissions and field definitions according to the organisation's retention and data-protection decisions. Do not assume rebuilding a form migrates its history or recreates every automation.

Test Forms as Data Flows, Not Just Interfaces

Use test contacts that are clearly labelled and safe to delete according to the organisation's process. Test valid, invalid and duplicate submissions, plus different consent choices and traffic sources.

Verify:

1. The visitor sees accurate validation and confirmation.
2. One correct CRM record is created or updated.
3. Every field maps to the intended property.
4. consent information is recorded as designed.
5. Ownership, lists, workflows and notifications run once.
6. Email delivery and suppression rules behave correctly.
7. Source and campaign information is available.
8. Connected systems receive only the expected data.

Test mobile and keyboard use. Check spam protection and error handling. Submit forms from the production-like domain because previews can behave differently around cookies, embeds or allowed origins.

Where some pages remain outside HubSpot, its guide to installing the HubSpot tracking code explains that external pages need the code to capture site analytics and some non-HubSpot form activity. It also warns not to install multiple HubSpot tracking codes on one page. Document which environment owns the installation.

Create One Tracking and Attribution Plan

HubSpot, Google Analytics and advertising platforms answer different questions. Decide which system is authoritative for leads, customers, sessions, campaign cost and revenue. Document expected differences rather than trying to force all tools to show identical numbers.

The plan should list:

• page views and key content events;
• form starts and submissions;
• calls, emails, meetings and downloads;
• campaign parameters and original source rules;
• consent requirements;
• cross-domain or subdomain journeys;
• internal and agency traffic exclusions;
• advertising conversion events;
• CRM lifecycle and revenue stages;
• reporting owners and quality checks.

If both old and new tracking run during testing, prevent duplicate live events and clearly separate staging data. Confirm tags do not fire before the relevant consent state. Check the receiving reports and CRM, not just a browser console.

An analytics and reporting service should reconcile test actions with stored records and describe any expected attribution limitations.

Map Workflows and Integrations

Forms often trigger workflows that assign owners, send emails, create tasks, update lifecycle stages or sync another system. Inventory each dependency before changing forms or properties.

For every workflow, record the enrolment trigger, exclusions, re-enrolment rules, delays, actions, owner and failure route. Use a small set of controlled test contacts to check branches. Prevent a migration test from sending an internal alert to the whole sales team or a customer-facing email to real contacts.

Review API integrations, native apps, webhooks, imports and custom code separately. Confirm permissions and rate limits against current vendor documentation. A marketing automation review should include failure handling and human ownership, not only a diagram of the happy path.

Protect Domains, Email and Existing Campaigns

Domain connection work affects more than a website. Inventory root, www, blog, landing-page and tracking subdomains. Identify where DNS is managed and who can approve changes. Do not remove unrelated email records while changing website records.

List current paid ads, social profiles, directory listings, QR codes, email templates and sales documents that point to old pages. Update high-volume destinations after redirects are active. Keep redirects available for old links that cannot reasonably be changed.

If campaign landing pages remain on a separate HubSpot subdomain while the main website moves, test cross-domain attribution and customer expectations. A technically valid journey can still feel untrustworthy if branding or domains change without explanation.

Run a Structured Pre-Launch Review

Use a protected preview or staging setup without letting it compete in search. Test representative pages and every critical journey on supported browsers and real mobile devices.

The release checklist should cover:

• approved content and media;
• titles, canonicals, robots and structured data;
• URL redirects and not-found responses;
• navigation, search and internal links;
• forms, workflows and CRM records;
• analytics, consent and advertising events;
• accessibility and performance;
• integrations and error handling;
• DNS changes and certificates;
• backups, exports and rollback decisions;
• support contacts and launch authority.

Freeze unrelated changes before launch. Record exactly which content and configuration version was approved. If a serious issue appears, the team should know who can roll back and what data may have changed since release.

Monitor the Migration After Launch

Check the live system immediately, again after caches and DNS have settled, and repeatedly over the following weeks. Monitor technical and commercial evidence:

• old and new URL responses;
• crawl and indexing reports;
• sitemap processing;
• organic landing pages and queries;
• 404 and server errors;
• form submissions and CRM creation;
• workflow failures and email delivery;
• attribution and advertising events;
• page performance and accessibility faults;
• qualified enquiries, not only sessions.

Annotate reporting with the migration date and other campaign changes. A fall in leads can be a form-routing problem even when traffic is stable. A traffic change can be seasonal rather than technical. Our guide to website traffic without enquiries helps separate acquisition from conversion problems.

Frequently Asked Questions

Will moving to HubSpot Content Hub hurt SEO?

It can if valuable URLs, content, internal links, metadata, canonicals, rendering or redirects are changed carelessly. A controlled migration can preserve these signals, but no supplier can guarantee unchanged rankings.

Can I keep the same URLs when migrating to HubSpot?

Often yes, and preserving useful established paths usually reduces unnecessary change. Where HubSpot or the new structure requires a different URL, map and test a relevant permanent redirect.

Do HubSpot forms automatically keep my old form history?

No. Rebuilding or embedding a form does not by itself migrate every historic submission, field mapping, consent record, workflow or integration. Export, map and retain data according to the agreed business and privacy requirements.

How do I preserve tracking during a HubSpot migration?

Inventory every current tag, pixel, event and domain; define the future measurement plan; avoid duplicate installations; test consent states and real journeys; then verify the data in HubSpot, analytics and advertising platforms.

How long should a HubSpot migration be monitored?

Check critical functions immediately and monitor technical, search and commercial evidence for several weeks. Larger sites, complex integrations and significant URL changes may require a longer observation period.

What Success Looks Like After Migration

The strongest migration plan follows each important journey from search result or campaign through page, form, CRM record, workflow and business response. If any connection is missing, the new site is not ready simply because its pages look complete.

If you need an independent migration scope or launch review, contact MattDarm with the current domain, platform, HubSpot subscription and the systems that must remain connected.