Migrate from SalesCaptain to HubSpot

SalesCaptain contacts migrate as HubSpot contacts. Every standard contact property (firstname, lastname, email, phone, jobtitle, address fields) maps directly to HubSpot's contact properties. Owner assignment resolves by email match against HubSpot users. Unmatched owners receive a fallback assignment or are flagged for your admin to provision before the full migration runs.

SalesCaptain company records map to HubSpot company records. Company name, domain, industry, employee count, and revenue field map directly. HubSpot's company record serves as the association hub for all related contacts. If a SalesCaptain company has no contacts, it still migrates as a standalone HubSpot company record.

SalesCaptain conversation threads are split into HubSpot engagement sub-types: logged calls become HubSpot Calls, text-based messages become Notes, and scheduled meetings become HubSpot Meetings. Each engagement preserves the original timestamp, owner (resolved by email), and parent contact/company association. Thread-level metadata (e.g., conversation channel) is stored as a custom engagement property.

SalesCaptain deal records migrate as HubSpot deal records. Deal name, amount, and close date map directly. Deal status in SalesCaptain maps to the HubSpot pipeline stage pick-list — this requires mapping each SalesCaptain status value to a corresponding HubSpot stage. If SalesCaptain uses a single pipeline, it maps to one HubSpot deal pipeline. Multiple SalesCaptain deal statuses require multiple HubSpot pipelines.

SalesCaptain custom fields attached to contacts require pre-creation as HubSpot custom contact properties before migration. HubSpot's tier determines the custom property cap. We deliver a custom property creation checklist before the migration run so your HubSpot admin can pre-provision the schema. Field type mapping: text fields to single-line text, number fields to number properties, date fields to date properties, pick-lists to dropdown properties.

SalesCaptain company-level custom fields map to HubSpot custom company properties. Same pre-creation requirement applies — the custom property must exist in HubSpot before data loads. We provide a field-level mapping document that names each SalesCaptain custom field, its HubSpot target property name, and its field type so your admin can create them in the correct order.

SalesCaptain owner IDs resolve to HubSpot owners by email address match. If a SalesCaptain user has no matching HubSpot user account, their assigned records are flagged before migration. Your team either creates HubSpot user accounts for those owners or assigns them to a designated fallback owner. This step prevents orphaned records in HubSpot after migration.

SalesCaptain file attachments on contacts or deals re-upload to HubSpot Files. Each file is re-hosted in HubSpot's file manager and linked back to the associated contact or deal record. Large files (over 250 MB per file) require chunked upload. Inline images in notes are extracted and rehosted separately.

SalesCaptain communication channel profiles (e.g., linked phone numbers, SMS channels, calling profiles) have no direct HubSpot equivalent. Channel identifiers and configuration metadata are preserved as read-only custom properties on the contact record for reference. Rebuilt integrations point to HubSpot's calling or telephony settings post-migration.

SalesCaptain workflow definitions (lead routing rules, follow-up sequences, automated message triggers) do not migrate. We export the workflow logic as a structured JSON reference document that your HubSpot admin or implementation partner uses to rebuild equivalent automations in HubSpot's Workflows tool. Sequence step definitions, trigger conditions, and delay rules are all preserved in the export.