A HubSpot website migration is a significant project involving moving a live website from a platform like WordPress, Webflow, or a custom CMS onto the HubSpot CMS Hub. It is more than a simple copy-and-paste task; it requires a structured plan to protect SEO rankings, maintain functionality, and ensure a seamless user experience. Without a clear process, businesses risk broken links, lost traffic, a negative impact on search engine rankings, and a chaotic launch that undermines the entire investment in HubSpot.
This guide provides that structured process. We will walk through the seven core phases of a successful migration, from the initial audit and discovery to post-launch monitoring and validation. This is the same framework HubStack uses for our clients to ensure no detail is overlooked during a HubSpot website migration. Whether you plan to handle the project in-house or are preparing to work with a specialist, this plan will provide the clarity and confidence needed to manage the transition effectively and avoid common pitfalls.
We will cover the technical setup required within your HubSpot portal, the critical URL mapping process to preserve search equity, a detailed quality assurance checklist to execute before launch, and the essential steps to take after you go live. You will learn how to manage redirects, migrate various content types, and validate the success of the project using real data. This structured approach demystifies the process and turns a potentially stressful project into a predictable series of manageable tasks.
Phase 1: Pre-Migration Technical & Content Audit
The first phase of any successful migration is a comprehensive audit of your existing website. This process involves creating a complete inventory of every digital asset that needs to be moved, preserved, or retired. You must document all URL structures, content types (website pages, landing pages, blog posts, resource articles), and underlying page templates. The goal is to build a master list that will serve as the foundation for the entire project, ensuring nothing gets left behind or forgotten during the transition.
Beyond content, a technical audit is essential. This means evaluating the current site's tech stack, including any plugins, custom scripts, or third-party integrations that are critical to business operations. Do you have forms that feed into a specific system? Are there custom calculators or interactive elements that need to be rebuilt? Identifying these components early prevents functionality gaps post-launch. A thorough HubSpot technical SEO audit should also be performed to benchmark current performance, identifying top-performing pages, high-value keywords, and existing backlink profiles that must be protected.
Finally, this phase is about data gathering. Use tools like Screaming Frog to crawl your entire site and export all URLs, meta titles, descriptions, and header tags. Use Google Analytics and Google Search Console to identify your most visited pages and the queries that drive traffic to them. This data is not just for inventory; it informs your strategy, helping you prioritize the migration of high-traffic pages and ensuring that your most valuable SEO assets are handled with the utmost care.
Phase 2: URL Mapping and Redirect Strategy
With a complete inventory of your old site's URLs, the next critical phase is creating a URL map. This document is a spreadsheet that explicitly connects every old URL to its corresponding new URL on the HubSpot CMS. This is arguably the most important step for preserving SEO value. Search engines have spent years indexing your old URLs; if they suddenly lead to 404 'Not Found' errors after the migration, your rankings will plummet. The URL map serves as the blueprint for the 301 redirects you will implement during launch.
A 301 redirect is a permanent redirect that tells search engines and browsers that a page has moved to a new location. It passes most of the link equity (or 'SEO juice') from the old URL to the new one. Your URL map must be meticulously accurate. For every single URL on your old site, you need a corresponding entry showing where it will live on HubSpot. In some cases, you may be able to maintain the exact URL structure. In others, such as moving from a subdomain blog to a subfolder structure (e.g., `blog.yourcompany.com` to `yourcompany.com/blog`), every single blog post URL will change and need a redirect.
This phase also includes a content strategy component. You may discover old, low-value, or irrelevant content that doesn't need to be migrated. In these cases, you should strategically decide whether to retire the page (and let it 404) or redirect it to a relevant, higher-level page like the homepage or a parent category page. Every decision should be documented in the URL map. Neglecting this step is a common and costly mistake that our team at HubStack takes great care to avoid.
| Current URL (Old Site) | New URL (HubSpot) | Redirect Type | Content Type | Notes |
|---|---|---|---|---|
| https://www.oldsite.com/about-us | https://www.newsite.com/about | 301 | Website Page | URL slug simplified. |
| https://blog.oldsite.com/my-first-post | https://www.newsite.com/blog/my-first-post | 301 | Blog Post | Migrating from subdomain to subfolder. |
| https://www.oldsite.com/services/old-service | https://www.newsite.com/services | 301 | Website Page | Retiring service page, redirecting to parent. |
| https://www.oldsite.com/contact.html | https://www.newsite.com/contact | 301 | Website Page | Removing .html extension. |
Phase 3: Preparing the HubSpot Portal and Templates
While the strategy and mapping are underway, parallel work must begin inside the HubSpot portal to prepare the destination. This starts with technical configuration. You need to connect your domain(s) to HubSpot within the settings, which involves adding CNAME records in your DNS provider. This step doesn't make the site live; it simply validates to HubSpot that you own the domain and are ready to host content on it. You will also configure your brand settings, including logos and default colors, which themes and templates will inherit.
Next is the theme and template setup. Your website's design needs to be built on the HubSpot CMS. This can be approached in two ways: using a pre-built theme from the HubSpot Marketplace or engaging in HubSpot theme customization for a bespoke design. A custom theme ensures a perfect match with your brand and specific functional requirements. Regardless of the choice, you must create or customize the core page templates identified in your audit: the homepage, standard website pages, landing pages, blog listing page, and blog post page.
This is also the time to set up global content, such as the website header, footer, and any other elements that appear across multiple pages. Building these as global modules in HubSpot means you can update them in one place, and the changes will apply everywhere. Properly structuring your templates and modules at this stage is crucial for a scalable and easy-to-manage website long after the migration is complete. It ensures that your marketing team can easily create new HubSpot landing pages and other content without needing developer assistance.
Phase 4: Content Migration Execution
With the HubSpot portal prepared and templates in place, the process of migrating the actual content begins. This is where the pages on your old site are recreated within HubSpot. This can be a manual or an automated process. Automated migration, using tools or scripts, can be fast for very large sites with thousands of similar pages. However, it often results in formatting errors, broken images, and messy HTML that requires extensive cleanup.
For this reason, a manual migration is often the preferred method for quality control, especially for high-value pages. This involves a content specialist copying text, uploading images, and rebuilding the page layout using the new HubSpot templates. While more time-consuming, this method ensures that each page is formatted correctly, is fully responsive, and adheres to brand guidelines. It also provides an opportunity to improve the content, update metadata, and optimize on-page elements as you go.
The migration process must be systematic. Using your content inventory spreadsheet, you work through the list of URLs, building each page on the staging domain provided by HubSpot. As each page is completed, you mark it as 'migrated' and note the new HubSpot staging URL. This includes migrating all SEO metadata (title tags, meta descriptions), image alt-text, and internal links. For a blog, this includes authors, tags, and publication dates. This meticulous work ensures that when you go live, the new site is a true and improved version of the old one.
Phase 5: Pre-Launch Quality Assurance (QA)
Before you can even consider changing your DNS records to go live, a rigorous quality assurance phase is non-negotiable. The entire migrated site, which exists on a HubSpot-provided staging domain, must be tested from top to bottom. The goal is to identify and fix every possible issue before it can affect a live user or a search engine crawler. This process should involve multiple stakeholders and follow a structured checklist.
The QA checklist must cover functionality, usability, and technical integrity. Every internal link on every page must be clicked to ensure it points to the correct destination and does not result in a 404 error. All forms must be submitted to confirm that they work, that the data flows into the HubSpot CRM correctly, and that thank-you pages or messages fire as expected. The site must be tested across multiple browsers (Chrome, Firefox, Safari) and devices (desktop, tablet, mobile) to verify responsive design and consistent user experience.
Technical checks are also critical. Ensure all tracking codes, such as the Google Analytics 4 tag or any advertising pixels, have been correctly installed via the HubSpot settings. Review the source code of key pages to verify that title tags and meta descriptions are correct. Use a tool to crawl the staging site to programmatically find broken links or images. Only when the site passes this comprehensive QA review is it ready for launch. Skipping or rushing this phase is the primary cause of post-launch emergencies.
Phase 6: The Go-Live Process
The go-live process is the technical cutover where you point your domain's traffic from the old website to the new one on HubSpot. While it is a significant step, a well-executed plan makes it a straightforward and low-stress event. The primary action is updating your DNS records with your domain registrar or DNS provider (like GoDaddy, Cloudflare, or Route 53). You will change the CNAME record for your 'www' subdomain to point to the unique CNAME value provided by HubSpot.
Timing is an important consideration. It is best practice to schedule the DNS change during a period of low website traffic, such as late at night or over a weekend. This minimizes potential disruption for the few users who might be on the site. Once the DNS record is updated, it begins to 'propagate' across the internet. This process can take anywhere from a few minutes to several hours, though it is typically fast. During this time, some users might see the old site while others see the new one.
Simultaneously with the DNS change, you must implement the 301 redirects defined in your URL map. In HubSpot, this is done using the URL Mappings tool. You can bulk upload your spreadsheet of old-to-new URLs to activate all redirects at once. This ensures that as soon as search engines and users start hitting the old URLs, they are immediately and seamlessly sent to the correct new page on your HubSpot-hosted site. Confirming a few key redirects are working immediately after the DNS change is a crucial first validation step.
Phase 7: Post-Launch Monitoring and Validation
The work is not finished once the site is live. The first few weeks after a migration are a critical monitoring period to validate success and catch any lingering issues. The most important tool for this is Google Search Console (GSC). You need to watch the 'Pages' (Indexing) report for any spike in 404 errors, which would indicate that some URLs were missed in the redirect map. Submitting your new XML sitemap directly in GSC can help accelerate Google's discovery and indexing of your new site structure.
Closely monitor your website analytics in HubSpot and Google Analytics. It is normal to see some turbulence in traffic for a week or two as search engines process the changes. However, you should watch for any sustained, significant drops in organic traffic, which could signal a problem with redirects or indexing. Compare traffic to top pages before and after the migration to ensure your most valuable assets have not lost visibility. A full post-launch crawl of the live site is also recommended to find any remaining broken internal links or redirect chains that need to be cleaned up.
This final phase is about confirming the project's success and ensuring a smooth transition for the long term. It involves technical validation, performance analysis, and proactive issue resolution. Managing this post-launch period diligently is what separates a good migration from a great one. It is a core part of the comprehensive HubSpot website migration service provided by HubStack, ensuring our clients' investments are protected from launch day forward.