Migrate from Salesflare to HubSpot

Salesflare Account maps to HubSpot Company. Account.name becomes Company name, domain becomes Company domain, industry maps via value lookup, and employee count + revenue transfer directly. Multi-address accounts collapse to the primary location; additional addresses are preserved as custom properties.

Salesflare Contact maps 1:1 to HubSpot Contact. First name, last name, email, phone, job title, and address fields map directly. Owner is resolved by email match against HubSpot users. Contacts without a primary company are attached to a placeholder 'Unassigned' company record.

Salesflare Opportunity maps to HubSpot Deal. Deal name, amount, close date, and owner transfer directly. Salesflare pipeline + stage fields map to HubSpot's deal pipeline + dealstage — stage names require value mapping when pipeline structures differ between the two systems.

Salesflare's pipeline field on Opportunity becomes HubSpot's Deal Pipeline object. Each Salesflare pipeline creates a corresponding HubSpot pipeline. Stage names within each pipeline map value-by-value to HubSpot stage names. Stage probability and forecast category are re-applied from HubSpot's pipeline configuration.

Salesflare logged calls, emails, meetings, and notes are imported as HubSpot engagements and notes, preserving original timestamps, owner assignments, and parent‑record links to the contact or company. Each engagement type appears in HubSpot's activity timeline in chronological order, enabling a complete history view for each record. Attachments are transferred to HubSpot Files and linked to the corresponding engagement.

Salesflare owner assignment resolves by email match to HubSpot user accounts. Unmatched owners are flagged before migration — teams either create HubSpot user accounts for them or assign records to a fallback owner. No record lands without a valid HubSpot owner.

Salesflare custom fields on accounts become HubSpot custom properties on the Company object. Property type is inferred from Salesflare data type (text, number, date, pick-list). HubSpot's property type must be set before import — value mapping applies for pick-list fields.

Salesflare custom fields on contacts become HubSpot custom properties on the Contact object. Pick‑list values in Salesflare map to HubSpot pick‑list options, while multi‑select fields are translated to HubSpot multi‑checkbox properties. Boolean, number, and date types transfer directly; date fields are reformatted to YYYY‑MM‑DD during import. HubSpot property types must be pre‑created before the bulk load so the import validation passes without errors.

Salesflare custom fields on opportunities migrate to HubSpot custom properties on the Deal object. Numeric, text, and checkbox fields transfer directly, while pick‑list values are mapped to HubSpot pick‑list options and multi‑select fields become multi‑checkbox properties. Stage‑related custom fields require per‑pipeline value mapping before import. Date and datetime fields are reformatted to HubSpot's YYYY‑MM‑DD standard. Custom properties must be created in HubSpot before the bulk load to avoid validation errors.

Salesflare file attachments on accounts, contacts, or opportunities are downloaded and re-uploaded to HubSpot Files. Files attach to the corresponding HubSpot record (Contact, Company, or Deal). HubSpot's 115MB file size limit applies per file; larger files require chunked upload or alternative hosting.

Salesflare tags on contacts or companies become HubSpot custom multi-select properties or are enrolled in HubSpot lists. Tags with semantic meaning (e.g., 'enterprise', 'referral') are mapped to custom pick-list properties for segmentation; freeform tags are preserved as-is in a tag property.

Salesflare sequences and email templates do not have a HubSpot equivalent that preserves the same logic. These must be rebuilt manually in HubSpot's workflows and sequences tools. FlitStack can export Salesflare sequence definitions as a reference document for your HubSpot admin.