Migrate from Copper to Microsoft Dynamics 365 Sales

Copper People records map to either Dynamics 365 Lead or Contact depending on the prospect's qualification status. We apply a split rule during scoping based on whether the People record has a related Copper Lead, a converted Lead link, or a status indicating active opportunity involvement. Unqualified prospects become Leads; qualified contacts become Contacts attached to the mapped Account. The original Copper contact status and any custom person-level properties migrate to custom fields on both Lead and Contact for audit and reporting continuity.

Copper Company records map directly to Dynamics 365 Account. The Company domain or website URL becomes the Account Website field and serves as the dedupe key during import. Account is provisioned before any Contact or Lead import so that the parent Account lookup is satisfied at the moment of record insert. We preserve the Company-Industry mapping to Account Industry, and any Company custom fields become Account custom fields.

Copper Opportunities map to Dynamics 365 Opportunity with Pipeline Stage mapped to the configured Sales Process stage. Closed-Won and Closed-Lost probabilities are set from the destination stage probabilities rather than carried from Copper, since Copper does not expose explicit probability values via API. Opportunity.Amount, CloseDate, and OwnerId resolve against the Account and User lookups created in earlier phases. We scope open Opportunities by default and document any closed deals included in the migration scope before extraction begins.

Copper pipeline stage names and order map to Dynamics 365 Sales Process stage categories. Each Copper pipeline becomes a separate Sales Process in Dynamics 365, and stage probabilities are set to match Copper's stage percentages rounded to the nearest integer. Dynamics 365 requires Sales Processes to be configured in the target environment before Opportunities are imported with stage values, so this phase precedes record migration.

Copper Lead records map directly to Dynamics 365 Lead. Copper's Lead_Status maps to the Dynamics 365 Lead Status field, and any lead score or grade values migrate to custom numeric fields. Leads without a matching Company in Copper map to Leads without an AccountName; Leads with a mapped Company resolve the AccountName on the Lead record during migration. We preserve the Lead creation date and owner from Copper for timeline accuracy.

Copper Tasks migrate to Dynamics 365 Task records with Status, Priority, and ActivityDate preserved. The task Subject maps to Task.Subject, Description maps to Task.Description, and the related People or Company reference resolves to the WhoId or WhatId on the Task. Open tasks are imported with their existing due dates; completed tasks carry their completion timestamp as ActivityDate. Assignee resolution follows the Owner reconciliation phase.

Copper Activities of type email map to Dynamics 365 EmailMessage records (body content) paired with a Task record for the activity timeline entry. Call activities map to Task with TaskSubtype=Call and duration stored in a custom field. Meeting activities map to Event with StartDateTime, EndDateTime, and Location preserved. The WhoId on each record links to the migrated Lead or Contact; the WhatId links to the related Opportunity or Account. Activity timestamps are preserved exactly from Copper to maintain timeline ordering.

Copper custom field definitions are enumerated via the Custom Field Definitions API during discovery. Each custom field is created as a new field in Dynamics 365 on the corresponding entity (Account, Contact, Lead, Opportunity, Task) with a type-mapped Dynamics 365 field type. Text fields map to Single Line of Text, numeric fields to Decimal or Whole Number, date fields to Date and Time, and checkbox fields to Two Options. Field labels and API names are preserved where possible, with __c suffix appended per Dynamics 365 convention. Validation rules on the target entity may require adjustment if they reference fields that Copper did not enforce.

Copper tags (flat labels applied to People, Companies, and Opportunities) migrate to a custom text field on the corresponding Dynamics 365 entity. If the customer has fewer than 20 distinct tags per entity, we map them to a Dynamics 365 Option Set for filterable reporting. Tags with high cardinality (more than 50 distinct values) are migrated as plain text in a custom text field and the customer decides on consolidation or tagging strategy post-migration.

Copper Projects have no direct equivalent in Dynamics 365 Sales. We migrate Projects as Accounts with a custom Account Type value of 'Project' to distinguish them from business Accounts. Associated Tasks migrate to Tasks with the WhatId pointing to the project Account. If the customer requires a distinct project object with budget, timeline, and milestone fields, we provision a custom Dataverse entity during schema design and map Projects there, with Tasks linked via the custom entity lookup.