Migrate from Clientify to Microsoft Dynamics 365 Sales

Clientify Contact records map directly to Dynamics 365 Sales Contact. Standard fields (FullName, Email, Phone, MobilePhone, JobTitle) migrate 1:1. The clientify lifecycle stage property maps to a custom field cly_lifecycle_stage__c on Contact since Dynamics 365 Sales does not have a native lifecycle stage concept. Contact requires an AccountId parent link; we resolve the parent Company from Clientify and create or match the Account record before Contact insert.

Clientify Company records map to Dynamics 365 Sales Account. The clientify industry, number of employees, annual revenue, and address fields map to their Dynamics 365 equivalents (IndustryCode, NumberOfEmployees, AnnualRevenue, Address1_*). Account is created before Contact import so that the AccountId lookup is satisfied on insert. Domain name from Clientify becomes the Account Website field and is used as the dedupe key.

Clientify Lead records (distinct from Contact in Clientify) map to Dynamics 365 Lead. Lead status from Clientify maps to Dynamics 365 Lead StateCode and StatusCode. Any lead score value from Clientify's AI scoring migrates to a custom field lead_score__c. The customer's admin reviews the Lead-to-Contact convert mapping post-migration since lead qualification criteria differ between platforms.

Clientify Deal records map to Dynamics 365 Sales Opportunity. Deal name maps to Opportunity Name, deal value maps to EstimatedRevenue, and expected close date maps to EstimatedCloseDate. The Clientify deal stage maps to the corresponding StageName in the configured Sales Process. OwnerId resolves by email match to the Dynamics 365 User record.

Clientify pipeline stage names and ordering are read from the export and replicated as StageName values within a Dynamics 365 Sales Process. Probability percentages from Clientify map to StageProbability on each stage. If Clientify uses multiple pipelines, we create multiple Sales Processes or Record Types in Dynamics 365 to preserve the multi-pipeline structure.

Clientify activity records (logged calls, emails, meeting notes, tasks) map to Dynamics 365 Task and EmailMessage entities. Activity type label and timestamp format are normalized to match Dataverse conventions. The regarding_objectid on each activity links to the parent Contact, Account, or Opportunity record by resolving the original Clientify record ID through the mapping table created during scoping.

Clientify custom fields on Contact, Company, and Deal map to Dynamics 365 custom fields. We pre-create the destination schema including all custom fields, field types, and picklist value sets before migration begins. Any picklist-based custom property in Clientify requires pre-creation of the corresponding option set values in Dynamics 365 or the import fails for those records. Required-field flags and validation rules are reviewed with the customer's admin before activation.

WhatsApp conversation metadata (timestamps, participant IDs, message count, thread length) attached to Clientify Contact records migrates to a custom Dataverse entity we create for WhatsApp activity. Full message body export depends on Clientify's API availability at migration time; if the complete thread is not exportable via API, we preserve available metadata and note the gap. Media attachments, delivery receipts, and read receipts require separate documentation. Dynamics 365 Sales does not have native WhatsApp support; the customer may configure a Power Automate flow or third-party connector post-migration to reactivate live WhatsApp sync.

Clientify contact tags migrate to Dynamics 365 Sales as multi-select picklist values on the Contact record. Segments built from dynamic filters in Clientify do not transfer as logic; we export the segment membership list (which contacts qualified) and the customer chooses whether to store segment membership as a static Marketing List in Dynamics 365 or as a custom picklist field. The segment rebuild as dynamic logic requires manual recreation in Dynamics 365 Marketing or a Power Automate flow.

Clientify marketing campaigns with open rates, click rates, and send volumes migrate to Dynamics 365 Sales Campaign records as static performance data. The campaign execution logic (A/B test conditions, trigger schedules, automation rules) lives in Clientify's campaign builder and cannot be extracted; we document the campaign parameters (subject, send date, audience size, aggregated metrics) for the customer's marketing team to reconstruct in Dynamics 365 Marketing or their chosen email platform.

Clientify user records (name, email, role) export for mapping to Dynamics 365 User. We resolve each Owner by email match against the destination org's User table. Any Clientify Owner without a matching Dynamics 365 User is held in a reconciliation queue until the customer's admin provisions the User account. Role and team structure from Clientify require manual reconfiguration in Dynamics 365 Security Roles and Teams post-migration.