Migrate from Sales Snap to HubSpot

Sales Snap contacts map directly to HubSpot contacts. HubSpot requires a primary company association — contacts without a linked company in Sales Snap land as HubSpot contacts with no associated company record, and your team sets the association manually or via a secondary mapping pass.

Sales Snap company records map to HubSpot company records. HubSpot company hierarchies (parent/child) are supported via the parent_company_id field, which maps to HubSpot's parent company association. Multi-company associations on a single contact collapse to the primary company in HubSpot. During migration, we preserve the parent_company_id values and recreate the hierarchy in HubSpot using the parent_id field, ensuring reporting continuity for child companies.

Sales Snap deals map to HubSpot deals. The pipeline field in Sales Snap determines which HubSpot deal pipeline the record enters. Deal stage names map value-by-value to the corresponding HubSpot pipeline stages, and stage probability is re-applied based on HubSpot's stage configuration.

Each Sales Snap pipeline stage value maps to a HubSpot deal stage value within the target pipeline. Stage probability percentages are preserved as custom fields in HubSpot for reporting continuity. Custom stage values in Sales Snap require corresponding stage creation in HubSpot before migration runs.

Sales Snap custom contact fields require HubSpot custom properties created in the portal before import. We deliver a schema setup plan naming each custom property, its HubSpot data type (text, number, date, picklist, checkbox), and any default values or validation rules to apply. Properties that exist in HubSpot with matching names map directly.

Sales Snap custom deal fields map to HubSpot deal custom properties. Each property requires creation in HubSpot with the correct field type — picklists must match the source values exactly for import to succeed without error. We validate property type compatibility during the mapping phase.

Sales Snap call logs with timestamp, duration, owner, and outcome map to HubSpot call records on the contact timeline. HubSpot requires a connected calling plan or telephony integration to log calls natively; our migration creates the activity records so they appear in the contact's timeline regardless of calling tool.

Sales Snap email engagement records map to HubSpot email activities on the contact timeline. HubSpot's email tracking requires a connected inbox or CRM seat — our migration preserves the subject, body preview, timestamp, and owner so the activity history is complete even before inbox connection is configured.

Sales Snap meetings map to HubSpot meeting records on the contact or deal timeline. Original start/end times, location, title, and owner are preserved. If Sales Snap stores meeting notes as separate records, they map to HubSpot engagement notes attached to the meeting.

Sales Snap notes map to HubSpot notes on the associated contact or deal record. Rich-text formatting in Sales Snap notes is preserved as plain text in HubSpot's note body. Notes without an associated record map to the contact if a contact association exists.

Sales Snap owner IDs resolve by email match against HubSpot users. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts for them or assigns their records to a fallback owner. No record migrates without a valid HubSpot owner.

Sales Snap tasks and follow-up reminders map to HubSpot CRM tasks attached to the relevant contact, company, or deal. Task status (open, completed), due date, and owner are preserved. HubSpot's task model supports only one owner per task, matching Sales Snap's assignment logic.