How to Migrate Customer Support Tickets & Data to HubSpot Service Hub

Start by defining the exact support data you want to bring over. In most migrations, that includes tickets, ticket properties, internal notes, customer replies, conversation history, attachments, and the contact and company records tied to each ticket. If a field helps the team route, solve, or report on the ticket, it belongs on the migration list.

The key is to move more than the headline fields. A support ticket is only useful when the team can still see who raised it, what happened, who handled it, and how it was resolved. If that context is missing, the record may exist in HubSpot, but it will not be very useful.

A good migration scope usually includes:

• Ticket subject.
• Ticket description.
• Status.
• Priority.
• Owner.
• Created date.
• Closed date.
• Internal notes.
• Customer replies.
• Attachments.
• Contact associations.
• Company associations.
• Custom support fields.

Before you move anything, review the source support system and confirm what can actually be exported. Some systems make it easy to export ticket records but harder to preserve history, attachments, or relationship data. (Source: Manage tickets in help desk - HubSpot Knowledge Base)

At this stage, decide three things:

• Which tickets are in scope.
• Which historical details must be preserved.
• Which records can be simplified or left out.

This is also the right time to prepare HubSpot itself. Create the properties you will need, set up the ticket pipeline, and make sure your team has agreed on status names, ownership rules, and the way tickets should be organized once they arrive.

If you skip this step, the import may still work, but the data will not be easy to use after the move. A clean plan here saves a lot of cleanup later. For source-system review and scope planning, see Pre-Migration CRM Audit.

Field mapping is where most migrations succeed or fail. Every source field should have a clear destination in HubSpot, and that mapping should be agreed on before the first import starts.

A few common examples:

• Source ticket ID to original ticket ID custom property.
• Subject to ticket subject.
• Description to ticket details.
• Priority to priority field.
• Status to pipeline stage.
• Created date to created timestamp.
• Closed date to closed timestamp.

HubSpot’s ticket object supports properties and associations, so you can structure ticket data in a way that still makes sense after migration. That is why the field map should not be treated as a rough guide. It should be a working document that tells you exactly how each record will land. (Source: CRM API | Tickets)

If you have custom fields in the source system, map only the ones that matter. It is better to import fewer fields cleanly than to import every field badly. For the broader mapping approach, see CRM Data Mapping.

Tickets are much more valuable when they stay connected to the right contact and company. HubSpot supports associations on ticket records, so those links should be part of the migration plan from the start.

The safest sequence is usually:

• Import or match contacts first.
• Import or match companies second.
• Import tickets last.
• Attach each ticket to the correct records using a stable identifier.

Email is often the simplest contact match field. Company domain is often the simplest company match field. If your source data does not match cleanly, define a fallback rule before you import.

For tickets that involve multiple people, decide who should be treated as the primary contact. For tickets with no clear match, flag them instead of forcing a bad association. A wrong association is often worse than no association at all. If you want to preserve data relationships cleanly, review Preserve CRM Data Integrity During a HubSpot Migration.

Field mapping is where most migrations succeed or fail. Every source field should have a clear destination in HubSpot, and that mapping should be agreed on before the first import starts.

A few common examples:

• Source ticket ID to original ticket ID custom property.
• Subject to ticket subject.
• Description to ticket details.
• Priority to priority field.
• Status to pipeline stage.
• Created date to created timestamp.
• Closed date to closed timestamp.

HubSpot’s ticket object supports properties and associations, so you can structure ticket data in a way that still makes sense after migration. That is why the field map should not be treated as a rough guide. It should be a working document that tells you exactly how each record will land. (Source: CRM API | Tickets)

If you have custom fields in the source system, map only the ones that matter. It is better to import fewer fields cleanly than to import every field badly. For the broader mapping approach, see CRM Data Mapping.

Field mapping is where most migrations succeed or fail. Every source field should have a clear destination in HubSpot, and that mapping should be agreed on before the first import starts.

A few common examples:

• Source ticket ID to original ticket ID custom property.
• Subject to ticket subject.
• Description to ticket details.
• Priority to priority field.
• Status to pipeline stage.
• Created date to created timestamp.
• Closed date to closed timestamp.

HubSpot’s ticket object supports properties and associations, so you can structure ticket data in a way that still makes sense after migration. That is why the field map should not be treated as a rough guide. It should be a working document that tells you exactly how each record will land. (Source: CRM API | Tickets)

If you have custom fields in the source system, map only the ones that matter. It is better to import fewer fields cleanly than to import every field badly. For the broader mapping approach, see CRM Data Mapping.

Tickets are much more valuable when they stay connected to the right contact and company. HubSpot supports associations on ticket records, so those links should be part of the migration plan from the start.

The safest sequence is usually:

• Import or match contacts first.
• Import or match companies second.
• Import tickets last.
• Attach each ticket to the correct records using a stable identifier.

