Drupal to HubSpot
Open-source PHP CMS for structured content, multilingual and editorial sites. It is often self-hosted or run on a managed host.
Drupal data can move into HubSpot, landing mainly in Content Hub. 1 of 8 mapped objects move directly (Article / blog nodes); 5 items need manual work and 3 do not move. Plan roughly 4-8 weeks for a small move and 16-30 weeks for a large one.
Migration checklist for Drupal
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 6 doneAfter
0 of 6 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
Up to ~200 pages/posts
Blog import plus a template rebuild.
Mid migration
~200-2,000 pages/posts
Custom types, redirects and some multilingual work.
Large migration
2,000+ nodes
Multisite or multilingual, with heavy structured content and custom modules.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Drupal: what you need to get in, what lands in HubSpot, and what will not.
REST (JSON:API core module, plus core REST)
A Drupal user with permission to view the content. The JSON:API module must be enabled.
Admin is needed to enable modules and to create Views exports. Read access is enough for published content over the API.
Choose your route
How will you move the data?
No native connector was found.
- You need: A Drupal user with permission to view the content. The JSON:API module must be enabled.
- Permission: Admin is needed to enable modules and to create Views exports. Read access is enough for published content over the API.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- JSON:API collections at /jsonapi/node/{type}
- Core REST with ?_format=json, one entity at a time
- Views Data Export contrib module for XML/CSV
- Migrate API (Migrate Plus/Tools) for custom pipelines
- Crawl-based HubSpot smart copy of the public blog
- Database dump and file-system copy of public files
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 16-30 weeks, usually phased.
Talk to a partnerWhere each object lands
In Drupal
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Article / blog nodes | Blog posts (Content Hub) | yes | The importer takes title, body, URL, date, author, tags and meta description. Use smart copy or an XML file in WordPress format. |
| Basic page / landing nodes | Website/landing pages (Content Hub) | manual | No page importer was found. Pages are rebuilt on HubSpot templates and modules, or created through the CMS API. |
| Custom content types / Paragraphs | HubDB / Custom objects / dynamic pages | partial | Agencies map these to dynamic pages or custom objects. The mapping is custom work. |
| Media / files | Files | partial | Inline blog images import with posts. PDFs linked in posts are not included in an XML import. |
| Taxonomy terms | Blog tags / topics | partial | Tags and categories import with posts. Vocabularies beyond that need manual mapping. |
| URL aliases / redirects | URL redirects | manual | Build a redirect map from the old paths and load it in bulk. |
| Webforms / contact forms | Forms | manual | Rebuild as HubSpot forms. Submission data would need a separate export to Contacts. |
| Users / CRM contacts | Contacts | partial | Users are readable via JSON:API. Whether to import them as Contacts is a scoping decision. |
What to expect
They must be rebuilt as HubSpot templates and modules (HubL).
There is no equivalent import. It is recreated with HubSpot features or an integration.
JSON:API does not export Views results.
Layouts do not transfer.
URL structure changes on move.
Webforms do not map directly.
Drupal translations must be rebuilt as HubSpot language variants.
New templates need their own checks.
Crawl the old site and test redirects before launch.
Use JSON:API or Views XML export, then smart copy or the HubSpot API.
Convert them to absolute URLs before import.
Design modules and HubDB structures first.
Use Views export or the Migrate API on older versions.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Drupal's JSON:API export and HubSpot's blog importer are backed by docs. The page, template, form and redirect mapping rests on agency guides and category-level knowledge. No native Drupal-to-HubSpot connector was found.
Sources
Related migrations
Frequently asked questions
How do I migrate Drupal to HubSpot?
1. Inventory content types, vocabularies, Paragraphs, Views and webforms. 2. Confirm the Drupal version and whether core JSON:API is available to enable. 3. Export the URL alias list and a full crawl of the live site. 4. Decide which nodes become blog posts, pages, HubDB rows or are dropped.
What data can move from Drupal to HubSpot?
These objects move directly: Article / blog nodes. Check the mapping table for partial and manual items.
What does not move from Drupal to HubSpot?
Themes, Twig templates, Layout Builder layouts, Custom and contrib module functionality (Views, dynamic blocks) and Views results via JSON:API. Plan to rebuild or retire these.
How long does a Drupal to HubSpot migration take?
Small (Up to ~200 pages/posts): 4-8 weeks. Mid (~200-2,000 pages/posts): 8-16 weeks. Large (2,000+ nodes): 16-30 weeks. These are planning estimates, not a quote.
What access do I need to export from Drupal?
A Drupal user with permission to view the content. The JSON:API module must be enabled. Admin is needed to enable modules and to create Views exports. Read access is enough for published content over the API.
Is there a native HubSpot connector for Drupal?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Drupal data?
Check: Check webforms for health, financial or minors' data. and Check member-only or gated content.. Agree consent, retention and access rules before exporting.
Moving Drupal into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner