> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Coming from HubSpot

> How to move HubSpot companies, contacts and deals into Soundcheck as clients, leads and gigs

Teams that sell in **HubSpot** run their shows in Soundcheck. A production company on Soundcheck keeps HubSpot as its CRM, and its deals arrive in Soundcheck as gigs. This guide shows how to bring your client list and deal pipeline across: export three lists from HubSpot, then import them through **Settings → Apps & data → Import & export**.

The move is file-based. Soundcheck reads the files you export; it does not sign in to your HubSpot account to copy records. If you plan to keep HubSpot for sales and run shows in Soundcheck, see [Keep HubSpot running](#keep-hubspot-running).

![Soundcheck mapping step for a HubSpot companies export, with Company name mapped to Client name and Record ID to External ID](https://mintcdn.com/soundchecklive/AWWPa-Own7U-SgWm/images/imports/coming-from-hubspot-mapping-light.png?fit=max\&auto=format\&n=AWWPa-Own7U-SgWm\&q=85\&s=392c5e22b7cdfe898387a0dacd1caad0)

A HubSpot companies export on the mapping step. Soundcheck suggests the field for each HubSpot column. Sample data, not a customer.

**Who can import:** the web page (**Settings → Apps & data → Import & export**) shows for organization **owners and admins**. The API and the MCP import tools accept anyone with the **Import and export data** permission (`imports.manage`): Owner, Admin and Gig Coordinator.

## Steps at a glance

1. In HubSpot, export **Companies**, **Contacts** and **Deals** as CSV or XLSX.
2. Add the columns Soundcheck needs to the Deals file: client email, event date, event type and location.
3. In Soundcheck, import **Clients** first, then **Leads**, then **Events** for deals that are booked shows.
4. Check the pipeline and a few gigs, then import the same files once more and expect **0 new** rows.

## What moves and what doesn't

| In HubSpot | Import target (UI label) | Notes |
| - | - | - |
| Companies | **Clients** | Matched by name. Keep **Record ID** as the External ID so a later import updates the same client |
| Contacts | Contact columns on **Clients** | One contact per client row: name, email, phone, title |
| Open deals | **Leads** | Needs client email, event date, event type, location and deal stage on every row |
| Won deals with a show date | **Events** | One gig per deal. The client links by name |
| Deal amount | **Budget** on Leads | A budget figure, not a quote or an invoice |
| Quotes, line items, invoices, payments | n/a | Do not import. Re-create a quote in Soundcheck when you need one |
| Emails, calls, notes, tasks, sequences | n/a | Activity history stays in HubSpot. Export it there if you need a record |
| Workflows, forms, lists | n/a | Rebuild intake with [lead intake](https://docs.soundchecklive.io/crm/leads/lead-intake.md) or [portal forms](https://docs.soundchecklive.io/features/gigs/documents/portal-forms.md) |

## Export from HubSpot

HubSpot exports each object from its own list page. Official help: [Export records](https://knowledge.hubspot.com/import-and-export/export-records).

1. Open **CRM → Companies**. Choose the view you want (for example, all companies), click **Export**, pick **CSV** or **XLSX**, and include all properties.
2. Repeat on **CRM → Contacts**. Include the associated company so each contact row names its company.
3. Repeat on **CRM → Deals**. Include the associated company and contact, and every custom property that holds an event date, event type or location.
4. HubSpot emails a download link or downloads the file. Save the three files in one folder.

HubSpot limits who can export. If **Export** is missing, ask a HubSpot super admin for the export permission.

> [!TIP]
>
> Export deals from a filtered view, not the whole pipeline. Old lost deals add rows you then have to review. A date range or a set of stages keeps the file to work that still matters.

## Prepare the files

### Clients (Companies and Contacts)

The **Clients** target holds one client with one contact per row. The simplest file is the Companies export with the main contact's columns added.

| HubSpot column | Map to |
| - | - |
| Company name | **Client name** (required) |
| Record ID | **External ID** |
| Website URL or Company Domain Name | **Website** |
| Phone Number | **Client phone** |
| Street Address, City, State/Region, Postal Code, Country/Region | **Address**, **City**, **State / region**, **Postal code**, **Country** |
| Contact First Name + Last Name, joined in one column | **Contact name** |
| Contact Email | **Contact email** |
| Contact Phone Number | **Contact phone** |
| Contact Job Title | **Contact title** |

Columns you leave unmapped on Clients are saved with each record as extra data, so HubSpot properties such as industry or owner are not lost.

A HubSpot header with `ID` in it maps only to an ID field. `Record ID` will not be mistaken for a name.

### Leads (open deals)

A deals export on its own is not enough for the **Leads** target. Every row needs:

| Required lead field | Where it comes from in HubSpot |
| - | - |
| **Client name** | Associated company, or the contact's name |
| **Client email** | The associated contact's email. Add this column; the deals export names the contact but does not always carry the email |
| **Event date** | Your event date property. Close Date is the sale date, not the show date |
| **Event type** | Your event type property, or a default you set on the mapping step |
| **Location** | Your venue or city property, or a default |
| **Deal stage** | Deal Stage |

Optional: **Amount** → **Budget**, deal description → **Message / details**, **Record ID** → **HubSpot deal ID**.

If every row should share one value, set a **default** for that field on the mapping step and skip the column. To start from a known-good layout, download the lead template from the wizard and paste your deals into it.

### Events (booked work)

For deals that are confirmed shows, build an Events file with one row per deal. Import it after Clients so each gig links to a real client record.

| HubSpot column | Map to |
| - | - |
| Deal Name | **Event title** (required) |
| Your event date property | **Event date** (required) |
| Record ID | **Event external ID**, so a later import updates the same gig |
| Associated company | **Customer name** |
| Company Record ID | **Customer external ID** |
| Your venue property | **Venue name** |
| Your event type property | **Event type** |

Add a **Status** column and set it to draft when you want to review the gigs before crew can see them. A draft gig is hidden from crew and holds its invitations until you publish it.

## Import into Soundcheck

1. Open **Settings → Apps & data → Import & export** and drop the Clients file on the page.
2. Soundcheck does not recognize a HubSpot companies export from its file name or headers. Under **Review before import**, choose **Clients** as the target, then confirm.
3. Check the suggested mapping (Company name → Client name, Record ID → External ID), fix anything left unmapped, check the preview and commit.
4. Repeat for **Leads**, then **Events**.
5. Open **Leads** to check the pipeline, and open a few gigs to check the client and date.
6. Import each file once more. A clean move shows **0 new** rows.

One bad row doesn't block the file: valid rows commit and rows with errors are skipped. Download the error CSV from the results screen, fix those rows, and import them again. See [When a row is bad](https://docs.soundchecklive.io/features/imports/overview.md#when-a-row-is-bad).

Full wizard detail: [Operator data imports](https://docs.soundchecklive.io/features/imports/overview.md). Lead rules: [Leads](https://docs.soundchecklive.io/features/imports/overview.md#leads).

## Traps

* **Close Date is not the show date.** Map your own event date property to **Event date**.
* **Deal stage names are yours.** Soundcheck keeps the stage text you import. Rename stages in HubSpot before export if you want cleaner names.
* **Duplicate companies.** Clients match by name, so `Acme Events` and `Acme Events LLC` become two clients. Merge duplicates in HubSpot first.
* **Contacts without a company.** A contact row with no company has no client to attach to. Give it a company name or leave it out.
* **Leads match by email and event date.** Importing the same email and event date again updates the matching lead instead of adding one.

## Keep HubSpot running

Some teams keep HubSpot for sales and use Soundcheck from the booking onward.

* **Read HubSpot from your AI.** When your organization has HubSpot connected under **Settings → Apps & data → Integrations**, [member MCP](https://docs.soundchecklive.io/integrations/mcp-server.md) can list HubSpot contacts, companies and deals (`list_hubspot_contacts`, `list_hubspot_companies`, `list_hubspot_deals`). These tools read only.
* **Sync deal stages with gigs.** The [HubSpot ↔ Flex pipeline](https://docs.soundchecklive.io/integrations/hubspot-flex-pipeline.md) keeps a HubSpot deal, a Flex quote and a Soundcheck gig in step. It is not generally available yet.

## Get help with the move

Soundcheck's team has brought a customer's HubSpot deals into Soundcheck, including a season of deals pulled by date range and stage. That customer still sells in HubSpot. If your export is large or your deal properties are unusual, [contact support](mailto:info@soundchecklive.io) before you start.

Practice files with HubSpot's own column names are in the repo under `docs/sample-imports/migrations/hubspot/`.

## Related

> [card] [Coming from another system](https://docs.soundchecklive.io/features/imports/coming-from.md)
>
> Hub for every migration guide, the shared import path and mapping traps

> [card] [Coming from Flex](https://docs.soundchecklive.io/features/imports/coming-from-flex.md)
>
> Move inventory, contacts, venues and quotes from Flex Rental Solutions

> [card] [Lead tracking](https://docs.soundchecklive.io/crm/leads/overview.md)
>
> How the pipeline works once your deals are in

> [card] [Customers](https://docs.soundchecklive.io/crm/customers.md)
>
> Client records and their contacts


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.