Migrate from CINC to Microsoft Dynamics 365 Sales

CINC Lead maps directly to Dynamics 365 Lead. The lead's firstname, lastname, email, phone, and address fields map to the corresponding Lead attributes. Owner resolution by email match identifies the Dynamics User. CINC leadscore maps to new_leadscore__c custom field on Lead.

CINC's numeric engagement_score has no native Dynamics equivalent. We create a custom integer field (new_leadscore__c) on the Lead entity. Historical engagement data from CINC's behavioral events also preserved in a custom Lead_Behavior_History__c table linked by LeadId. The custom table is created in Dataverse and the field added to the Lead form. Power Automate can later use this data for scoring recalculation.

CINC Company maps to Dynamics 365 Account. Company name maps to Account.Name, domain/website maps to Account.Website, industry maps to Account.Industry via value-mapping, and employee count maps to NumberOfEmployees. Parent-company hierarchy maps to Account.ParentAccountId. Physical address fields map to Address1_Line1, City, State, PostalCode, and Country. If the source includes a custom industry code, a new_industrycode__c field is created in Dynamics.

Agent and representative records in CINC that are people associated with a Company map to Dynamics 365 Contact. The Contact's AccountId lookup is set by resolving the CINC company relationship to the target Dynamics Account. Primary agent designation preserved as a custom field.

CINC Deal records—representing transaction commissions or listing deals—map to Dynamics 365 Opportunity. Deal name maps to Opportunity.Name, amount maps to Amount, close date maps to CloseDate, and stage maps to StageName via value-mapping against the configured sales process. Probability values are set from Dynamics default stage probabilities. Owner resolution follows email-to-User matching, similar to Lead migration.

CINC deal stages (e.g., 'Active', 'Under Contract', 'Closed Won', 'Lost') map value-by-value to Dynamics Opportunity StageName pick-list. Each CINC pipeline maps to a Dynamics Sales Process. Probability values re-applied from Dynamics side since CINC stage probability is not a standard field.

CINC engagement events (calls, emails, texts, meetings) migrate as Dynamics 365 Activities. Calls and tasks map to the Task entity with Type='Phone Call'. Emails map to Email entity. Meetings map to the Appointment (Event) entity. Original timestamps, subject, and owner preserved on each activity.

CINC links Leads to property listings via an N:M association. Dynamics 365 Sales has no native listings object. We create a custom LeadPropertyListing__c junction table (or custom lookup field) to preserve these associations. The Dynamics admin can add the field to the Lead form for reference.

CINC owner_id references a CINC User record. We resolve each owner by email against Dynamics 365 SystemUser table. Matched owners become OwnerId on the target record. Unresolved owners flagged before migration—team either creates a Dynamics user or assigns records to a fallback owner.

Any CINC custom properties beyond standard fields require a new_* custom field created in Dynamics 365 before migration. Field type mapping: text strings map to Text, numbers to Integer or Decimal, dates to Datetime, pick-lists to Option Sets. We deliver a custom field creation manifest as part of the pre-migration schema plan.

CINC automated sequences, AI lead routing rules, and behavioral triggers have no Dynamics 365 equivalent in the migration payload. We export CINC workflow definitions as structured JSON for your Dynamics admin to reference when rebuilding equivalent logic in Power Automate or Dynamics Sales Insights.

CINC file attachments associated with Leads or Deals migrate to Dynamics 365 native note attachments (Annotation entity). Large files re-upload to the connected SharePoint document library if the Dynamics environment has SharePoint integration enabled. File size limit is 128MB per note attachment in Dynamics.