Data Migration from HubSpot Service Hub
Last updated: August 14, 2026
This guide will help you migrate your data from HubSpot Service Hub to Pylon. Talk to your AE about a data migration to make sure that we cover what you are looking for.
This migration will bring over the tickets in a closed state, meaning neither you or the customer can reply on these tickets from Pylon.
For the overall process, see 📄 Migrating your Data to Pylon
Self-service option: If you do not want to use Pylon’s guided migration service, you can export HubSpot tickets and import them with Pylon’s import API endpoints instead.
Guided Migration Service: Pylon offers a one-time HubSpot ticket migration service performed by the Solutions team for a one-time fee. Pricing starts at $1,000 depending on the number of tickets being migrated. Talk to your AE about this option to make sure we cover what you are looking for.
What we'll need from you
To get started with your migration, we’ll need the following:
Admin access to your HubSpot account
Your users should already be invited to Pylon
An idea on what you want to bring over, we recommend only bringing over custom fields that you are going to use going forward.
Definitions for which ticket pipelines or inboxes you want to migrate
Supported Fields
HubSpot Service Hub | Pylon |
Help desk | |
Users | Users |
Companies | Accounts |
Contacts | Contacts |
Ticket | Issues |
Conversations | Issues |
Knowledge Base | |
Categories | Collections |
Subcategories | Sub-collections |
Articles | Articles |
Knowledge Base Limitations
Some objects don't migrate with our migrator tool due to HubSpot's API limitations
Unpublished articles (drafts)
Private docs (they need to be public-facing)