HubSpot Ticket Import template.

What's inside — the exact file

This is the complete template, not a sample. The rows are worked examples — replace them with your data (and delete them before any platform import).

What this template is for

This file is the starting layout for importing service tickets into HubSpot — moving a support history in from another tool, or bulk-creating tickets from a backlog that lived in a spreadsheet or shared inbox. Unlike Zendesk, HubSpot does import tickets from CSV natively: the import wizard treats tickets as a first-class object and will associate each row to contacts and companies during the same import.

The columns here map to the ticket properties HubSpot’s import flow expects as of October 2026, plus the two association columns (contact email, company domain) that connect each ticket to the right CRM records. Keep one ticket per row.

How to use it, step by step

1. Confirm your pipelines and statuses first. The Pipeline and Ticket Status values in your file must match what exists in HubSpot exactly. Create pipelines and stages in settings before the import, not during cleanup after it.
2. Stage your data under these headers. Ticket name, pipeline, and status are the essentials; the import wizard maps any header to any property, but matching names means zero manual mapping.
3. Use emails and domains for associations. The Associated Contact Email and Associated Company Domain columns link each ticket to existing CRM records. Contacts that don’t exist yet can be created in the same import from a second file.
4. Format dates plainly. Use an unambiguous date format (YYYY-MM-DD) in Create Date so historical tickets keep their real timeline in reporting.
5. Run the import with a test batch. Import 10 rows, open a few tickets, and check pipeline placement, status, owner assignment, and the contact/company associations before loading the full history.
6. Spot-check reporting. After the full import, check the service dashboard — if every ticket shows as created today, the Create Date column didn’t map.

What each column means

Common mistakes to avoid

• Status values that don’t exactly match pipeline stage names — the rows fail or pile into the default stage.
• Importing tickets before the contacts exist and skipping the association step, leaving orphaned tickets with no customer.
• Letting Create Date default to the import day, which collapses years of support history into one spike.
• Ambiguous date formats (3/4/26) that import as the wrong month depending on account settings.
• Importing an open backlog into a brand-new pipeline nobody has agreed to work — migrate history as closed, triage the live queue separately.

Questions, answered

Does HubSpot really import tickets from CSV natively?

Yes — tickets are an importable object in HubSpot’s import wizard, unlike some help desks where ticket history requires API work. These columns follow the documented ticket import flow as of October 2026; validate against HubSpot’s current import docs before a large load.

Which Service Hub tier do I need?

Ticket pipelines and imports work on every tier including free; what changes with paid tiers is automation, SLAs, routing, and reporting depth. The import itself is not gated.

Can one import create tickets and contacts together?

Yes — choose a multi-file import (one file of tickets, one of contacts) and HubSpot associates them by email during the same run. For most migrations, importing contacts first is simpler to verify.

This is a Market Disrupt worksheet, not a vendor file. Import-format templates follow each platform's documented layout as of July 2026 — platforms evolve, so validate against current documentation before a large import.