Migrate from SendPulse to HighLevel

SendPulse CRM Contacts migrate 1:1 to GoHighLevel Contacts. The email, phone, first name, last name, and custom properties transfer directly. We map SendPulse's contact status (Active/Inactive) to GoHighLevel's contact status. Any custom properties unique to the customer's SendPulse setup are created as Contact Custom Fields in GoHighLevel before import. GoHighLevel supports both Contact Custom Fields (per-person data) and Opportunity Custom Fields (per-deal data); we determine which type during scoping based on property usage patterns.

SendPulse CRM Companies map to GoHighLevel Companies. The company name, website, address, phone, and associated contacts migrate. We preserve the company-contact linkage by resolving contact records after the Companies import so that each Contact carries the correct company_id reference in GoHighLevel. SendPulse's industry and employee count fields map to GoHighLevel Company custom fields if configured during scoping.

SendPulse Deals map to GoHighLevel Opportunities. The deal name, value, stage, responsible user, and custom fields migrate. SendPulse deal stages map to GoHighLevel pipeline stages, which we configure before migration. If the customer uses multiple SendPulse deal pipelines, we create corresponding GoHighLevel pipelines with unique stage sets. The deal responsible user resolves to a GoHighLevel User by email match; any unresolved owners go to a reconciliation queue.

SendPulse CRM Tasks migrate to GoHighLevel Tasks with title, due date, assignee, status, and linked contact/company preserved. Task assignment resolves by matching the SendPulse responsible user email to a GoHighLevel User. Linked contacts and companies are resolved after their respective imports complete. Task priority and status values are mapped to GoHighLevel's enumerated values.

SendPulse Mailing Lists are recreated as GoHighLevel Smart Lists using the same segment criteria. We extract the saved filter conditions (field, operator, value combinations) from each SendPulse mailing list during discovery and document them as Smart List filter definitions for GoHighLevel. The mailing list membership itself is a subset of the Contact records already imported; the Smart List filter applies those criteria at query time rather than storing a static list. If SendPulse uses a static mailing list (no dynamic criteria), we create a GoHighLevel Tag for each list and assign contacts accordingly.

SendPulse Subscribers (the email marketing recipient records) are mapped to GoHighLevel Contacts using email as the dedupe key. Subscriber variables (first name, last name, phone if present) merge into the corresponding Contact fields. Subscription status (subscribed, unsubscribed, bounced) migrates as GoHighLevel Contact tags and the HasOptedOutOfEmail flag. Unique subscriber count for SendPulse billing purposes does not carry forward — it is a platform-specific metric used only during the billing reconciliation before migration.

SendPulse verified sender addresses (SMTP senders) are documented during discovery and must be re-verified in GoHighLevel's Domain Connection settings before email sending begins. We provide a written step-by-step for the customer to add DKIM, SPF, and DMARC records for each sending domain in GoHighLevel. Historical campaign send-from addresses are preserved as metadata on Campaign Statistics records but do not affect GoHighLevel's sending configuration.

SendPulse email campaign performance data — open rates, click rates, bounce data, unsubscribe counts — is extracted as structured records and imported into GoHighLevel as custom Report entries linked to the sending Contact segment. GoHighLevel's native reporting does not have a campaign performance history import endpoint, so we use a custom object or tagged notes to preserve the historical metrics. This gives the customer's team a reference record for pre-migration campaign ROI without rebuilding SendPulse's analytics dashboard.