Migrate from SalesPro CRM to HubSpot

Direct 1:1 map. SalesPro contacts land as HubSpot contacts with all standard properties transferred. SalesPro's company assignment becomes HubSpot's primary company association; additional SalesPro company links migrate as HubSpot secondary company associations. Each contact's original SalesPro creation date is preserved in a custom datetime property to maintain historical context for reporting and audit purposes.

Direct 1:1 map. SalesPro company records become HubSpot company records. Company name, domain, industry, employee count, and annual revenue map to HubSpot's corresponding company properties. Parent-child company hierarchies in SalesPro transfer via HubSpot's Parent Company field.

Direct 1:1 map. SalesPro deals become HubSpot deals. Each SalesPro deal pipeline maps to a corresponding HubSpot deal pipeline. Deal stage values require value-by-value mapping against HubSpot pipeline stage names configured for your portal. We also preserve the original SalesPro deal creation date in a custom datetime property to maintain historical context and ensure accurate reporting after migration.

SalesPro call logs migrate as HubSpot engagement records of type 'call'. Original call date, duration (if stored), direction (inbound/outbound), and outcome notes attach to the parent contact or deal in HubSpot's engagement timeline. The call duration is stored in seconds in HubSpot's call_duration property. If SalesPro recorded the outcome in a custom field, that data maps to HubSpot's hs_call_resolution property or a custom property if specified in the mapping plan.

SalesPro email logs migrate as HubSpot engagement records of type 'email'. Subject line, timestamp, and association to the contact or deal are preserved. Email body content migrates to HubSpot's engagement notes body field. Attachments on emails are handled separately through the file migration process. If the email was part of a sequence in SalesPro, the sequence information is captured as a custom property since HubSpot sequences work differently.

SalesPro meeting records migrate to HubSpot's meetings tool. Meeting title, scheduled time, location (if applicable), attendees (linked contacts), and outcome notes attach to the associated records in HubSpot. The meeting body or description from SalesPro migrates to HubSpot's meeting notes. If the meeting was created as part of a SalesPro sequence or workflow, that context is noted for your team to rebuild in HubSpot's workflow tool if needed.

SalesPro notes on contacts, companies, or deals attach as HubSpot engagement notes. Rich-text formatting in SalesPro notes is preserved where HubSpot's note format supports it. Standalone notes without a parent record become unattached engagement records. If a SalesPro note contains @mentions of other users, those mentions are converted to text references since HubSpot's note @mentions work differently and your team will need to re-establish those connections.

SalesPro user accounts are matched to HubSpot users by email address. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts for them or assigns their records to a fallback owner before data lands. If a SalesPro user is inactive in SalesPro, we recommend either deactivating them in HubSpot after migration or reassigning their records to an active owner to avoid orphaned records.

Every SalesPro custom field requires a corresponding HubSpot custom property created before migration. We deliver the full custom property specification (name, type, pick-list values, visibility settings) as part of the migration plan. This includes mapping SalesPro field data types to HubSpot field types (text, number, date, picklist, etc.).

SalesPro file attachments on records re-upload to HubSpot's file storage. Files attach to the same HubSpot record (contact, company, or deal) they were linked to in SalesPro. File size limits per HubSpot's storage tier apply. If a file exceeds HubSpot's upload limit, we notify your team before migration so you can decide whether to store it externally and link to it, or split the attachment into smaller files.