Migrate from Salescamp CRM to HubSpot

Salescamp's unified contact record maps directly to HubSpot Contact. The primary phone, email, job title, and address fields migrate as HubSpot contact properties. Salescamp owner (assigned by email) resolves to the HubSpot user with the matching email address. Custom fields on the contact map to HubSpot custom properties created before migration.

Salescamp lead status values map to HubSpot lifecycle_stage by default: 'Won' maps to 'Customer', 'Qualified' maps to 'SQL', 'Contacted' maps to 'Lead', 'New' maps to 'subscriber'. 'Lost' can map to a closed-lost lifecycle value or be preserved as a custom lead_status property for reporting continuity.

Salescamp company records map 1:1 to HubSpot Company objects. Core fields—company name, domain, industry, employee count, annual revenue, phone, address, city, state, country, zip—migrate to their HubSpot equivalents. Any custom fields on the Company object are created as HubSpot custom properties before migration. Parent‑company hierarchies map to HubSpot's parent_company_id property; child records are staged until the parent exists to avoid orphan associations.

Salescamp deals migrate to HubSpot Deals. Each Salescamp deal pipeline becomes a HubSpot Pipeline object. The deal name, amount, close date, owner, and stage all map to their HubSpot Deal equivalents. HubSpot's Deal object does not require a Contact association at creation — but a contact association is required for the deal to appear in the contact's deal timeline.

Each Salescamp pipeline becomes a HubSpot Pipeline. HubSpot Pipelines own their stage sets independently — the same stage name can have different probabilities in different pipelines. FlitStack creates the HubSpot pipeline and its stages based on the stage names and probabilities extracted from Salescamp before deal records load.

Salescamp stage names map value-by-value to HubSpot stage names within each pipeline. Stage probability and closed-won / closed-lost flags migrate from Salescamp's stage settings into HubSpot's stage configuration for each pipeline. HubSpot's forecast category (Omitted, Pipeline, Best Case, Commit, Closed Won, Closed Lost) is set per stage during migration.

Salescamp call logs, email logs, meeting records, and tasks migrate as HubSpot Engagements — the native activity store. Each engagement retains its original timestamp, owner (resolved by email match to HubSpot user), and association to the parent Contact or Deal. Call duration and outcome from Salescamp map to HubSpot call engagement properties.

Salescamp notes attached to contacts or deals migrate as HubSpot Notes. Note body text and the original create timestamp are preserved. HubSpot Notes can be associated to both a Contact and a Deal simultaneously, which mirrors Salescamp's note attachment behavior. Rich-text formatting in Salescamp notes is preserved as plain text or converted to HubSpot's note format.

Salescamp file attachments are downloaded and re-uploaded to HubSpot Files. Each file is associated to the original parent record (Contact or Deal). Files are re-uploaded to HubSpot's file storage — file size limits for HubSpot uploads apply. Inline images in Salescamp notes are extracted and rehosted within HubSpot's file manager.

Salescamp custom fields do not exist in HubSpot — each one requires a corresponding HubSpot custom property created before migration. FlitStack generates a property creation plan from the Salescamp field inventory, specifying the HubSpot property name, type (text, number, date, picklist, checkbox), and whether it is single-value or multi-value. Pick-list custom fields in Salescamp require value-by-value mapping to HubSpot pick-list options.

Salescamp workflow rules (task triggers, email automation, field-update sequences) have no HubSpot equivalent — they cannot be migrated directly. FlitStack exports Salescamp workflow definitions as a structured reference document so your HubSpot admin can rebuild equivalent automation in HubSpot's workflow engine. This is a manual step that takes place after the data migration is validated.

Salescamp owner records resolve to HubSpot users by email address match. If a Salescamp owner has no matching HubSpot user account, their records are flagged and assigned to a designated fallback HubSpot user (or a placeholder owner field) before migration. User permissions, roles, and team structure do not migrate — those are HubSpot-side configuration.

If Salescamp tracks campaign membership or UTM source as a field on contacts, that data migrates as a HubSpot custom contact property (e.g., original_source or campaign_name). HubSpot's native campaign membership is a separate object with different economics — for a direct campaign tracking migration, a custom property preserves the source attribution data without requiring a HubSpot campaign record.