Copper to Dynamics 365 migration
We migrate People, Companies, Opportunities, Leads, Activities, and Custom Fields from Copper into Microsoft Dynamics 365 Sales, resolving the Lead-versus-Contact split upfront, mapping pipeline stages to Sales Process stages, and re-linking Google Drive attachment references to SharePoint or OneDrive so that historical records remain intact at cutover.
FlitStack AI migrates lead or contacts, accounts, opportunities, sales process + stages and leads from Copper to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-8 weeks.

What moves from Copper to Dynamics 365?
Migrating from Copper to Microsoft Dynamics 365 Sales is a structural shift from a Google Workspace-centric CRM with a flat People-and-Companies model to a hierarchical Dataverse-backed platform that separates Leads from Accounts and Contacts.
Read the full summary
Copper treats People as the primary contact object; Dynamics 365 treats Leads as the unqualified-prospect entry point that must be converted into Account and Contact records. We resolve that split during scoping by applying a qualification rule based on Copper's Lead Status and People relationship fields. Pipeline stages migrate as Dynamics 365 Sales Process stages with probability values. Activity history (emails, calls, meetings) transfers to Dynamics 365 EmailMessage, Task, and Event records. Workflows, bulk email sequences, and Zapier automations do not migrate; we deliver a written inventory of every automation requiring rebuild in Dynamics 365 Sales, Power Automate, or Azure Logic Apps. Attachment files stored in Google Drive require separate file migration to SharePoint or OneDrive before re-linking to Dynamics 365 records.
People → Lead or Contact (split required)
Copper People records map to either Dynamics 365 Lead or Contact depending on the prospect's qualification status.
How it maps
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.
Companies → Account
Copper Company records map directly to Dynamics 365 Account.
How it maps
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.
Opportunities → Opportunity
Copper Opportunities map to Dynamics 365 Opportunity with Pipeline Stage mapped to the configured Sales Process stage.
How it maps
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.
Pipeline → Sales Process + Stage
Copper pipeline stage names and order map to Dynamics 365 Sales Process stage categories.
How it maps
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.
Leads → Lead
Copper Lead records map directly to Dynamics 365 Lead.
How it maps
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.
Tasks → Task
Copper Tasks migrate to Dynamics 365 Task records with Status, Priority, and ActivityDate preserved.
How it maps
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.
- PeopleLead or Contactsplit
- CompaniesAccount1:1
- OpportunitiesOpportunity1:1
- PipelineSales Processtransformed
- LeadsLead1:1
- TasksTask1:1
+ 4 more in the mapping below
How Copper and Dynamics 365 differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Copper | Dynamics 365 |
|---|---|---|
| Contact model | People as primary contact object with Company linkage | Separate Lead (unqualified) and Contact (qualified, tied to Account) objects with explicit Convert action |
| Pipeline architecture | Customizable stages per pipeline, editable directly on Opportunities | Sales Process stages tied to Record Types with pre-defined stage categories and probabilities |
| Custom objects | Not natively supported; extended via custom fields on standard objects | Full custom entity support on Dataverse from all paid tiers |
| Attachment storage | Files stored in associated Google Drive; links are Drive references | SharePoint or OneDrive document management; requires file re-hosting and re-linking |
| Pricing model | Per-seat with contact limits gating Starter ($9) and Basic ($23) tiers | Per-user Base CAL or Full CAL; unlimited contacts at all tiers |
| Workflow automation | Workflow automation gated at Professional ($59) tier; basic task automation at Basic | Power Automate and Dynamics 365 workflow from all tiers; Sales automation features vary by license type |
| AI and intelligence | AI-assisted email rewriting on higher tiers; limited scoring | Copilot for Sales, conversation intelligence, and opportunity scoring included with Full CAL |
What to watch for in a Copper to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Lead-Contact split requires qualification rule design before migration
Copper treats People as the primary contact record regardless of qualification status, while Dynamics 365 requires unqualified prospects to enter as Leads and convert into Account and Contact pairs.
How we handle it
There is no automated rule that correctly routes every Copper People record without explicit business logic from the customer. We define the split rule during scoping by reviewing the customer's Copper Lead records, People status fields, and opportunity involvement history. Records designated as Leads in Copper become Dynamics 365 Leads; all other People become Contacts attached to the mapped Account. Skipping this design step produces Contacts with no parent Account (orphaned records) or Leads for prospects who should have been converted immediately on day one.
Dynamics 365 pipeline stages require pre-configuration before Opportunity import
Copper allows pipeline stages to be edited directly on Opportunities at any time.
How we handle it
Dynamics 365 requires Sales Processes and Stage categories to be configured in the target environment before Opportunities with stage values can be imported. We configure the Sales Process stages during the schema design phase, mapping Copper stage names and probabilities to Dynamics 365 stage names and probability values. If the customer has multiple Copper pipelines, each becomes a separate Sales Process with its own stage category, and the Opportunity Record Type is assigned during migration. Without this pre-configuration, Opportunity imports either fail validation or land in a default stage that does not match the customer's process.
Attachment files live in Google Drive and require separate re-hosting
Copper stores file attachments in the user's associated Google Drive account.
How we handle it
Dynamics 365 uses SharePoint Online or OneDrive for Business document management by default. We cannot transfer file contents through the CRM API alone. During scoping, we enumerate all Copper records with attachment references, map the Google Drive file IDs, and coordinate a parallel Google Drive to SharePoint file migration. We then update the Dynamics 365 record's document location references to point to the new SharePoint URLs. Without this parallel track, attachment links become broken references at cutover. This is distinct from the CRM record migration and requires the customer's Google service account credentials and SharePoint destination library access.
Closed deal timestamps and stage history are not fully accessible via Copper API
Copper's API exposes the current pipeline stage on an Opportunity but does not provide a complete stage-change history with timestamps for closed deals.
How we handle it
When migrating Opportunities that have progressed through multiple stages, we import the current stage and set ClosedDate from Copper's close_date field. We flag any customer requirements for full stage history (such as time-in-stage analytics) and advise that stage transition logs do not transfer via API. Dynamics 365 Audit History can be enabled post-migration to capture future stage changes, but historical Copper stage progression is not retrievable through the API.
Inactive Copper owners need explicit User mapping before migration
Copper's owner system is email-based and does not distinguish active from inactive team members at the API level.
How we handle it
Dynamics 365 ties record ownership to Azure Active Directory User accounts, and records assigned to a User that does not exist or is inactive in the destination tenant fail to insert. We extract every distinct Copper owner from People, Company, Opportunity, Lead, and Activity records and match by email against the destination Dynamics 365 User table. Owners without a matching active User go to a reconciliation queue for the customer's IT or Dynamics 365 admin to provision before record migration proceeds. We do not default inactive owners to a generic system user without explicit approval because owner attribution is used for territory reporting and commission tracking.
How the migration runs
Discovery and scoping
We audit the Copper workspace across account plan tier, People count, Company count, Opportunity count and pipeline structure, Lead count, Task volume, Activity history volume, custom field definitions via the Custom Field Definitions API, and active tag taxonomy.
What this step covers
We cross-reference this with the destination Dynamics 365 environment: licensed user count, existing Account and Contact volume, active Sales Processes, and any existing custom entities. We produce a written migration scope that defines the Lead-Contact split rule, the Opportunity pipeline-to-Sales Process mapping, and the custom field translation matrix. This phase also includes a Google Drive attachment audit to scope the parallel file migration track.
Schema design and Dynamics 365 pre-configuration
We configure the destination Dynamics 365 environment before any records are imported.
What this step covers
This includes provisioning custom fields on Account, Contact, Lead, and Opportunity entities to receive Copper custom field values. We create Sales Processes matching each Copper pipeline with stage names and probabilities. We define Record Types on Opportunity if the customer requires separate page layouts per line of business. Schema configuration is deployed into a Dynamics 365 Sandbox environment first for validation by the customer's admin team. No records are written to production until schema is signed off.
Sandbox migration and reconciliation
We run a full migration into a Dynamics 365 Sandbox using production-like data volume extracted from Copper.
What this step covers
The customer's Dynamics 365 admin and RevOps lead reconcile record counts, spot-check field mappings on 25-50 random records, and validate that the Lead-Contact split rule produces the expected distribution. Any field mapping corrections, custom field type adjustments, or stage probability corrections are documented and applied to the production migration scripts. The sandbox sign-off is a required gate before production migration begins.
Owner reconciliation and User provisioning
We extract every distinct Copper owner referenced on People, Company, Opportunity, Lead, and Activity records and match by email against the destination Dynamics 365 User table.
What this step covers
Owners without a matching active User are listed in a reconciliation report with their email, record count, and record type. The customer's Dynamics 365 admin provisions missing Users in Azure Active Directory and assigns them to the appropriate Business Unit before production migration. Migration cannot proceed past record insertion until all owner references are resolvable.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Copper Companies), Leads (from Copper Lead records and the People split), Contacts (from Copper People records mapped via the split rule, with AccountId resolved), Opportunities (with AccountId, OwnerId, and Sales Process stage resolved), Tasks (with WhoId and WhatId resolved), Activities (EmailMessage, Task, Event via bulk insert with parent-record lookup), Custom Fields (as field values on each entity), Tags (as text or Option Set values).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Bulk API chunking and exponential backoff are used for activity records to stay within Dataverse API rate limits.
Cutover, validation, and automation handoff
We freeze Copper writes during the cutover window, run a final delta migration of any records modified during the window, then re-link SharePoint attachment URLs to Dynamics 365 record document locations.
What this step covers
We enable Dynamics 365 as the system of record and deliver the Workflow and Automation Inventory document listing every Copper workflow, Zapier trigger, and bulk email sequence that requires rebuild in Power Automate, Dynamics 365 Sales automation, or Azure Logic Apps. We support a one-week hypercare window for reconciliation issues. We do not rebuild Copper workflows as Power Automate flows as part of the migration scope; that work is a separate engagement or an internal admin task.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with total record count, custom field count, activity volume, and whether the customer needs parallel file migration from Google Drive to SharePoint. Dynamics 365 licensing costs (Base CAL or Full CAL per user) sit outside the migration fee and are the customer's recurring cost. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Copper to Dynamics 365 →Why teams move from Copper to Dynamics 365
- Copper's contact limits and feature gating push teams toward expensive upgrades mid-growth. Starter caps at 1,000 contacts, Basic at 2,500, and Professional at 15,000 with workflow automation and bulk email. Teams on Starter or Basic hit the contact ceiling or the automation wall without warning, forcing a tier jump that does not align with their actual seat count or feature usage. Microsoft Dynamics 365 Sales licensing carries no per-contact cap; per-user licensing with Base CAL or Full CAL covers all contacts at any volume, making the cost model more predictable as teams scale beyond 5,000 records.
- Teams requiring advanced AI for sales, conversation intelligence, and predictive forecasting find Copper's feature set insufficient for complex sales motions. G2 and Capterra comparisons note that Microsoft Dynamics 365 Sales includes Copilot for Sales, opportunity scoring, and pipeline intelligence built on the Dataverse data model without requiring an additional platform layer. Reviewers who moved from Copper to Dynamics 365 cite the depth of analytics and AI-driven insights as a primary driver, particularly for teams managing multi-stage enterprise deals.
- Organizations with existing Microsoft 365, Azure, Power Platform, or Teams infrastructure find Dynamics 365 provides tighter native integration than Copper's Google Workspace focus. Monday.com's CRM alternatives analysis explicitly notes that if an organization is not already invested in Google Workspace, the cost and complexity of Copper relative to what comes out of the box becomes difficult to justify. Teams using Outlook, Teams, SharePoint, and Power BI gain a unified data surface when Dynamics 365 is the CRM layer, reducing the context switching that Google-centric CRMs introduce for Microsoft-based teams.
- Copper's flat, minimal interface serves simple sales motions well but constrains organizations with complex territory management, multi-object reporting, or non-standard sales processes. Capterra and TrustRadius reviewers who switched to Dynamics 365 cite the need for deeper customization, multiple sales processes across business units, and custom objects that Copper does not support natively. Dynamics 365 on Dataverse allows custom entities, calculated fields, and Power Apps extensions without requiring a separate platform tier.
- Workflow automation, bulk email, and custom reporting are gated behind Copper's Professional ($59/seat) and Business ($99/seat) tiers. Teams that outgrow Starter or Basic and need these features face a significant per-seat cost jump before they have the usage data to justify the investment. Microsoft Dynamics 365 Sales includes workflow capabilities through Power Automate at all tiers, and Power BI for reporting is licensed separately but integrates natively with Dataverse, giving teams more control over their automation and analytics stack without tier-based feature gating based on contact count.
Questions, answered
Copper to Dynamics 365 migration questions
How long does a Copper to Microsoft Dynamics 365 Sales migration take?
Most migrations land between four and eight weeks for accounts under 10,000 People, 2,000 Opportunities, and a manageable custom field set. Migrations with large engagement histories (over 200,000 activity records), many custom fields, multiple Copper pipelines, or a complex Lead-Contact split matrix move to ten to sixteen weeks because of Sales Process pre-configuration time, Dataverse schema design, and parent-record resolution during bulk load. Timeline is also affected by how quickly the customer's Dynamics 365 admin provisions User accounts for Owner reconciliation and signs off the sandbox migration.
Do Copper workflows, bulk email sequences, and Zapier automations migrate to Dynamics 365?
No. Copper workflows and Power Automate or Dynamics 365 Sales automation are different automation models with different triggers, actions, and execution contexts. We do not migrate them as code. We deliver a written inventory of every active Copper workflow and Zapier integration with its trigger conditions, action sequence, and a recommended Power Automate or Dynamics 365 Sales automation equivalent. The customer's admin or a Microsoft partner rebuilds them post-migration. Bulk email sequences (email series or cadences) do not migrate; Dynamics 365 Sales does not include a native sales engagement cadence feature, so the customer selects and implements a sales engagement tool separately if cadence tracking is required.
Do we lose our email, call, and meeting history when migrating from Copper?
No. We migrate the full activity history through Dynamics 365 bulk insert operations. Emails land as EmailMessage records with body content and metadata; calls land as Task records with TaskSubtype=Call and call duration stored in a custom field; meetings land as Event records with start and end times, location, and attendee references. 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 from Copper to maintain timeline ordering for the sales team's historical reference.
Can we migrate Copper's Google Drive attachments to Dynamics 365?
Attachment metadata migrates as part of the CRM record migration, but the actual file contents require a separate file migration track. Copper stores files in Google Drive; Dynamics 365 uses SharePoint Online or OneDrive for Business by default. We coordinate a parallel Google Drive to SharePoint file migration during the engagement, verify file accessibility in the new location, and update Dynamics 365 record document references to point to the SharePoint URLs. This parallel track requires the customer's Google service account credentials with read access to the relevant Drive folders and SharePoint destination library write access. Without this step, attachment links become broken references at cutover.
How do we handle the Lead-Contact split when Copper does not separate unqualified and qualified contacts?
Copper's People object is the primary contact record regardless of qualification status, so there is no automatic split without an explicit business rule. During scoping we review the customer's Copper Lead records, People status properties, and opportunity involvement to define a qualification rule: for example, People records with a related Copper Lead, an active Opportunity, or a Lead_Status of 'Qualified' become Dynamics 365 Contacts; all others become Leads. We apply this rule as a pre-transform during extraction and preserve the original Copper status in a custom field on both Lead and Contact for post-migration reporting continuity. The customer's sales operations lead approves the split rule before extraction begins.
Can FlitStack AI also migrate our Google Workspace data to Microsoft 365 alongside the CRM migration?
Yes. Teams migrating from Copper to Dynamics 365 frequently transition from Google Workspace to Microsoft 365 at the same time. We can coordinate a parallel scope that includes Google Contacts migration to Dynamics 365 Contacts, Google Calendar events to Dynamics 365 Activities (as Event records), and Gmail email history to Dynamics 365 EmailMessage records. This parallel track is scoped separately from the CRM record migration and requires the customer's Google Workspace admin credentials and Microsoft 365 admin access. We do not migrate Google Drive to OneDrive as part of the CRM migration scope; that is a separate file infrastructure migration engagement.
What happens to our Copper data after migration is complete?
We do not delete or modify Copper data during migration. The Copper workspace remains intact and accessible during the entire migration process. We freeze writes to Copper during the cutover window to prevent delta records from accumulating, but we do not delete the source account. After cutover, the customer controls the Copper account lifecycle: they may keep it as a read-only archive, cancel the subscription, or export a final backup. We provide a complete record of all migrated record IDs and source Copper IDs for cross-reference if the customer needs to reconcile against the original workspace at any point.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Salesforce to Dynamics 365Mapping · history · rollbackMailchimp to Dynamics 365Mapping · history · rollbackZoho CRM to Dynamics 365Mapping · history · rollbackConvertkit to Dynamics 365Mapping · history · rollbackmonday CRM to Dynamics 365Mapping · history · rollbackSugarcrm to Dynamics 365Mapping · history · rollback Copper to HubSpotMapping · history · rollbackCopper to SalesforceMapping · history · rollbackCopper to Zoho CRMMapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Service protection limits (Microsoft Dataverse)
- Entity relationship behavior — Microsoft Learn
Get a quote
Moving from Copper to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote