The former name of Copper CRM, a Google Workspace-native CRM that was rebranded in 2018 to better reflect its focus.
Full ReviewEnterprise CRM and ERP platform by Microsoft.
All Microsoft Dynamics 365 ToolsProsperWorks, now known as Copper CRM, is a CRM built natively for Google Workspace. It lives inside Gmail and Google Calendar, making it a natural choice for teams that run their business on Google tools. Microsoft Dynamics 365, by contrast, is deeply integrated with the Microsoft 365 ecosystem — Outlook, Teams, SharePoint, and Power Platform. When an organization has teams split across both ecosystems, connecting these two CRMs becomes essential.
This situation commonly arises in companies where different departments have adopted different productivity suites. A creative or marketing team might rely on Google Workspace and Copper CRM for its simplicity, while the enterprise sales or operations team uses Microsoft 365 and Dynamics 365. Mergers and acquisitions also create this split, where one company brings Google Workspace and the other brings Microsoft 365.
Whether you need to run both CRMs in parallel with synced data or migrate entirely from one to the other, a structured integration approach ensures no customer data falls through the cracks and both teams maintain visibility into shared accounts.
Copper CRM and Dynamics 365 use different terminology and structures. In Copper, you work with People, Companies, and Opportunities. In Dynamics 365, the equivalents are Contacts, Accounts, and Opportunities. Copper uses a flat, simple data model with custom fields for additional data. Dynamics 365 has a more complex relational model with entities, relationships, and business units. Map out how each Copper record type translates to Dynamics 365, including custom fields, pipeline stages, and activity types. Note that Copper's pipeline stages will need to map to Dynamics 365 opportunity stages or a custom status field.
In Copper CRM, navigate to Settings > Integrations > API Keys. Generate a new API key and save it securely. You will also need your Copper account email address for API authentication, as Copper uses email plus API key for its REST API. In Azure Active Directory, register a new application for the integration. Under API Permissions, add Dynamics CRM > user_impersonation. Generate a client secret and note your tenant ID, client ID, and client secret. Test both APIs independently using a tool like Postman to confirm connectivity.
Zapier offers native connectors for both Copper CRM and Dynamics 365, making it the easiest starting point. Create a new Zap and authenticate both accounts. If using Make, add a Copper CRM module and a Dynamics 365 module to a new scenario, authenticating each with the credentials from Step 2. For more complex workflows with branching logic, Tray.io provides advanced capabilities. Choose your platform based on the volume of records you need to sync — Zapier works well for low to medium volumes, while Make handles higher volumes more cost-effectively.
Create your first workflow to sync People from Copper to Contacts in Dynamics 365. Use the trigger "New or Updated Person" in Copper. Before creating a new contact in Dynamics 365, add a search step to check if a contact with that email already exists. If found, update the existing record; if not, create a new one. Repeat this pattern for Companies (Copper) to Accounts (Dynamics 365). For the reverse direction, create separate workflows triggered by Dynamics 365 record changes, with the same deduplication logic applied to Copper.
Map Copper Opportunity pipeline stages to Dynamics 365 Opportunity stages. Create a reference table for stage mappings (e.g., Copper "Qualification" = Dynamics "1 - Qualify"). Build a workflow to sync new and updated Opportunities from Copper to Dynamics 365. Include the associated Company/Account and Person/Contact lookups so opportunities maintain their relationships. Sync monetary values, expected close dates, and win probability. Handle currency formatting differences between systems if applicable.
If migrating entirely from Copper to Dynamics 365, export all data from Copper using its CSV export feature (Settings > Export Data). Export People, Companies, Opportunities, and Activities separately. Clean the CSV files, removing duplicate records and standardizing field values. Import into Dynamics 365 in order: Accounts first, then Contacts linked to Accounts, then Opportunities linked to Accounts and Contacts. Use the Dynamics 365 Data Import Wizard for smaller datasets or Azure Data Factory for large-scale migrations. After migration, run a data validation report comparing record counts and spot-checking key fields.
A tech company's SMB sales team uses Google Workspace and Copper CRM, while the enterprise team uses Microsoft 365 and Dynamics 365. When an SMB customer grows into an enterprise account, the contact and deal data syncs automatically from Copper to Dynamics 365. The enterprise rep picks up the full history without manual data entry.
After a merger, Company A (on Dynamics 365) acquires Company B (on Copper CRM). During a 6-month transition, bi-directional sync keeps both CRMs current. Shared accounts are visible to both teams. Gradually, Company B's team migrates to Dynamics 365, and Copper is decommissioned after full data transfer is validated.
The marketing team uses Google Workspace and tracks leads in Copper CRM. When a lead qualifies (reaches a specific pipeline stage), a Zapier workflow creates the lead in Dynamics 365 for the sales team. All further deal progression happens in Dynamics 365, with key updates pushed back to Copper so marketing maintains visibility.
A company decides to move from Microsoft 365 to Google Workspace. They export all Dynamics 365 contacts, accounts, and opportunities to CSV, clean the data, and import it into Copper CRM. Custom fields are recreated in Copper before import. Email history is preserved in Gmail through Google Workspace migration tools, and CRM data lives in Copper going forward.
Prosperworks Full Review » | All Microsoft Dynamics 365 Tools »
