Choose a time that minimizes disruption for your team. Be sure to communicate the schedule in advance, decide if your current system will stay active during the data migration, and prepare your Zendesk® environment, including custom fields, macros, and settings, before your HubSpot import.

Migration time depends on your dataset size, attachments, and internet speed. Smaller datasets with a few hundred tickets can migrate in minutes. Larger imports, like tens of thousands of tickets with attachments, may take several hours.

Running a Demo migration is the best way to get an accurate time estimate for your data import project.

All data is encrypted during transfer, and your API credentials are never stored. HubSpot to Zendesk® data migration process fully complies with privacy regulations like GDPR, CCPA, HIPAA, SOC 2 Type II, and SOC 3 compliance, so your customer data stays safe and private.

You can migrate from HubSpot Service Hub Free, Starter, Professional, and Enterprise plans. On the Zendesk® side, the Support Suite and related plans are supported.

We recommend checking your specific Zendesk® edition to see if any workflow-related limitations apply.

Yes, always make a backup. Export and save your HubSpot data before migration. It acts as a safety net in case you ever need to recover information manually.

Yes, but it’s best to start with a Demo migration. This lets you check that ticket fields, mappings, and attachments are transferred correctly before importing the HubSpot data.

You can choose to move newer tickets or records first, giving your team access to the most relevant data right away.

All associations remain intact, so you keep full context and history in Zendesk® after the HubSpot import.

A few Zendesk-specific behaviors can affect migration results:

• Suspended contacts in HubSpot may change status when imported.
• Tickets without contacts, organizations, or agents can’t be migrated.
• After a period (4 days without replies or updates), statuses like Solved may automatically switch to Closed or become archived.
• Some ticket statuses may not be visible in the main view, so you need to use search to locate them.
• Only the default language is migrated for Help Center content. An additional automated option lets you migrate all language versions of your Help Center content.
• Agent roles and limits depend on your Zendesk® plan.
• Knowledge base articles can be imported to folders rather than categories, and inline images or side conversations may need some extra setup.

Some HubSpot-specific limitations to keep in mind when moving your data with Help Desk Migration:

• Groups created in HubSpot aren’t supported for data migration.
• Inline images in tickets or knowledge base articles aren’t migrated automatically.
• Knowledge base articles may require a separate import to ensure structure and formatting are preserved.
• CC fields in tickets aren’t included in the migration.
• Conversations that exist outside standard ticket threads (for example, in the inbox) aren’t transferred.
• The ticket creation date may appear as the migration date unless a custom “created at” field is set up.
• Tags are not migrated, and attachments may not display unless handled explicitly during setup.

Once the Full Migration starts, any new or updated records in your HubSpot won’t move automatically (unless you schedule a Delta migration). Also, avoid making changes during this process because it may suspend the migration. As the data migration runs in the cloud, you can safely close your browser while it completes.

Our dedicated migration support team is available to guide you through every step of the HubSpot import process.

We help with troubleshooting field mappings, attachments, knowledge base migration, and any exceptions that may occur.

Yes. For large datasets, a phased migration approach is available to reduce risk and ensure a smooth transfer.