Migrate from Close to Microsoft Dynamics 365 Sales

Close Leads map directly to Dynamics 365 Lead. The Close status label (e.g. Potential, Contacted, Qualified) migrates to a custom Lead field close_original_status__c for audit. We set Lead.Status to a Dynamics 365 standard status value that most closely matches the original Close label, with a mapping table agreed upon during scoping. The close_date field maps to estimatedclose Date. Lead.OwnerId is resolved via email match against the destination User table.

Close Contacts require an Account parent in Dynamics 365. We first create Account records from Close Companies (or from the organisation field on Close Contact if no Company exists). Then we create Contact records linked to the resolved AccountId. Any Contact without an organisation in Close becomes a Contact linked to a placeholder Account, flagged for the customer admin to merge or resolve post-migration. The original Close contact ID migrates to a custom field close_contact_id__c for reconciliation.

Close Company records map to Dynamics 365 Account. The Company name becomes Account.Name, domain becomes Account.Website, and address fields map to Address composite fields. Account is created before any Contact import so that the AccountId lookup is satisfied at Contact insert time. We use Company.name as the dedupe key during Account creation to avoid duplicates from any overlapping Contact-level organisation entries.

Close Opportunities map to Dynamics 365 Opportunity. The pipeline-stage assignment maps to a Microsoft Dynamics 365 Sales Process and Record Type configured before migration. Opportunity.Amount migrates to EstimatedValue; close_date migrates to estimatedclose Date. If Close Opportunity is linked to a Contact (no Company), we resolve the Contact's parent Account and set AccountId before insert.

Each Close Pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from Close to the Dynamics 365 Stage Probability field. Stage ordering is preserved per the pipeline sequence in Close.

Close pipeline stages map to Dynamics 365 Stage values within the corresponding Sales Process. Stage names and display labels carry over directly. If Close has custom stage probability weights, these are set on the OpportunitySalesProcess entity after the Sales Process is deployed.

Close activity types split into Dynamics 365 equivalents: calls become Task with TaskSubtype=Call and CallDirection set; emails become Task plus an EmailMessage record; SMS notes become Task with a custom description field; tasks become Task directly. The parent reference (lead_id or contact_id) is resolved to the Dynamics 365 LeadId or ContactId before insert. ActivityDate preserves the original timestamp to maintain timeline ordering.

Close Custom Activities require a three-phase migration: create the Custom Activity Type as a Dataverse entity with its own logical name, create any type-scoped Custom Fields on that entity, then import the activity instances with a lookup to the parent Lead or Contact. The dependency chain is enforced strictly. If the destination org has no existing Dataverse custom entity for this type, we provision it during schema design. We flag any Custom Activity that uses a Custom Field not yet defined at migration time and halt that type's import until the field is created.

Close Custom Fields read via the API (type, choices, required flag) are created as Dynamics 365 custom attributes on the matching entity (Lead, Contact, Opportunity). Choice labels from Close become Option Set values in Dynamics 365. We preserve the Close field label and API name in the Dynamics 365 custom attribute display name for traceability. Required flags on Close map to Business Rules or field-level requirement in Dynamics 365.

Attachments on Close Leads and Contacts are retrieved via the API and re-uploaded to the destination as Note records linked via EntityImageId or as SharePoint document locations attached to the parent Account. The attachment file itself is preserved. We flag any attachment exceeding Dynamics 365 file size limits and resolve with the customer admin before migration.

Call recordings stored in Close are downloaded as audio files and re-uploaded as Note records attached to the matching Task activity in Dynamics 365. Recording duration and disposition from Close migrate to custom Task fields. We preserve the recording URL as a custom field reference if the customer intends to maintain a link to the original storage.

Close Users (name, email, role, team) map to Dynamics 365 User records resolved by email match. Role and team membership map to Dynamics 365 Security Roles and Teams, though we flag that internal permissions and Lead-sharing rules require post-migration admin review. Any Close Owner without a matching Dynamics 365 User goes to a reconciliation queue.