Migrate from SendPulse to HubSpot

SendPulse contacts migrate directly to HubSpot Contacts. The SendPulse company_id field resolves to the migrated HubSpot Company by company name lookup, then associates via HubSpot's primary Company field on the Contact record. All contact properties, including email, phone, and custom fields, are mapped to the corresponding HubSpot Contact properties, preserving timestamps and owner assignments.

SendPulse companies map 1:1 to HubSpot Companies. Parent-child company hierarchies in SendPulse map to HubSpot's Parent Company field. SendPulse company ID stored as Source_System_ID__c for traceability. Each company record also retains its original industry, website, and address fields, which are mapped to HubSpot's corresponding company properties, ensuring data continuity across the migration.

SendPulse deals map to HubSpot Deals with stage-name remapping to the target HubSpot pipeline. SendPulse's single-stage model maps to whichever HubSpot pipeline your team designates as primary. Stage probabilities re-applied from HubSpot's pipeline configuration. Deal owner assignments are resolved by email match to HubSpot users, and any unmatched owners are flagged for manual assignment before the migration runs.

Each SendPulse deal pipeline becomes a separate HubSpot Pipeline. If SendPulse has multiple pipelines, we create corresponding HubSpot pipelines with stage names remapped per pipeline. Closed-won and closed-lost stages added per HubSpot convention. Stage ordering and probability weights are set according to your HubSpot pipeline configuration, ensuring accurate forecasts and reporting from day one.

SendPulse tasks (calls, meetings, to-dos) migrate as HubSpot Timeline events with original timestamps, subject lines, owner email resolution, and linked contact or deal associations preserved. Each event type (call, meeting, or to-do) is tagged with a specific HubSpot engagement type, and any missing owners are logged for manual assignment post-migration.

SendPulse email open and click events become HubSpot Timeline events linked to the Contact. Original event timestamps and campaign names preserved. Volume of events can affect migration duration significantly. We also record the engagement type as a custom property, allowing you to filter and report on email interactions within HubSpot's analytics dashboards.

SendPulse chatbot conversation logs have no native HubSpot equivalent. We export them as structured Note records in HubSpot with original timestamps, bot name, and full conversation text for reference. These notes are searchable in HubSpot and can be linked to the associated contact record, providing a complete view of each chatbot interaction.

SendPulse SMS campaign sends and responses migrate as HubSpot Timeline events with Type=SMS, original timestamps, and linked contact associations preserved. Each SMS event captures the message content, direction (sent or received), and any UTM parameters present, enabling detailed reporting on SMS performance within HubSpot's analytics suite.

SendPulse per-contact custom fields become HubSpot Contact properties. If a property name already exists in HubSpot, we map to it; if not, we create a new HubSpot property with the appropriate type before migration. All custom field values are transferred as-is, preserving data integrity and enabling immediate reporting post-migration.

SendPulse Automation 360 flows (email sequences, trigger-based flows, A/B branches) do not migrate. We export flow definitions as a JSON reference file your HubSpot admin uses to rebuild each automation in HubSpot's workflow editor. The export includes trigger conditions, branch logic, and A/B test configurations, giving your team a comprehensive blueprint for reconstruction.

SendPulse per-contact engagement statistics (email sent count, open count, click count, last email date) migrate as HubSpot custom number or date properties on the Contact record for reporting continuity. These properties allow you to track contact engagement trends, measure email campaign effectiveness, and segment contacts based on historical activity within HubSpot.