This is a manual file transfer into a calling list. It does not carry over HubSpot owners, associations, deals, consent fields, DNC flags or activities. It does not update HubSpot after a call or trigger follow-up. An imported contact is not automatically eligible to dial.
1. Export an eligible Contacts view.
You need HubSpot export permission and permission to use these contacts for the intended calls. In HubSpot, open CRM → Contacts (some accounts show this under More). Select a saved view filtered to the contacts your team is authorized to call. Review opt-outs and restrictions before exporting; do not substitute a lifecycle stage for a calling eligibility decision.
HubSpot's export records instructions ↗ describe exporting from the list view with Export. Choose CSV and English column headers for the mapping below. Include the properties you need in the view, or use Customize to choose what is exported. Keep Record ID in your private source copy for reconciliation. Download the file from HubSpot's export email and store it securely; do not forward it to support.
2. Rename the headers in a working copy.
The current DialBreeze importer recognizes specific headers. Lowercasing a header does not remove spaces: First Name is not first_name. The phone header “Phone Number” is already recognized, but using a consistent phone column makes the selected number explicit. A generic drag-and-drop mapping wizard is not assumed. Review the actual file, especially if your HubSpot properties are customized.
| Source property | Working CSV header | Check before upload |
|---|---|---|
| First Name | first_name | Rename the header; do not use “First Name” with a space. |
| Last Name | last_name | Rename the header; keep accented characters in UTF-8. |
| Phone Number or Mobile Phone Number | phone | Pick one number per row; keep + and the country code. Mobile Phone Number is not an explicit importer header. |
| Keep one primary address; do not combine secondary emails. | ||
| Street Address | address | Optional. Rename; do not assume every HubSpot property is recognized. |
| City / State/Region / Postal Code | city / state / zip | Optional, separate columns. Review the actual exported headers. |
| Record ID | Do not import as a mapped field | Retain in a separate private reconciliation sheet. A HubSpot ID is not a DialBreeze lead ID. |
Use exactly one chosen phone in the phone column. Keep it as text so a spreadsheet does not strip the leading plus or turn it into a number. Use an explicit international prefix; ten-digit numbers are treated as US numbers by the current importer. Remove rows without a usable phone before upload rather than relying on automatic guessing.
first_name,last_name,phone,email,address,city,state,zip
Alex,Example,+12025550101,alex@example.com,,,,This is fictional format-only data, not a number to call. Remove unrelated properties, secondary phones and IDs from the upload copy. Unsupported columns do not become CRM fields; consent and stop requests must be reviewed separately.
3. Import five rows into a separate named list.
- Create a test list and upload a UTF-8 CSV with a header row, using the supported list import workflow. Use a new list that is not selected in any active session. The current importer creates NEW leads immediately; it does not provide a preview-only or release approval gate.
- Inspect every accepted row: first/last name, chosen phone, email and optional address. Compare the accepted count against the file. Rows without a parsable phone are skipped; a successful upload does not prove every row was accepted.
- If fields are blank or a phone is wrong, fix the file and inspect the destination before retrying. The importer is not a HubSpot upsert keyed on Record ID; do not assume repeated uploads reconcile existing people.
- Record the export date, view/filter and file version. Release the production list only after an admin checks contact restrictions and the current source records again.
4. Reconcile contact data separately from outcomes.
An admin can export selected DialBreeze leads or a list as a contact CSV. This export has First Name, Last Name, Email, address fields and a split phone: Code plus Phone Number. Rebuild a text phone as +{Code}{Phone Number} before mapping to HubSpot's Phone number property. Do not map DialBreeze's ID to HubSpot Record ID.
For an update to existing HubSpot contacts, join against your retained HubSpot IDs using a reviewed, unambiguous match. HubSpot's file requirements ↗ describe unique identifiers such as Record ID or Email; ambiguous or changed email addresses need manual review. Only include fields you intend to update and review the preview. Do not blindly create duplicates or overwrite your source contact data.
For a simple contacts-only import, HubSpot documents Data Management → Data Integration → Import data → Quick import (contacts only). Follow its current import steps ↗ and permissions; advanced updates or object associations use a different import flow. This contact export does not contain call dispositions, notes or tasks. For outcomes, review the signed outbound webhook contract and budget for your own receiver—not a native HubSpot writeback.
Before you request setup.
Tell us your source view, approximate list size and the fields you need. Do not send API keys, passwords, OAuth tokens or real contact files by email. Setup is assisted, uses your own Telnyx calling account, and the request takes no payment and does not create an account.