Migrate from Clarify CRM to Microsoft Dynamics 365 Sales

Clarify's flat Contact records with company linkage map to Dynamics 365 Contact records linked to Account records via the parentcustomerid lookup. We first create Account records from Clarify Company data (using Company name as the Account Name and Company domain as Website), then create Contact records with the resolved AccountId. Any Clarify Contact without a linked Company becomes a standalone Contact with no Account, which we flag for the customer to either link to an existing Account or create one. Lifecycle stage information from Clarify preserves in a custom field on Contact.

Clarify Company records map directly to Dynamics 365 Account. The Company domain becomes the Account Website field and is used as the deduplication key during import. AI-populated company details (industry, employee count, revenue) migrate as-is but are flagged in the validation report because Dynamics field validation rules may enforce required formats or picklist constraints that Clarify does not.

Clarify Deals map to Dynamics 365 Opportunities. The Deal stage maps to a Dynamics Sales Process stage (we pre-create a Sales Process matching Clarify's pipeline stage sequence). Close date, deal value, and owner information migrate directly. Any deal without a linked Company becomes an Opportunity without an Account, which we flag in the reconciliation report because Dynamics sales processes typically expect Opportunity.AccountId to be populated.

Clarify's configurable pipeline stages map to Microsoft Dynamics 365 Sales Process stage values. We capture the full stage sequence during discovery, create a corresponding Dynamics Sales Process in the destination org, and set stage probability percentages on each stage. If Clarify uses custom stage names, we create matching stage values in Dynamics rather than renaming to Dynamics defaults, preserving the customer's pipeline vocabulary.

Clarify's unified activity feed splits into Dynamics 365's typed activity objects. Phone calls map to Task with TaskSubtype=Call. Emails map to EmailMessage records linked to Tasks. Meetings map to Event with StartDateTime, EndDateTime, and Location preserved. Notes map to Note records. All activity records receive WhoId (Contact lookup) and WhatId (Opportunity lookup) references resolved from the parent Contact and Deal during migration.

Clarify's autonomous meeting summaries are stored as enriched note content attached to activity records, not as first-class structured objects. We export the summary text and attach it as a Dynamics 365 Note (annotation) linked to the corresponding Event record. The summary does not map to a structured Dynamics field because Microsoft Dynamics 365 Sales does not have a native meeting-summary property; the customer admin can optionally create a custom text field to receive these if desired.

Clarify's tag-based labeling migrates to Dynamics 365 Categories attached to records via the CategoryId lookup if the destination org has the Category feature enabled. If Categories are not in use, we create a custom multi-select picklist field on Contact and Opportunity to preserve tag assignments. The customer chooses the tag strategy during scoping based on how their Dynamics admin intends to use labels.

Clarify custom fields on Contacts, Companies, and Deals migrate to custom fields on the corresponding Dynamics 365 entity. We validate field types during discovery: Clarify multi-select values require Dynamics multi-select picklist; date fields require Dynamics DateTime or Date; currency fields require Dynamics Currency. Any type mismatch is flagged and corrected in the transform layer before import to avoid Dynamics validation rule rejection.