HubSpot Blog to WordPress Migration: Authors, Tags, Images and Redirects
Move your HubSpot blog archive with authors, dates, tags, images and redirects mapped. Test representative posts before committing to the complete migration.
In this article
Editorial illustration. Any screens and records are illustrative, not a delivered client system.
Moving a HubSpot blog to WordPress is not just copying the text into a different editor. Your archive has authors, dates, topic structures, images, internal links and older URLs that people may still use. Those details need a destination plan.
This guide focuses on the editorial archive. CRM contacts, email subscriptions and marketing workflows are separate decisions. A clear blog migration brief lets your editor, marketing owner and developer agree what should be preserved, rebuilt or retired before the bulk transfer begins.
Define which parts of HubSpot are moving
List the blogs and languages included, the approximate post count and any unpublished content that needs a separate handover. Decide whether WordPress will host only the archive or also the surrounding resource pages, search and subscription journey. Include the people responsible for editorial acceptance.
Keep the CMS move distinct from the CRM decision. A business can plan its website destination separately from the systems it uses for contacts and campaigns, but any retained connection needs an explicit scope. My HubSpot website and CRM migration guide explains those wider boundaries.
Do not treat a blog-only quote as approval to migrate every marketing asset or change how customer data is handled.
Inspect the export before promising an automatic import
HubSpot’s official content export guidance describes HTML exports for pages, posts and templates, alongside structured blog-post exports. Export permissions and the information provided depend on the content involved. An exported template is not a ready-made WordPress theme.
The WordPress import documentation describes import routes according to source format. Confirm the actual export, mapping and destination importer with a sample. Do not assume that a CSV or HTML directory will carry every editorial field into the right WordPress setting.
Choose representative posts before estimating transformation work: an ordinary article, a heavily formatted page, a post with embeds and one with unusual author or taxonomy details.
Use one content map for the whole archive
Create a record for each in-scope article. The map should connect its source identity to the intended WordPress result, so editors can review exceptions without searching through folders of exported files.
| Map field | Decision to record |
|---|---|
| Old URL and source reference | Which original article this row represents |
| New URL and publication status | The intended destination and whether it should be public |
| Author and dates | Approved attribution and the meaning of publication/modified dates |
| Topic labels | How existing tags map to WordPress categories or tags |
| Featured and inline images | Where each asset will live and which text describes it |
| Embedded forms and calls to action | Retain, rebuild, replace or remove with approval |
| Redirect result | Which old URL reaches which relevant destination |
Keep the original source reference even if the new slug changes. It makes sample reviews and later questions easier to resolve.
Preserve editorial context without reproducing obsolete markup
Agree how author names, biographies and dates should appear in the new shared post template. Preserve a genuine original publication date where appropriate, rather than making an old archive look newly written. A later migration date is not evidence that the article’s content was substantively updated.
Review topic structures with the editorial owner. Mapping several near-identical tags to one destination may be sensible, but it is a content decision that should be documented. Similarly, old spacing tricks and embedded styling do not need to be reproduced when native editable WordPress or Elementor content can express the article clearly.
Separate faithful content transfer from an editorial rewrite. If obsolete advice needs updating, identify that as approved content work with its own review responsibility.
Move images and embedded actions deliberately
List featured images, inline illustrations, captions, download links, video embeds and subscription forms. Decide who owns each asset and whether the WordPress site may use it. A visible image in an exported article is not proof that the destination has a durable local media reference.
Check a sample image at the intended desktop and mobile sizes, with appropriate alternative text and no unexpected dependence on an old host. Retained external assets should have a named owner and an understood availability risk.
For an embedded HubSpot form or campaign action, agree whether it remains, is rebuilt or is replaced. Confirm the destination and the required consent or contact-preference behaviour with the business owner. A content migration should not quietly change those rules.
Plan redirects and internal links as a reviewable set
Use the approved URL map to preserve meaningful destinations. Where an old article still has a valid equivalent, point visitors toward that equivalent rather than sending every removed URL to the homepage. A redirect is a forwarding instruction, not a substitute for deciding where content belongs.
Review links inside the transferred articles as well as incoming old URLs. Check links to other posts, category pages, files and campaign destinations. Keep a list of intentionally retired content and the reason, so a missing page can be distinguished from an accidental omission.
Scope crawl and redirect checks in the HubSpot to WordPress migration proposal. No migration process can guarantee unchanged search rankings, but explicit URL decisions make the release easier to verify and investigate.
Agree what the sample migration must demonstrate
Have an editor check content and attribution while a technical reviewer checks status, URLs, media and shared templates. Compare the approved record count with the published destination set, and document drafts, exclusions and failures separately.
- The correct author, meaningful dates and agreed topic labels appear.
- Headings, lists, tables and embeds remain readable and editable.
- Featured and inline images load without relying on unintended old URLs.
- Old URLs and internal links reach the approved destinations.
- Any retained form or subscription action has an agreed verification result.
- The archive can be browsed on mobile, including search or pagination where in scope.
Use a sign-off list with an owner for each unresolved item. A sample approved in isolation does not remove the need to reconcile the full in-scope archive.
Bring an archive brief to the first conversation
Share the existing blog URL, post count, languages, intended WordPress address and your preferred treatment of authors, dates and topic labels. Mention embedded forms, downloads, subscription journeys and any articles already scheduled for retirement. Keep CRM exports and personal contact data out of an initial blog enquiry.
I can scope a HubSpot blog migration to WordPress around that inventory, a representative sample and an agreed launch map. You receive a clearer division between content transfer, editable templates, retained integrations and editorial changes before committing to the larger move.
Written by
Jagjeet Singh
Full stack development, WordPress engineering and practical web products. I work with businesses, teams and agencies in India and worldwide.
Explore my work
