Find out why the import will fail — before it does.
Every destination has its own required fields, picklist values and format rules, and none of them tell you what's wrong until you've already uploaded. Pick a target and we'll check your file against its actual rules first.
Email is HubSpot's unique identifier for contacts, so a missing or duplicated address is what usually breaks this import. Lifecycle Stage must also match HubSpot's fixed list exactly.
Salesforce refuses any Lead row missing Last Name or Company — the two fields people most often don't have when importing a scraped or event list.
Mailchimp only truly requires an email address, but its Birthday field takes month and day only — a full date is the classic silent failure here.
Shopify rejects the whole row for a badly formatted phone number, and its marketing-consent columns accept literally only 'yes' or 'no' — not TRUE, 1, or Y.
Klaviyo doesn't need a specific column so much as an identifier: every row must carry an email, a phone number or an ExternalID. Rows with none of the three are dropped, and SMS numbers must be E.164.
QuickBooks caps imports at 1,000 rows, rejects any customer name that duplicates an existing customer, vendor or employee, and refuses colons or quotation marks in the name field.