Email is often the simplest contact match field. Company domain is often the simplest company match field. If your source data does not match cleanly, define a fallback rule before you import.

For tickets that involve multiple people, decide who should be treated as the primary contact. For tickets with no clear match, flag them instead of forcing a bad association. A wrong association is often worse than no association at all. If you want to preserve data relationships cleanly, review Preserve CRM Data Integrity During a HubSpot Migration.

Field mapping is where most migrations succeed or fail. Every source field should have a clear destination in HubSpot, and that mapping should be agreed on before the first import starts.

A few common examples:

• Source ticket ID to original ticket ID custom property.
• Subject to ticket subject.
• Description to ticket details.
• Priority to priority field.
• Status to pipeline stage.
• Created date to created timestamp.
• Closed date to closed timestamp.

HubSpot’s ticket object supports properties and associations, so you can structure ticket data in a way that still makes sense after migration. That is why the field map should not be treated as a rough guide. It should be a working document that tells you exactly how each record will land. (Source: CRM API | Tickets)

If you have custom fields in the source system, map only the ones that matter. It is better to import fewer fields cleanly than to import every field badly. For the broader mapping approach, see CRM Data Mapping.

Field mapping is where most migrations succeed or fail. Every source field should have a clear destination in HubSpot, and that mapping should be agreed on before the first import starts.

A few common examples:

• Source ticket ID to original ticket ID custom property.
• Subject to ticket subject.
• Description to ticket details.
• Priority to priority field.
• Status to pipeline stage.
• Created date to created timestamp.
• Closed date to closed timestamp.

HubSpot’s ticket object supports properties and associations, so you can structure ticket data in a way that still makes sense after migration. That is why the field map should not be treated as a rough guide. It should be a working document that tells you exactly how each record will land. (Source: CRM API | Tickets)

If you have custom fields in the source system, map only the ones that matter. It is better to import fewer fields cleanly than to import every field badly. For the broader mapping approach, see CRM Data Mapping.

Field mapping is where most migrations succeed or fail. Every source field should have a clear destination in HubSpot, and that mapping should be agreed on before the first import starts.

A few common examples:

• Source ticket ID to original ticket ID custom property.
• Subject to ticket subject.
• Description to ticket details.
• Priority to priority field.
• Status to pipeline stage.
• Created date to created timestamp.
• Closed date to closed timestamp.

HubSpot’s ticket object supports properties and associations, so you can structure ticket data in a way that still makes sense after migration. That is why the field map should not be treated as a rough guide. It should be a working document that tells you exactly how each record will land. (Source: CRM API | Tickets)

If you have custom fields in the source system, map only the ones that matter. It is better to import fewer fields cleanly than to import every field badly. For the broader mapping approach, see CRM Data Mapping.

Tickets are much more valuable when they stay connected to the right contact and company. HubSpot supports associations on ticket records, so those links should be part of the migration plan from the start.

The safest sequence is usually:

• Import or match contacts first.
• Import or match companies second.
• Import tickets last.
• Attach each ticket to the correct records using a stable identifier.

Email is often the simplest contact match field. Company domain is often the simplest company match field. If your source data does not match cleanly, define a fallback rule before you import.

For tickets that involve multiple people, decide who should be treated as the primary contact. For tickets with no clear match, flag them instead of forcing a bad association. A wrong association is often worse than no association at all. If you want to preserve data relationships cleanly, review Preserve CRM Data Integrity During a HubSpot Migration.

Tickets are much more valuable when they stay connected to the right contact and company. HubSpot supports associations on ticket records, so those links should be part of the migration plan from the start.

The safest sequence is usually:

• Import or match contacts first.
• Import or match companies second.
• Import tickets last.
• Attach each ticket to the correct records using a stable identifier.

Email is often the simplest contact match field. Company domain is often the simplest company match field. If your source data does not match cleanly, define a fallback rule before you import.

For tickets that involve multiple people, decide who should be treated as the primary contact. For tickets with no clear match, flag them instead of forcing a bad association. A wrong association is often worse than no association at all. If you want to preserve data relationships cleanly, review Preserve CRM Data Integrity During a HubSpot Migration.

Tickets are much more valuable when they stay connected to the right contact and company. HubSpot supports associations on ticket records, so those links should be part of the migration plan from the start.

The safest sequence is usually:

• Import or match contacts first.
• Import or match companies second.
• Import tickets last.
• Attach each ticket to the correct records using a stable identifier.

Email is often the simplest contact match field. Company domain is often the simplest company match field. If your source data does not match cleanly, define a fallback rule before you import.

For tickets that involve multiple people, decide who should be treated as the primary contact. For tickets with no clear match, flag them instead of forcing a bad association. A wrong association is often worse than no association at all. If you want to preserve data relationships cleanly, review Preserve CRM Data Integrity During a HubSpot Migration.