Migrate from Zymplify to Microsoft Dynamics 365 Sales

Zymplify Contacts are a unified object with enrichment provenance and role data. Dynamics 365 requires a split decision during scoping: prospects with no sales interaction map to Lead; active buyers with open Deals or previous engagement map to Contact attached to an Account. We define the split rule using Zymplify's engagement history and Deal association as the qualifying criteria, then apply it as a transform during import. Original Zymplify contact source and enrichment provenance carry as custom fields on the destination record.

Zymplify Company records map directly to Dynamics 365 Account. The Company domain name becomes the Account Website field and is used as the dedupe key during import. All Zymplify intent scores (Bombora signals, G2 Buyer Intent spike data) and the original enrichment source list migrate as custom fields on the Account record. No native Dynamics 365 object stores third-party intent metadata; we treat intent signals as enrichment provenance rather than native CRM data and carry them explicitly as custom Account fields with the source system identifier.

Zymplify Deals map to Dynamics 365 Opportunity. Deal stage names migrate to a Sales Process configured in Dynamics 365 before migration; we create a Record Type per Zymplify pipeline to scope stage values per business line. Owner assignment resolves via email match to the Dynamics 365 User table. Closed-Lost and Closed-Won deal outcomes carry as custom Opportunity fields if they are present in Zymplify.

Each Zymplify pipeline with its custom stage names maps to a Dynamics 365 Record Type with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate to the Sales Process StageProbability field. We configure this schema in a Dynamics 365 Sandbox before production migration begins.

Zymplify Sales Cadences are multi-step outreach sequences combining email steps, delays, tasks, and conditional branches. Microsoft Dynamics 365 Sales does not include Sequences in the base Sales Professional or Enterprise tiers; Sequences require the Sales Engagement add-on ($50/user/mo additional). We export the cadence structure as a sequence definition document listing step order, step type, delay duration, recipient criteria, and task actions. The customer's Dynamics admin rebuilds cadences in Sales Engagement or a third-party sales engagement platform post-migration.

Zymplify customer health scores and churn risk indicators are Zymplify-native calculations without a direct Dynamics equivalent. We export the raw health signals and composite score as custom fields on the Account record (e.g., zd_health_score__c, zd_churn_risk_tier__c). The scoring model itself does not migrate; we document the calculation logic in a requirements spec so the customer's data team can rebuild an equivalent model in Dynamics 365 or Power BI.

Zymplify's CDP hub tracks enrichment status, deduplication decisions, and data provenance across contact and company records. We carry the cleansed contact and account data as standard fields in Dynamics 365 and flag the enrichment source as a custom field (e.g., zd_enrichment_source__c, zd_last_enriched_date__c). Source-of-truth provenance is preserved for audit purposes but enrichment decisions do not translate to native Dynamics objects.

Zymplify custom fields migrate to Dynamics 365 custom fields on the corresponding entity. We discover the full custom field inventory during the discovery phase, map field types (text to Text, number to Number, date to DateTime, checkbox to Two Options), and deploy the custom field schema to a Sandbox before production import. Lookup relationships between Zymplify custom objects require pre-creation of the relationship in Dynamics 365 metadata.

Zymplify users map to Dynamics 365 Users resolved by email match. Role-based access information and hub assignments carry as custom fields on the User record (e.g., zd_hub_assignment__c) since Dynamics 365 uses a different permission model (Security Roles and Business Units). Owners without a matching Dynamics User go to a reconciliation queue for admin provisioning before record import.

Zymplify tags applied to Contacts and Companies migrate to a Dynamics 365 text field storing comma-separated values, or to a global Option Set if the tag taxonomy is fixed and under 150 values. We document the full tag taxonomy during discovery and recommend a tagging strategy during scoping; Dynamics 365 native tagging (regarding) is a separate configuration.