Migrate from SendPulse to Pipedrive

SendPulse CRM Contacts map directly to Pipedrive Persons. Email is the dedupe key. We preserve first name, last name, phone, and all custom contact properties as Pipedrive custom fields. The SendPulse contact owner maps to a Pipedrive User by email match; any unresolved owner goes to a reconciliation queue for the customer's admin to provision before production import. Created and updated timestamps migrate as custom fields since Pipedrive's native timestamps are read-only on import.

SendPulse CRM Companies map to Pipedrive Organizations. The organization name becomes the Organization's primary name field; the website URL migrates as the Website field. We preserve all custom company properties as Pipedrive Organization custom fields. Organizations are imported before Persons so that the Person-Organization lookup relationship (Org ID on Person) is satisfied at insert time.

SendPulse Deals map to Pipedrive Deals with deal name, value, stage, responsible user, expected close date, and custom fields preserved. The SendPulse pipeline and stage name map to a Pipedrive Pipeline and Stage; we create these in Pipedrive during schema design before migration. Stage probabilities migrate as custom fields if the customer requires the original values; Pipedrive's native stage probability percentages can be set independently.

SendPulse CRM Tasks map to Pipedrive Activities. Each task's title, due date, assignee, status, and linked Contact or Company transfer as an Activity record. The linked Contact (Person) and Company (Organization) are resolved via the Person and Organization ID mappings performed earlier in the migration sequence. Task status (completed, open) maps to the Pipedrive Activity done flag (true/false).

SendPulse Subscribers are contact records scoped to a Mailing List with subscription status (active, unsubscribed, bounced) and per-subscriber variables. We flatten all Subscribers into Person records using email as the dedupe key, then write a custom multi-select field on each Person listing every SendPulse List the email address belonged to. Subscription status per list is stored in additional custom fields. Multiple Lists with the same email address result in one Person record with all list memberships preserved.

SendPulse CRM Products map to Pipedrive Products with name, price, SKU, and category fields preserved. Hidden integration fields (String or Number type, up to 255 characters, stored under the product integration_fields key in the API) do not appear in the standard product export UI. We access these via a targeted API call to the integration_fields parameter, extract them, and write them as Pipedrive custom fields on the Product record. This step must be explicitly requested during scoping since it requires a non-standard API call.

SendPulse email campaign performance data (open rates, click rates, bounce counts, unsubscribe counts per subscriber) has no native Pipedrive equivalent. We aggregate this data per Subscriber and write aggregated statistics as custom fields on the Person record (sp_open_rate__c, sp_click_rate__c, sp_bounce_count__c, sp_unsubscribe_count__c). Individual campaign send history is documented as a separate written record for the customer to reference or import into a BI tool. This is not a full campaign archive in Pipedrive's native UI.

SendPulse Automation 360 flows have no API export endpoint and cannot be extracted programmatically. We document each active flow via screenshots and structured notes covering trigger type, step conditions, delay actions, and channel destinations (email, SMS). The customer receives a written flow inventory with Pipedrive Workflow equivalents annotated for manual rebuild. Complex multi-branch flows with conditional logic require significant reconfiguration in Pipedrive's workflow builder and may need a Pipedrive partner or admin to complete.

SendPulse chatbots (Telegram, Facebook Messenger, Instagram, WhatsApp, TikTok, Viber) store flow logic, trigger conditions, and message content in the platform UI only. No export mechanism exists. We document the chatbot structure as screenshots and structured notes per messenger channel. The customer rebuilds each chatbot in their chosen platform (Telegram Bot API, WhatsApp Business API, or a third-party chatbot builder). The messenger accounts and API keys must be reconfigured in the destination platform independently of the migration.

SendPulse Landing Pages are self-contained web assets with HTML content, form fields, and connected CRM logic that are not exposed via API for export. We document the page URL, form field names, and connected CRM actions in a written inventory. The customer rebuilds landing pages in Pipedrive using the Pipedrive Web Forms feature (Growth plan and above) or in a third-party landing page builder, then connects the form to the Pipedrive account via the standard web-to-lead mechanism.

SendPulse Course Builder student records (enrollment date, completion percentage, completion date, lesson progress) migrate to Pipedrive Person records with course enrollment data written to custom fields. Course content (video, text, lesson structure) resides on SendPulse's platform and cannot be transferred. Students without an existing SendPulse CRM Contact record receive a new Person record; students with an existing Contact are matched by email and enhanced with course metadata.

SendPulse CRM custom properties on Contacts, Companies, Deals, Tasks, and Products map to Pipedrive custom fields of equivalent type. We create all custom fields in Pipedrive before importing any records. Multi-value text fields (tags, arrays) map to Pipedrive multi-select or text fields depending on the customer's reporting needs. Required field enforcement in Pipedrive is disabled during import and re-enabled after validation so that records with incomplete custom fields can be imported and completed post-migration.