Migrate from SendPulse to Freshsales

SendPulse CRM Contacts map directly to Freshsales Contacts with name, email, phone, and custom properties preserved. SendPulse contact variables (first_name, last_name, email, phone, and any custom fields) map to Freshsales standard fields and custom contact fields. We deduplicate by email address during import to match SendPulse's unique-subscriber counting logic. Subscription status from SendPulse maps to Freshsales's email opt-out field.

SendPulse CRM Companies map to Freshsales Accounts. The company name becomes Account Name, and any associated address fields map to the standard billing address fields in Freshsales. Company-contact linkage is preserved as the Account-Contact relationship in Freshsales. We run the Accounts import before Contacts so that AccountId is available as a lookup reference at Contact insert time.

SendPulse Deals map to Freshsales Deals with name, value, stage, responsible user, and custom fields. Freshsales requires a Deal value (non-null), so we flag any SendPulse Deals with null or zero value during scoping and apply a customer-specified default (typically $0 or $1) before import. Deal stages map to Freshsales pipeline stages which we configure in Admin Settings before migration. The responsible user resolves via email match against Freshsales User records.

SendPulse CRM Tasks (title, due date, assignee, status, linked contact or company) map to Freshsales Tasks. The linked entity reference in SendPulse resolves to the migrated Freshsales Contact or Account ID. Task status (open, completed) maps directly to Freshsales Task status values. Tasks without a linked entity are imported as standalone tasks and flagged for manual reassignment.

SendPulse email Subscribers (recipient records with first name, last name, email, phone, and subscription status) map to Freshsales Contacts. The unique-subscriber count drives SendPulse billing; we count raw unique email addresses during migration scoping to establish the destination plan tier. Any duplicate email addresses within the same SendPulse account deduplicate to a single Freshsales Contact record. Subscription status (active, unsubscribed, inactive) maps to Freshsales email opt-out fields.

SendPulse Mailing Lists are segment definitions that group Subscribers for campaign targeting. Since Freshsales does not have an equivalent Mailing List object, we treat each SendPulse Mailing List as a Contact List in Freshsales and populate it by filtering the migrated Contacts by the email addresses present in the corresponding SendPulse list. Lists with complex conditions (behavioral triggers, date-based segments) are documented as segment logic for the customer's admin to recreate using Freshsales Filters.

SendPulse CRM Products (name, price, SKU, category) map to Freshsales Products. The hidden integration fields in SendPulse (POS IDs, payment gateway metadata stored as String or Number values up to 255 characters) are extracted via a targeted API call with the integration_fields parameter and written as custom properties on the corresponding Freshsales Product record. We flag this extraction step during scoping because it is not included in the standard UI export.

SendPulse email campaign results (open rates, click rates, bounce data, unsubscribes) are exported as CSV and imported into Freshsales as a custom reporting object or as notes attached to the corresponding Contacts. Freshsales does not have a native campaign statistics object, so these metrics serve as supplemental audit records. Historical delivery statistics should be treated as approximate because SendPulse's moderation queues may have suppressed some sends that appear as delivered in the export.