Migrate from Spin CRM to HubSpot

Spin CRM contacts migrate to HubSpot contacts. The HubSpot contact record retains the original email, name, phone, job title, and address fields. Owner resolution happens by email match against HubSpot users — unmatched owners are flagged before migration so your admin can assign a fallback owner.

Spin CRM companies map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer directly. Spin CRM parent-company relationships map to HubSpot's Parent Company field. Contacts without a primary company receive a placeholder association until the record is reviewed.

Spin CRM deals map to HubSpot deals 1:1. Deal name, amount, close date, and owner transfer directly. Each Spin CRM sales process becomes a HubSpot pipeline — the pipeline name becomes the HubSpot pipeline name and the stages within map to HubSpot deal stages via value mapping per pipeline.

Spin CRM supports multiple named sales processes, each with its own pipeline stages. Each Spin CRM sales process becomes a separate HubSpot pipeline. If Spin CRM has two sales processes named 'Direct Sales' and 'Partner Sales', both migrate as HubSpot pipelines with their respective stage names mapped to HubSpot deal stages.

Stage names from Spin CRM map value-by-value to HubSpot deal stages within the corresponding pipeline. Probability and forecast category are re-applied based on HubSpot's stage defaults unless your team specifies custom probability values. Stage-transition timestamps are preserved as custom datetime fields on the deal.

Spin CRM tasks migrate as HubSpot engagements of type 'task'. The task subject, body, due date, and completion status transfer. Completed tasks preserve their completed timestamp. Incomplete tasks appear in HubSpot as open tasks on the contact or company timeline.

Spin CRM calls, emails, and meetings migrate as HubSpot engagements on the contact record. Original timestamps, duration (for calls), and body content are preserved. Meetings include start and end times from Spin CRM. Each engagement is linked to the parent contact record.

Spin CRM notes transfer as HubSpot notes attached to the relevant contact, company, or deal record. Note body content is preserved. If Spin CRM notes contain attachments, the file content is re-uploaded and linked to the HubSpot note. During migration, note timestamps are retained as the HubSpot note creation date, providing an accurate activity timeline. Any embedded images or linked files are preserved and remain accessible from the HubSpot note.

Spin CRM's flexible custom field model means every custom field defined in Spin CRM needs a corresponding HubSpot custom property created before the migration runs. FlitStack AI generates the property creation list based on the Spin CRM export. Pick-list custom fields in Spin CRM map as HubSpot pick-list custom properties with the same option values.

Spin CRM file attachments on contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. Files are attached to the corresponding HubSpot record via the file association. Large files exceeding HubSpot's default 25 MB per-file limit are flagged for manual review.

Spin CRM products associated with deals map to HubSpot line items. Product name, unit price, and quantity transfer. If Spin CRM stores product descriptions, those migrate as the line item description. Line items are linked to the HubSpot deal after the deal record is created.

Spin CRM user records are matched to HubSpot users by email address. If a Spin CRM owner has no matching HubSpot user, the deal or contact is assigned to a designated fallback HubSpot user and the original owner name is preserved in a custom field (Original_Owner__c) for audit purposes.