Skip to main content
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.
Soundcheck mapping step for a HubSpot companies export, with Company name mapped to Client name and Record ID to External IDSoundcheck mapping step for a HubSpot companies export, with Company name mapped to Client name and Record ID to External ID

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

Export from HubSpot

HubSpot exports each object from its own list page. Official help: 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.
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. 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: 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. 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. Full wizard detail: Operator data imports. Lead rules: 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 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 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 before you start. Practice files with HubSpot’s own column names are in the repo under docs/sample-imports/migrations/hubspot/.

Coming from another system

Hub for every migration guide, the shared import path and mapping traps

Coming from Flex

Move inventory, contacts, venues and quotes from Flex Rental Solutions

Lead tracking

How the pipeline works once your deals are in

Customers

Client records and their contacts