Migrate from Contlo to Microsoft Dynamics 365 Sales

Contlo Contacts map to Microsoft Dynamics 365 Sales Lead for unqualified records and Contact for qualified records attached to an Account. We assess the contact's lifecycle state, engagement score, and purchase history to determine the split. Contacts with purchase history or high engagement scores map to Contact under an Account; all others map to Lead. The original Contlo contact score and segment membership persist as custom fields (contlo_score__c, contlo_segments__c) on both Lead and Contact for audit and rebuild use.

Contlo Company records map directly to Microsoft Dynamics 365 Sales Account. The Company domain and address fields translate to Account Website and Address fields. Account serves as the parent of any Contact records that map to it. We deduplicate by Company domain name during import and flag any Company records without a domain for manual review.

Contlo behavioral segments are preserved as pipe-delimited tags in a custom text field contlo_segments__c on Contact and Lead. Segment rules (AND/OR filter conditions) are documented in a separate segment-mapping worksheet so the customer's admin can rebuild equivalent segments in Microsoft Dynamics 365 Sales using Advanced Find queries or Power Automate flows. Native Dynamics 365 Marketing segments (if the customer licenses that module) are documented as a future-state option.

Contlo Deals map to Microsoft Dynamics 365 Sales Opportunity. Deal stage maps to Opportunity StageName; Deal amount maps to EstimatedRevenue. If the Contlo Deal has an associated Company, we resolve that as AccountId on the Opportunity at migration time. Closed-won Deals become Closed Won Opportunities; closed-lost Deals become Closed Lost with a Loss Reason populated from Contlo custom fields if available.

Contlo campaigns with template content and delivery history map to Microsoft Dynamics 365 Sales Campaign records. Campaign Member status (Sent, Delivered, Opened, Clicked) migrates as CampaignMember records linked to the relevant Leads and Contacts. Template content (subject lines, body HTML) is preserved in a Notes attachment on the Campaign record so the customer's admin can reference it when rebuilding in Dynamics 365 Marketing or a third-party email tool.

Contlo email engagement records migrate to Microsoft Dynamics 365 Sales EmailMessage (the email content) linked to a related record (Lead, Contact, or Account) with an Activity Task for the timeline. Open and click event data from Contlo are stored as custom fields on the EmailMessage record because Microsoft Dynamics 365 Sales does not natively track engagement micro-events at the email level. The original timestamps are preserved in the ActivityDate field.

Contlo call engagements map to Microsoft Dynamics 365 Sales Task with Subject indicating Call, TaskType or custom call fields capturing direction (inbound/outbound), duration, and disposition. Call recording URLs stored as custom fields on the Task if the customer wants to preserve links. Original call timestamps map to ActivityDate.

Contlo custom fields on Contacts and Companies migrate to custom fields on Microsoft Dynamics 365 Sales Contact, Lead, and Account. Field types are mapped: text to Text, number to Whole Number or Decimal, date to Date, checkbox to Two Options. Picklist values from Contlo migrate to Option Sets in Dynamics 365 with the original labels preserved. If a custom field has no direct Dynamics 365 equivalent, we store the value as a JSON blob in a catch-all text field and document the mapping for the customer's admin to split out post-migration.