Migrate your SendPulse data

SendPulse CRM Contacts are standard structured records with name, email, phone, and custom properties. The platform supports export via UI to XLSX/CSV and via REST API. We map Contacts 1:1 in most migrations, preserving all standard fields and custom properties as name-value pairs.

CRM Companies (Accounts) are first-class objects in SendPulse linked to Contacts via a many-to-one relationship. Export is available per-object. We preserve the company-contact linkage during migration by importing both objects and maintaining the foreign key relationship.

SendPulse Deals include name, value, stage assignment, responsible user, and custom fields. Deal stages map to pipeline stages, which we reconstruct in the destination using the platform's stage export. We carry forward deal value and stage history where the destination schema supports it.

CRM Tasks in SendPulse have title, due date, assignee, status, and linked contact/company. Export is available to XLSX, CSV, or XLS formats. We map Tasks directly, preserving the linked entity reference by resolving the contact or company ID during import.

SendPulse Mailing Lists group Subscribers for campaign targeting. Both objects are exportable individually. We treat Mailing Lists as segment definitions and Subscribers as the contact records, mapping them to equivalent list/tag structures in the destination CRM.

Subscribers are the recipient records in SendPulse's email service, with variables like first name, last name, email, phone, and subscription status. The unique subscriber count drives billing. We preserve subscriber status (active/unsubscribed/bounced) and custom variables, but subscription status semantics differ by platform and require explicit mapping.

Automation 360 flows define multi-step triggered sequences across email and SMS channels. Each flow has conditions, actions, and delay steps. SendPulse does not expose a full programmatic export of flow logic via standard API. We reconstruct flows by documenting the trigger, conditions, and step sequence from screenshots or manual export, then rebuild them in the destination or implement them as equivalent automation rules.

SendPulse bills up to 300 sender addresses on Pro and unlimited on Enterprise. These are verified SMTP senders tied to campaigns. Migration requires re-verification of sender domains or IPs in the destination ESP, which is a manual step outside the data migration scope.

Email campaign results include open rates, click rates, bounce data, and unsubscribes. SendPulse exports statistics to CSV or to a mailing list. We extract these as reporting records and import them as historical campaign performance data, noting that the raw event-level log is not publicly accessible via API.

SendPulse CRM Products include name, price, SKU, category, and hidden integration fields used for POS or payment gateway metadata. Hidden fields (String/Number type, up to 255 characters) are stored under Integration fields. We export all product fields including hidden ones, mapping them to destination product or item records and preserving integration field values as custom metadata.

SendPulse supports chatbots on Telegram, Facebook Messenger, Instagram, WhatsApp, TikTok, and Viber. Chatbot configurations include flow logic, trigger conditions, and message content. Export is not available via API or UI. We document chatbot structure from screenshots and rebuild the message trees in the destination platform, noting that platform-specific channel integrations will need reconfiguration.

SendPulse Landing Pages are self-contained web assets built on the platform. They are not exposed via API for export. The HTML content, form fields, and connected CRM logic cannot be programmatically extracted. We recommend migrating form configurations and lead data separately while rebuilding landing pages manually in the destination tool.

SendPulse's Course Builder creates courses with lessons and tracks student enrollment, progress, and completion. Student records are exportable. Course content (video, text) resides on SendPulse's platform and cannot be exported. We migrate student enrollment and progress data, flagging that course media must be re-hosted in the destination LMS.