Migrate from Symplify Communication to Microsoft Dynamics 365 Sales

Symplify Contacts map directly to Dynamics 365 Contact records. The Symplify originalId is preserved in a custom field symplify_original_id__c for deduplication and cross-reference. Email address is the dedupe key. All standard contact fields (name, email, phone, address) migrate 1:1. Subscription preferences (HasOptedOutOfEmail) migrate from Symplify Optout records. Hard bounce and soft bounce status migrate to a custom bounce_status__c field on Contact.

Symplify Contacts lack a native organizational affiliation field. During scoping, we identify whether the customer's use case requires Account creation from contact domain (extracting company from email domain) or whether the customer provides a company-to-account mapping file. If domain-based Account creation is used, we group contacts by email domain, create one Account per unique domain, and link all contacts within that domain to the parent Account. If contacts represent individual consumers rather than B2B accounts, we create individual Accounts per contact without domain grouping.

Symplify Lists are static contact groupings. Microsoft Dynamics 365 Sales does not have an equivalent static list object at the Contact level, but Marketing List (a standard entity in Sales Enterprise) serves this purpose for marketing-segmentation use cases. We export list membership and recreate lists as Dynamics Marketing List records. For sales-driven use cases where lists represent sales territories or account tiers, we map Lists to custom Account or Contact fields rather than Marketing List entities.

Symplify Campaigns do not map to Dynamics 365 Campaigns as 1:1 equivalents because Symplify tracks campaign-level metrics (open rate, click rate, bounce rate) as aggregate statistics rather than per-recipient records. We create a Dynamics Campaign record for each Symplify Campaign (preserving campaign name, start date, channel type), then link the Symplify Message recipients as CampaignMember records on the corresponding Dynamics Campaign. The aggregate metrics (total sends, opens, clicks) are stored as custom fields on the Campaign record. If the customer requires per-message historical metrics, we attach these as Notes on the Campaign.

Symplify Messages are individual sendouts within a campaign. Dynamics 365 Campaign Activity captures the send event and links it to the parent Campaign and target recipients (CampaignMembers). We map Message name, send timestamp, subject, and the per-message statistical fields (total sent, delivered, opened, clicked) as custom fields on the Campaign Activity record. Message body content is stored as an attachment or Note linked to the Campaign Activity.

Symplify engagement events (Opens, Clicks, Sents) have no direct CRM equivalent. Dynamics 365 tracks engagement through CampaignMember status transitions and Activity records. We map Symplify engagement events as follows: Sents become CampaignMember records with status Sent; Opens become CampaignMember status Updated (or a custom status); Clicks are captured as CampaignMember status with the clicked URL stored in a custom field. For detailed per-contact engagement history beyond campaign membership status, we create Note records linked to the Contact or Account that capture the timestamped engagement sequence (e.g., 'Opened email: Subject Line, 2024-03-15 14:32 UTC'). This preserves the engagement timeline in a human-readable format without requiring custom entities.

Symplify bounce records are merged into a single custom field bounce_status__c on the Dynamics Contact record. We set the field to Hard Bounce, Soft Bounce, or Clear (if the contact has no bounce history) based on the most recent Symplify bounce record for that email address. Hard bounce contacts are flagged with Do Not Email (emailoptout = true) to protect deliverability and compliance in Dynamics and any downstream email tools.

Symplify Optout records set the Dynamics Contact emailoptout field to true, ensuring unsubscribe preferences are honored immediately upon import. The timestamp of the optout event is stored in a custom field optout_date__c for audit and compliance. We do not land optout contacts as Marketing List members in Dynamics, preventing any email sends to suppressed addresses.

DataDocs store relational data (purchase history, events, bookings) linked to Symplify contacts by originalId. Each Symplify Document Type requires individual mapping. For DataDocs with simple field structures (5 or fewer fields, no nested JSON), we create a corresponding Dynamics custom entity with matching fields and link it to the Contact via a Lookup relationship. For DataDocs with complex nested JSON Schema or more than 10 fields, we store the DataDoc content as a structured Note on the Contact record with a reference to the originalId for reconciliation. Document Types without valid mandatory field definitions (originalId, externalId) cannot be migrated without customer remediation.