Migrate from SendPulse to Zoho CRM

SendPulse CRM Contacts map directly to Zoho CRM Contacts. We preserve name fields (First_Name, Last_Name), email address, phone number, and all custom properties. The SendPulse contact ID is stored as a custom field sp_contact_id__c for reconciliation. Address data migrates to Zoho's Mailing_Street, Mailing_City, Mailing_State, and Mailing_Country fields. Custom properties with picklist values are mapped to Zoho picklist fields if the destination layout includes matching picklist options.

SendPulse CRM Companies map to Zoho CRM Accounts. The company name becomes Account_Name, website becomes Website, and industry data maps to the Industry picklist. SendPulse company-contact linkage is preserved through Zoho's Contacts subgrid on Account; we resolve the company reference at migration time so that each Contact is linked to its parent Account via the Account_Name lookup. Any company without contacts is imported as a standalone Account.

SendPulse email Subscribers do not map 1:1 to Zoho CRM records because Subscribers are contact records in the email marketing layer rather than the CRM layer. We treat Subscribers as potential Leads in Zoho. Each unique subscriber email address becomes a Zoho Lead with the email address, first name, last name, and any custom variables (phone, company name) mapped to corresponding Lead fields. Subscribers that already exist as CRM Contacts in SendPulse are deduplicated during import to avoid creating duplicate Leads. The customer chooses during scoping whether to import all subscribers as Leads or to filter by subscription status (active, unsubscribed, bounced).

SendPulse Deals map to Zoho CRM Potentials. Deal name becomes Potential_Name, Deal value maps to Amount, and responsible user maps to Owner. SendPulse Deal stages are mapped to Zoho Stage values in the configured sales pipeline. We pre-create the Zoho pipeline layout during schema design with stage names matched to the customer's SendPulse stage names. Closed-won and closed-lost outcomes are preserved with closing date migrated to Closed_By_Date.

SendPulse CRM Tasks map to Zoho CRM Tasks. Title, due date (SendPulse Due_Date to Zoho SEVTASK due date), status, priority, and description migrate directly. SendPulse task assignment (linked contact, linked company) maps to Zoho's Related_To lookup pointing at the Contact or Account record. Completed status in SendPulse maps to Zoho Task Status = Completed. Overdue flag is preserved as a custom field or Task status.

SendPulse Mailing Lists define the segmentation group for a campaign audience. We treat these as Zoho Campaigns (Campaign_Name = SendPulse mailing list name, Campaign_Type = Email) and optionally as Zoho Lists for audience segmentation. The mailing list-subscriber membership migrates as Campaign Member records linking each Subscriber Lead to the Campaign. This preserves the audience grouping for future email campaigns in Zoho Campaigns or Zoho Email Templates.

SendPulse campaign performance data (open rate, click rate, bounce data, unsubscribe rate) migrates as custom fields on the corresponding Zoho Campaign record. We create custom fields sp_open_rate__c, sp_click_rate__c, sp_bounce_rate__c, and sp_unsubscribe_rate__c on the Campaign object. Individual subscriber engagement (opened, clicked, bounced) migrates as Campaign Member Status and custom fields on each Campaign Member record. This gives the customer historical performance context without a native SendPulse reporting connection.

SendPulse CRM Products map to Zoho CRM Products. Product name, SKU (mapped to Product_Code), unit price, and category migrate directly. SendPulse product images are not natively supported in Zoho Products; we store the image URL as a custom text field sp_product_image_url__c on the Product record. Customers that use SendPulse Products for a product catalog can maintain image links via this field.

SendPulse Products store hidden String or Number integration fields (up to 255 characters) used for POS IDs and payment gateway mapping. These fields are not visible in the standard product export UI and are not in the public API schema. We access them via a targeted API call with the integration_fields parameter, then create matching custom fields in Zoho CRM on the Product layout. This step is not automatic and must be explicitly requested during scoping. The customer should confirm whether integration field values are needed in Zoho or can be retrieved from the source POS system directly.

SendPulse verified sender email addresses are tied to SendPulse's SMTP infrastructure. They cannot be transferred to Zoho CRM directly. We document each verified sender address during export and provide a setup checklist for re-verification in Zoho Mail (if the customer uses Zoho Mail) or for configuring a third-party SMTP in Zoho CRM's email settings. Sender addresses are not imported as data records; they are re-verified post-migration in the destination platform's email configuration.

SendPulse Automation 360 flows define multi-step triggered sequences for CRM actions (e.g., task creation when a deal stage changes, email trigger when a contact is added). SendPulse does not expose flow definitions via API or bulk export. We document each active flow from screenshots and step descriptions taken during the export phase, then provide a written inventory with a recommended Zoho Workflow equivalent. The customer's Zoho admin rebuilds the workflow in Zoho. Complex flows with multiple branches and conditional logic require additional configuration time outside the migration scope.

SendPulse CRM Owners map to Zoho CRM Users. We resolve by email match. Any SendPulse Owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision the Zoho user account before record import proceeds. Owner-less records (e.g., tasks assigned to no one) are assigned to the Zoho admin user or held for the customer to assign manually. User provisioning is a pre-migration step validated before the main migration run.