Migrate from SendPulse to Nutshell

SendPulse CRM Contacts map directly to Nutshell People. The mapping preserves first name, last name, email address, phone number, and any custom contact properties as Nutshell custom fields on the Person record. We resolve the Company linkage (many-to-one in SendPulse) by creating Nutshell Company records first and linking via the Person-Company relationship field. Any SendPulse contact that represents an unqualified prospect maps to a Nutshell Lead instead, with a Lead status set to Open; the customer's admin converts to Person post-migration as needed.

SendPulse Companies map to Nutshell Companies with a direct 1:1 mapping on company name as the dedupe key. Address fields (street, city, state, postal code, country) migrate to Nutshell's address fields. We pre-create all Companies before Person import so that the Person-Company relationship is satisfied at insert time. Any SendPulse Company without contacts attached still migrates as a standalone Company record.

SendPulse Deals map to Nutshell Deals with the deal name, value, and stage preserved. The SendPulse pipeline assignment maps to a Nutshell Pipeline that we configure before migration, with deal stages mapped to Nutshell stage values. Responsible user (SendPulse owner) resolves to Nutshell User by email match. Closed-won and closed-lost reasons from SendPulse custom fields migrate as Nutshell custom deal fields.

SendPulse CRM Tasks map to Nutshell Activities of type Task. Task title, due date, assignee, status, and linked contact/company migrate directly. The linked SendPulse contact reference resolves to the Nutshell Person record by email; the linked company resolves to the Nutshell Company record by name. Completed status in SendPulse maps to Nutshell's completed Task status.

SendPulse Mailing Lists and Subscribers are a two-object structure: a Mailing List groups Subscribers, and Subscribers are the actual contact records. We flatten this into Nutshell People records with the Mailing List name(s) stored as Tags on each Person. Email address, first name, last name, and subscriber variables migrate to Person fields and custom fields. The unique-subscriber deduplication logic is applied here: SendPulse bills on unique email addresses per month, but Nutshell counts raw records, so we deduplicate by email address during extraction to avoid importing duplicate Person records.

SendPulse email campaign results (open rate, click rate, bounce data, unsubscribes, send date) export to CSV and migrate to Nutshell as Activity records logged against the relevant Person record. Each campaign generates a 'Email Campaign' activity with the campaign name in the activity title and statistics stored in a JSON custom field on the activity for reporting. Delivery statistics reflect SendPulse's send history; Nutshell does not operate as an email sending platform, so these are historical records, not live delivery metrics.

SendPulse Products with name, price, SKU, and category map to Nutshell Products if the customer uses Nutshell's product catalog feature, or to custom fields on the Deal object if they track products manually per deal. The hidden integration fields (POS IDs, payment gateway metadata stored in hidden String/Number fields up to 255 characters) require a targeted API call using the integration_fields parameter; we extract these and write them as Nutshell custom text fields on the Product or Deal record. This step is not automatic and must be explicitly requested during scoping.

SendPulse Automation 360 flows have no API export endpoint. Flow trigger logic, step conditions, delays, and CRM actions exist only within the SendPulse UI and cannot be programmatically extracted. We document every active flow with screenshots and step descriptions, then deliver a written rebuild guide with the equivalent logic mapped to Nutshell Workflow rules. The customer's admin rebuilds the flows in Nutshell post-migration. Complex multi-branch flows with multiple triggers require significant reconfiguration and should be scoped as a separate automation rebuild engagement.