Migrate from Spark CRM to HubSpot

Spark CRM contacts map directly to HubSpot contacts. Each contact's first name, last name, email, phone, job title, and address fields migrate as HubSpot standard properties. The primary company association from Spark CRM becomes the HubSpot contact's Company property. Contacts without a company in Spark CRM land as unassociated HubSpot contacts, with no default account assigned.

Spark CRM companies map to HubSpot companies on a one-to-one basis. The standard fields—company name, domain, industry, number of employees, annual revenue, phone, address, city, state, zip, and country—migrate as HubSpot company properties. Parent‑child hierarchies defined in Spark CRM are recreated in HubSpot using the parent company association. Any custom properties on the company object are created as HubSpot custom properties before data loads.

Spark CRM deals map to HubSpot deals with deal name, amount, close date, and owner preserved. Spark's deal stage migrates as the HubSpot deal stage within the configured pipeline. Spark's single-pipeline model becomes one HubSpot pipeline; teams can add more pipelines post-migration.

Spark CRM owners are resolved to HubSpot users by matching the email address stored in the owner record to the HubSpot user email. Any owner whose email does not correspond to an existing HubSpot user is flagged in the pre‑migration report; your team can then either create a HubSpot user for that person or reassign their records to a designated fallback HubSpot user before the migration run begins.

Spark CRM logged calls migrate as HubSpot call engagements, preserving call outcome, direction, duration, phone number, and body text. The original call timestamp and the owner assigned in Spark CRM carry over to the HubSpot engagement record. Once in HubSpot, call engagements display in the contact’s timeline, the associated deal’s activity feed, and are searchable via the HubSpot calls API.

Spark CRM logged emails are imported as HubSpot email engagements, transferring the subject line, body (including HTML formatting), participants (to, cc, bcc), and the original sent timestamp. Attachments are downloaded from Spark CRM and re‑uploaded to HubSpot Files, then linked to the engagement. Emails are associated with the appropriate contact and company records by matching email addresses, and they also appear in any related deal’s activity feed.

Spark CRM meeting records are imported as HubSpot meeting engagements, preserving the meeting title, description, start and end times (including time zone), location, and the list of attendees. Any meeting attachments stored in Spark CRM are downloaded and re‑uploaded to HubSpot Files, then linked to the engagement. In HubSpot, the meeting is associated with the relevant contact and company records, and it also appears in the linked deal’s activity feed.

Spark CRM notes are imported as HubSpot note engagements, preserving body text and any HTML or rich‑text formatting. Original creation timestamp and owner transfer to the HubSpot note. File attachments are downloaded and re‑uploaded to HubSpot Files, then linked to the note. Notes are associated with the matching contact, company, or deal by Spark CRM record ID, keeping context in HubSpot.

Spark CRM's custom field API uses a key-value pair structure grouped by field category. Each unique key becomes a HubSpot custom property on the appropriate object (contact or company), with the data type inferred from the value format. Multi-value selections in Spark CRM become HubSpot multi-checkbox or multi-select properties with value-by-value mapping.

Spark CRM allows a deal to associate with multiple contacts. In HubSpot, each deal has a primary contact with additional contacts added via deal-contact associations. We migrate all Spark deal-contact links; the primary contact is identified by the most-recent association timestamp or your specified rule.

Spark CRM file attachments are downloaded and re-uploaded to HubSpot Files. Files are associated with the relevant contact, company, or deal record. Large files are subject to HubSpot's file size limits. Original Spark file URLs embedded in notes are flagged for manual review post-migration.

Spark CRM's single pipeline and its stage set map to one HubSpot pipeline with corresponding stages. Each stage name becomes a HubSpot deal stage value in the target pipeline. If Spark stages include custom statuses not present in HubSpot's defaults, those stages are created as custom stage values within the pipeline.