Migrate from Propeller CRM to HubSpot

Propeller contacts map directly to HubSpot contacts. The primary company association migrates as the contact's primary company in HubSpot. Propeller's custom per-contact tags become a HubSpot custom multi-line-text or multi-select property so segmentation data is preserved for list-building. This ensures that all contact records retain their original categorization and can be segmented immediately after migration using HubSpot's native list tools.

Propeller company records map 1:1 to HubSpot companies. Domain is preserved as the company domain property for enrichment triggering. If a Propeller contact has no associated company, a placeholder HubSpot company is created so the contact has a valid primary association on import.

Propeller deals map to HubSpot deals. Each deal carries its stage name, monetary value, close date, and owner. If Propeller used multiple pipeline views, the most-active pipeline becomes the primary HubSpot pipeline; others are recreated as additional named pipelines in HubSpot.

Propeller stage names map one-to-one to HubSpot deal stage names within each pipeline. Stage display order and probability are set in HubSpot's pipeline editor. If Propeller stage names conflict with HubSpot default stage names, custom stage names are created to preserve the exact source terminology.

Propeller's Gmail-tracked email history migrates as HubSpot email engagements, associated to the corresponding contact and deal by email-address match and timestamp correlation. Open/click data from Propeller is stored as HubSpot custom properties on the engagement record since HubSpot tracks opens natively.

Propeller notes map to HubSpot notes with original create timestamps and owner attribution preserved. Rich-text formatting in Propeller notes is rendered as plain text in HubSpot notes; if the note contains structured data, it is stored in a custom property on the associated contact or deal.

Propeller call records — including call duration, direction, and outcome — migrate as HubSpot call engagements. Call disposition (answered, voicemail, no answer) maps to HubSpot's call outcome property. Owner attribution and timestamp are preserved so activity history is complete in HubSpot.

Propeller meeting records migrate as HubSpot meeting engagements with start/end time, associated contact, and owner preserved. If Propeller recorded a meeting outcome or follow-up task, that data is stored in HubSpot custom properties on the meeting record. This preserves the complete meeting history including outcomes and follow-up commitments, enabling teams to review past interactions and track accountability after migration.

Propeller's per-record tag system has no direct HubSpot equivalent — HubSpot uses lists, custom properties, and smart lists for segmentation. We create a HubSpot custom property for each unique Propeller tag and populate the tag values per record so list filters in HubSpot can reproduce the original segmentation.

Propeller owner names are matched to HubSpot users by email address. Unmatched owners are flagged and assigned to a fallback HubSpot user until the client provisions the correct HubSpot accounts. Owner assignment is resolved before deal migration so every opportunity lands with a valid HubSpot owner.