URL mapping worksheet
Record old and new URLs, keep/redirect/remove decisions, expected status codes and QA results.
Download URL map (CSV)Migration checklist
WordPress to HubSpot Migration Checklist
Use this checklist before moving a WordPress website to HubSpot so pages, blog content, redirects, forms, tracking, and SEO checks are not discovered too late.
Free migration templates
Download the URL map and launch checklist
Open these CSV files in Excel or Google Sheets. Replace the illustrative example.com rows with your own URLs, assign owners and record test evidence. No email address is required. These are planning worksheets, not redirect files to import into your CMS.
Launch QA checklist
Track pre-launch, launch-day and post-launch checks with acceptance criteria, owners and evidence.
Download checklist (CSV)Inventory
1. Capture the WordPress site before rebuilding it
Pages and templates
List core pages, landing pages, legal pages, reusable sections, custom templates, page builder layouts, and any pages that should be consolidated or retired.
Blog and media
Count posts, authors, categories, tags, featured images, downloads, embedded media, and blog templates that need to exist in HubSpot.
Plugins and dependencies
Document form plugins, SEO plugins, caching, popups, tracking scripts, shortcodes, custom post types, and any functionality that HubSpot must replace.
SEO and redirects
2. Map URLs before anything changes
Export current signals
- Indexable WordPress URLs
- Titles, descriptions, canonicals, and H1s
- Top organic landing pages
- Internal links and sitemap URLs
Plan the HubSpot destination
- URLs that stay unchanged
- Changed URLs that need one-to-one redirects
- Old posts or pages that should merge
- Redirects for removed category or tag URLs
Launch readiness
3. Test the HubSpot version like a real migration
Before launch
Review responsive templates, forms, thank-you pages, metadata, internal links, sitemap output, robots rules, analytics, and conversion paths.
At launch
Publish with redirects ready, test priority URLs, confirm HTTPS and canonicals, submit the sitemap, and inspect representative pages in Search Console.
After launch
Watch 404s, redirect chains, form submissions, indexed pages, organic landing pages, and any query or page that drops unexpectedly.
WordPress-specific checks
4. Create a migration worksheet with testable outcomes
For every source URL, record the content type, destination URL, owner, migration method, redirect requirement and QA status. Prioritize pages with organic traffic, backlinks or form submissions. Keep an export of the original site so you can compare the result.
Permalinks and archives
Record the actual permalink structure, including date prefixes and trailing slashes. Decide whether author, category and tag archives still serve a purpose. Do not send every removed archive to the homepage; choose an equivalent destination or document an intentional removal.
Blog import sample
Test posts containing featured images, galleries, embeds, tables and downloads before importing the full blog. Verify authors, dates, image URLs and internal links against the originals. Review the WordPress blog migration guide for blog-specific scope.
Plugin replacement
Assign a replacement or a retirement decision to each plugin feature. Check shortcodes, custom post types, page-builder blocks, search, popups and forms. An exported post may contain shortcode text rather than the rendered component.
Example URL mapping
If /2024/05/example-post/ moves to /blog/example-post/, record both full URLs and create a permanent redirect. Confirm the old URL redirects directly to the new page, the destination returns 200, its canonical points to itself and all internal links use the destination. Keep the original path when a change brings no clear benefit.
Launch sign-off
5. Agree on the launch gates and follow-up checks
Do not launch with unresolved blockers
- Important source URLs have no agreed destination.
- Forms fail or send submissions to the wrong destination.
- Production pages inherit staging noindex or access restrictions.
- Navigation, key downloads or images are broken.
- The domain, HTTPS or redirect configuration has not been tested.
Monitor after publication
- On launch day: crawl priority URLs and submit a real test form.
- In the first week: inspect representative URLs and investigate unexpected 404s.
- Over the following weeks: compare complete GSC periods by query and landing page.
- Log every fix, its owner and the date so changes can be traced.
- Separate tracking failures from search traffic changes.
For deeper permalink and canonical decisions, use the WordPress SEO migration guide. For checks shared by every CMS, use the HubSpot migration SEO checklist.
Next step
Turn the checklist into a migration scope
For the full implementation, use the WordPress to HubSpot migration service. For blog-specific planning, review how to migrate a WordPress blog to HubSpot.