Which CRMs Hailo imports

Hailo reads exports from fifteen tools plus any spreadsheet. Some have a ready-made column map that lines up with that tool's own export; the rest go through the smart path, where Hailo reads whatever you drop and works out the columns. Both end in the same review screen.

The two paths

Path	What happens
Ready-made column map	Hailo knows that tool's export columns by name and maps them straight away. These cards carry a dot marked "One-click CSV import" in the picker
Smart path	Hailo reads the file, proposes a mapping from the headers and the data, and shows it to you to confirm. Exact export steps are still given for each tool

In both cases the numbers in the preview come from your rows, never from a guess. The smart path only decides which column is which.

Tools with a ready-made column map

Tool	Files to export
Pixieset Studio Manager	Contacts CSV, Transactions CSV
Studio Ninja	Clients CSV, Payments CSV
Dubsado	Projects CSV (one per status), Transactions CSV
Bloom	Contacts CSV, Invoices CSV, Transactions CSV
Aisle Planner	Leads CSV, Contacts XLSX, Payment Reports XLSX
Spreadsheet / Other	Any CSV from Google Sheets, Excel, Numbers, Airtable or Notion. Hailo's own templates are here too

Tools that use the smart path

Tool	Files to export
Táve (now VSCO Workspace)	Jobs CSV, exported with all columns
HubSpot	Contacts or Deals CSV, Invoices and Payments CSV
HoneyBook	Contacts CSV, Projects report CSV, Payments Completed CSV
17hats	Contacts CSV, Client Sales report CSV
Pixifi	Clients CSV
Iris Works	Client list CSV (from their support), Square export CSV
Sprout Studio	Contact Analytics CSV, your payment processor's CSV
ShootQ	Contacts CSV, QuickBooks .iif invoices and payments (convert to CSV first)
Vidlead Studio	Support-assisted CSV. Vidlead has no self-serve export

The page for each tool in Hailo lists the exact menu clicks for that export, kept current.

The columns Hailo can fill

Clients file

Hailo field	Typical column names it recognises
Couple / client name	Client name, Couple, Full name, Contact name, Customer
Partner A name	Partner 1, Bride, Groom, First name, Spouse 1
Partner B name	Partner 2, Spouse 2, Second contact, Fiance, Co-client
Email	Email address, Client email, Primary email
Secondary email	Partner email, Email 2, Alternate email
Phone	Phone number, Mobile, Cell, Client phone
Secondary phone	Work phone, Alt phone, Phone 2
Mailing address	Street address, Home address, Address line 1
Client status	Status
Deal stage	Stage, Pipeline stage
Inquiry / date created	Created, Inquiry date, Date added
Event type	Event type, Job type
Event / wedding date	Wedding date, Event date, Shoot date, Main shoot date
Ceremony venue	Ceremony venue, Venue
Reception venue	Reception venue
Venue address	Venue address
Guest count	Guests, Guest count
Contract total / revenue	Revenue, Contract total, Total
Outstanding balance	Balance, Balance due
Collected / paid so far	Paid, Collected, Amount paid
Notes	Notes

That is 23 fields. When a jobs list carries revenue and balance on each row (Táve and HoneyBook do), Hailo builds an invoice and a deposit for each couple from those two numbers so the review shows real money rather than zero.

Invoices and payments file

Hailo field	What it holds
Client (to match the clients file)	The name or email that ties the row to a couple
Invoice number	The invoice's own number
Invoice date / issued	When it was sent
Due date	When it was due
Subtotal	Before tax
Tax	Tax amount
Invoice total	The billed total
Invoice status	Paid, unpaid, overdue and so on
Row type (invoice/payment/refund)	Whether the row is an invoice, a payment or a refund
Payment amount	Amount of a payment row
Payment method	Card, transfer, cheque and so on
Payment status	Completed, pending, failed
Payment date	When it was received

That is 13 fields. Several payment rows with the same invoice number are grouped back into one invoice.

How headers are matched

Hailo compares your column headers to a list of known names for each field. The comparison ignores case, spaces and underscores, so "Wedding_Date", "wedding date" and "WeddingDate" all match. When two fields could claim the same header, the longer, more specific name wins. Anything Hailo cannot place is left unmapped, and you can point it at a field in the mapping grid.

Dates are read in the order your tool uses. Pixieset exports day-first dates and Hailo reads them that way; the others are month-first.

What "what won't come over" means

Every tool's page has a fold titled What won't come over (on the Settings page, What won't come across). It lists what that tool's export does not contain, so you know what to add by hand afterwards. Common examples:

• A contacts export with no wedding date, venue, package or pipeline stage. Those come from the gap interview or the record page.
• Transactions that are payment-level only, so a multi-payment invoice arrives as several rows and the billed total is rebuilt from them.
• Reports that only include invoices paid in full, so open balances are missing.
• Custom fields and questionnaire answers, which most tools drop.
• Exports that need an owner or admin login. Limited roles get a stripped file.

Nothing in that list stops the import. It tells you what to check on Manage > Clients afterwards.

If it didn't work

Your tool is not in the list. Export a CSV of your clients from wherever you keep them and pick Spreadsheet / Other. A screenshot of a client list also works through Have Hailo sort it for me in onboarding.

Your tool exports several files for one thing. Drop them all on the same zone. Duplicates merge on the couple's name and email.

The export button is missing in your old tool. Most tools hide export from non-owner roles. Sign in as the account owner.