Migrate from SendPulse to Mailchimp

SendPulse CRM Contacts map directly to Mailchimp Audience members. Each contact's email address is the primary key; first name, last name, phone, and custom properties migrate as standard and merge fields. The CRM contact's company linkage is resolved separately (see Companies mapping). SendPulse contact owner assignments do not transfer as Mailchimp has no user-level CRM ownership. All contacts inherit the audience's default subscription status at import; unsubscribed and bounced contacts from SendPulse are imported to a suppression list first.

SendPulse email Subscribers are functionally identical to CRM Contacts as email recipient records — they share the same data model for name, email, phone, and subscription variables. We deduplicate against CRM Contacts using the email address as the key, preserving the unique subscriber count for Mailchimp plan tiering. Subscription status (active, inactive, unsubscribed, bounced) maps to Mailchimp's Member Status values and opt-in flags.

SendPulse Companies have no direct Mailchimp equivalent. We extract the company name, domain, industry, employee count, and any custom company fields and write them as Mailchimp merge fields (FIRMNAME, INDUSTRY, COMPANY_SIZE) on the related Contact records. For multi-contact companies, we also apply a tag matching the company name so that audience segmentation can group contacts by account. This preserves account-level context without a formal CRM relationship.

SendPulse Deals (name, value, stage, responsible user, custom fields) have no equivalent in Mailchimp. We transform Deal records into tags on the associated Contact (format: DEAL_[deal_name]_[stage]) and append a formatted note string to the contact record capturing deal value, stage name, and close date. The customer's admin should evaluate whether a standalone CRM (Zoho CRM, HubSpot Starter, or Pipedrive) is needed post-migration if deal pipeline visibility is a business requirement.

SendPulse CRM Tasks (title, due date, assignee, status, linked contact) have no Mailchimp equivalent. We extract task titles, due dates, and completion status and append them as formatted notes on the linked Contact's activity history in Mailchimp. Assignee information is lost unless the customer also migrates user accounts to Mailchimp (Mailchimp does not support internal user assignment on contacts; this is a limitation of the target platform).

SendPulse Mailing Lists define recipient groups for campaigns and map directly to Mailchimp Audiences. Each Mailing List in SendPulse becomes a separate Audience in Mailchimp. SendPulse variable fields defined at the list level (custom subscriber properties) are created as merge fields in the corresponding Mailchimp Audience. The subscriber count per SendPulse Mailing List determines the initial Mailchimp audience size and informs the plan tier selection.

SendPulse campaign performance data (open rate, click rate, bounce data, unsubscribes, send timestamps) has no native Mailchimp equivalent as historical reporting records. We extract aggregate campaign statistics per subscriber and append them as a formatted note on the contact record (last campaign open date, total clicks, opt-out date if applicable). Individual email engagement events are too granular for Mailchimp's contact model; aggregate summaries are the practical preservation limit.

SendPulse CRM Products (name, price, SKU, category, and hidden integration fields for POS or payment gateway metadata) have no Mailchimp product catalog equivalent. We extract product name, price, SKU, and category and write them as contact-level custom properties on the associated Contact record. Hidden integration fields are preserved as string properties with a prefix (INTG_) if requested during scoping. Customers using SendPulse Products for e-commerce catalog management should consider a dedicated Shopify or WooCommerce-to-Mailchimp integration post-migration.

SendPulse Automation 360 flows are not accessible via API and cannot be exported programmatically. We document each active flow by capturing screenshots and step-by-step descriptions of triggers, conditions, delays, and actions. This documentation is delivered as a written inventory with Mailchimp automation equivalents for each step. The customer's admin rebuilds the automations in Mailchimp's automation builder. Flows with complex branching logic or multi-channel triggers (email + SMS) may require significant redesign since Mailchimp does not support SMS automation.

SendPulse verified sender domains and IP assignments do not transfer to Mailchimp. Sender reputation resets at migration. We document every SendPulse sender address used in campaigns and flag which domains and sending IPs are active. The customer's admin must add and verify each domain in Mailchimp's authentication settings (SPF, DKIM, custom tracking domain) before sending resumes. Domain warm-up best practices apply post-verification: start with low volumes and gradual ramp-up to re-establish inbox placement.