Migrate from SendPulse to Microsoft Dynamics 365 Sales

SendPulse CRM Contacts map directly to Microsoft Dynamics 365 Sales Contact. Email address is the primary deduplication key. First name, last name, phone, and custom properties map to typed Dynamics fields. Any subscription status or unique-subscriber billing flag from SendPulse is preserved in a custom field sp_subscription_status__c for re-segmentation if the customer later implements marketing automation. Mobile and social fields map to Dynamics telephone and social-profile fields where available.

SendPulse Companies map to Microsoft Dynamics 365 Sales Account. Company name is the primary key, and the company domain maps to Account Website. The company-contact linkage is preserved via the Contact's parentcustomerid field pointing to the Account. We create the Account record before importing Contacts so that the parent Account lookup is satisfied at the moment of Contact insert.

SendPulse Deals map to Microsoft Dynamics 365 Sales Opportunity. The SendPulse pipeline becomes a Dynamics Record Type on Opportunity, and SendPulse deal stages map to Opportunity Stage values under a corresponding Sales Process. Deal value, responsible owner, and stage timestamps transfer directly. Closed-Lost and Closed-Won dates from SendPulse map to Dynamics CloseDate and a custom loss-reason field.

SendPulse CRM Tasks map to Dynamics 365 Task records linked via the Regarding field to the parent Contact, Account, or Opportunity. Task subject, due date, assignee, status, and priority transfer directly. We resolve the SendPulse responsible user to a Dynamics User record by email match during import.

SendPulse CRM Products map to Dynamics 365 Product records with name, price, SKU, and category. We access SendPulse's hidden integration fields (POS IDs, payment gateway metadata stored in String or Number fields up to 255 characters) via the targeted API call with the integration_fields parameter and write them as custom properties on the Dynamics Product record. This step must be explicitly requested during scoping.

SendPulse Subscribers from the email marketing module are not identical to CRM Contacts — a subscriber may have provided an email without full contact details. We deduplicate by email address, create CRM Contacts for subscribers with full name data, and create Leads for partial records (email-only). Subscription status (active, inactive, unsubscribed) is preserved in a custom field sp_email_status__c on the target record.

SendPulse Automation 360 flows define multi-step triggered sequences across email and SMS channels with conditions, actions, and delay steps. There is no API endpoint or bulk export for flow definitions. We document the flow structure from screenshots and step-by-step screenshots, map each trigger and action to a Power Automate equivalent, and deliver the inventory to the customer's admin for manual rebuild. Complex flows with multiple branching conditions may require significant reconfiguration in the destination.

SendPulse Chatbots for Telegram, Facebook Messenger, Instagram, WhatsApp, TikTok, and Viber have flow logic, trigger conditions, and message content that are not API-exportable. We document the chatbot configuration as-is from the SendPulse UI and deliver a written reconstruction guide. The customer rebuilds chatbot flows in Microsoft Copilot Studio, Power Virtual Agents, or a third-party conversational AI platform of their choice. This is outside data migration scope.

SendPulse email campaign results (open rates, click rates, bounce data, unsubscribes) are exported as reporting records and attached as Notes to the relevant Contact or Account in Microsoft Dynamics 365 Sales . Email delivery statistics should be treated as approximate, not definitive, because SendPulse applies content moderation that makes historical delivery outcomes uncertain. We flag this in the migration report.