---
title: "Civicrm to Dynamics 365 Migration: Field Mapping & Rollback"
description: "Migrate Civicrm to Dynamics 365 with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/civicrm/to/dynamics-365-sales"
---

# Civicrm to Dynamics 365 migration

We migrate Contacts, Activities, Contributions, Memberships, Cases, and Custom Fields from CiviCRM into Microsoft Microsoft Dynamics 365 Sales . The core challenge is modeling CiviCRM Activity-based engagement records into Dynamics pipeline objects, creating custom objects for nonprofit-specific Contribution and Membership data, and resolving per-case status scoping before any record is written to the destination.

Short answer

FlitStack AI migrates contact or leads, task and events, custom fields, connections and marketing list or teams from Civicrm 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.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/crm/civicrm/to/dynamics-365-sales#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Civicrm ![](https://flitstack.ai/platforms-trim/civicrm.webp)

Destination Dynamics 365 ![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp)

Contact or Lead Task and Event Custom Field Connection Marketing List or Team

Mapped field by field · sample run · one-click rollback

## What moves from Civicrm to Dynamics 365?

CiviCRM tracks engagement as Activities against a flat contact record; Microsoft Microsoft Dynamics 365 Sales uses Leads, Contacts, Accounts, and Opportunities with a structured pipeline model.

Read the full summary

There is no native Opportunity or pipeline concept in CiviCRM, so migrations require identifying which Activities represented informal deal tracking and reconstructing them as Opportunities with stage, amount, close date, and probability. Contributions and Memberships have no standard Dynamics equivalent; we create custom objects to preserve these nonprofit-native records. Relationships become Connections, Groups become Marketing Lists or Teams, and multi-record custom field sets require schema-aware custom object creation. ECK (Entity Construction Kit) entities with arbitrary custom schemas are handled as custom objects with explicit schema mapping.

1:N split

### Contact (Individual, Household, Organization) → Contact or Lead (split required)

CiviCRM Contact subtypes (Individual, Household, Organization) map to Dynamics Contact.

How it maps

We recommend mapping all CiviCRM Contacts to Dynamics Contact rather than splitting to Lead, because CiviCRM has no separate Lead object and organizations using CiviCRM typically track all contacts equally without a qualification gate. If the customer requires Dynamics Lead for an explicit sales qualification workflow, we define the split rule during scoping using contact properties such as source, activity count, or contribution history, and preserve the original contact record as a custom field on Lead for audit.

1:N split

### Activity → Task and Event

CiviCRM Activities (email, call, meeting, task subtypes) map to Dynamics Task and Event objects.

How it maps

Each Activity type routes to the corresponding Dynamics object: calls and tasks become Task records, meetings become Event records. The src\_contact\_id maps to WhoId, and the case\_id or parent\_case reference maps to WhatId pointing at the related Case. We flag Activities that represent informal deal or pipeline stages for Opportunity reconstruction separately during scoping.

1:1

### Custom Field (CustomValue / Custom\_\*) → Custom Field

Single-record custom groups attach as custom fields on the parent object using the custom.\* selector in APIv4.

How it maps

Multi-record sets appear as separate entities prefixed Custom\_ and become Dynamics custom objects with lookup relationships to the parent Contact or Case. We query both via API, reconstruct the multi-record cardinality, and create the corresponding custom object schema before import. Multi-record sets with more than 20 custom groups fall back to entity-by-entity exports to stay within MySQL join limits on the CiviCRM side.

1:1

### Relationship → Connection

CiviCRM Relationships (spouse, household member, employee, employer, and custom types) map to Dynamics Connection records with ConnectionRole matching the CiviCRM relationship\_type label.

How it maps

Both contact references (contact\_id\_a and contact\_id\_b) map to the Dynamics record1id and record2id Contacts. We preserve the relationship is\_active flag and start/end dates as custom fields on Connection since Dynamics Connections do not natively track activation periods.

configuration

### Group and GroupContact → Marketing List or Team

CiviCRM Groups map to Dynamics Marketing Lists (for contact segmentation and campaign targeting) or Teams (for access control and record sharing).

How it maps

We preserve the group hierarchy where it exists, flattening nested groups into a flat list annotated with parent group references. Dynamic (smart) groups that recalculate based on CiviCRM search criteria cannot be reproduced as static lists; we document the search criteria and recommend rebuilding as a Dynamics Marketing List with equivalent filter conditions or a Power Automate flow.

configuration

### Contribution → Custom Object (contribution\_custom)

CiviCRM Contributions (financial\_type, total\_amount, currency, receive\_date, payment\_instrument, check\_number, card\_type, trxn\_id) have no standard Microsoft Dynamics 365 Sales equivalent.

How it maps

We create a custom object contribution\_custom with fields matching the CiviCRM contributionfinancial\_type, total\_amount, currency, receive\_date, and payment\_instrument. Price sets introduce variable line-item complexity; we flatten price set fields to custom line\_item fields on the contribution\_custom record. The source contact\_id maps to a Contact lookup.

******What moves 11 objects

Civicrm Dynamics 365

- Contact Contact or Lead split
- Activity Task and Event split
- Custom Field Custom Field 1:1
- Relationship Connection 1:1
- Group and GroupContact Marketing List or Team transformed
- Contribution Custom Object transformed

\+ 5 more in the mapping below

## How Civicrm 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                | Civicrm                                                                            | Dynamics 365                                                                                   |
| ------------------------ | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Engagement model         | Activities attached to Contacts; no pipeline or deal object                        | Leads, Contacts, Accounts, Opportunities with pipeline stages and revenue tracking             |
| Contact model            | Single Contact with Individual/Household/Organization subtypes                     | Separate Lead and Contact objects with explicit Convert workflow                               |
| Custom objects           | Built-in via custom fields, multi-record sets, and ECK entity construction kit     | Requires explicit schema creation via Power Apps; available from Essentials tier ($70/user/mo) |
| Nonprofit-native objects | Contributions, Memberships, Grants, Events, Cases as first-class entities          | No native financial transaction, membership, or grant objects; custom objects required         |
| Pricing model            | Free open-source download; hosting and maintenance costs only                      | Per-user subscription at $50-$210/user/mo plus $25,000-$250,000+ implementation                |
| Workflow automation      | CiviRules extension plus PHP hooks; no native visual builder                       | Power Automate with 600+ connectors from Essentials tier; requires separate licensing          |
| API ecosystem            | REST API with session-key or API-key auth; no published rate limit for self-hosted | Dataverse Web API with \~6,000 req/300s per-user throttle; Azure-backed Graph API              |

## What to watch for in a Civicrm 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.

high

### CiviCRM has no Opportunity or pipeline object

CiviCRM does not have a deal, opportunity, or pipeline object.

How we handle it

Organizations using CiviCRM for any sales-adjacent work track pipeline stages as Activity subject lines, case references, or custom field values. There is no formal stage, probability, or revenue field. We identify these informal pipeline records during scoping by analyzing Activity subject patterns, custom field usage, and contribution records attached to contacts. Each identified pattern is either reconstructed as a Dynamics Opportunity with stage, amount, close\_date, and probability, or documented as a historical Activity that should not become a pipeline record. Migrations that skip this step lose all informal deal history.

high

### Dynamics API rate limit constrains export pacing

Microsoft Dynamics 365 Sales enforces a Dataverse Web API rate limit of approximately 6,000 requests per 300 seconds per user.

How we handle it

CiviCRM on a self-hosted instance has no published rate limit on its REST API, which makes pacing straightforward on the source side. During migration scoping, we run a burst test of 500 API requests against the Dynamics destination to confirm the effective throttle ceiling. We implement exponential backoff with Retry-After header reading and chunk our batch inserts to stay within the observed safe rate. For large activity migrations, we also use ExecuteMultipleRequest batch operations where supported, which counts as one request against the limit per batch rather than per record.

high

### CiviCase statuses are scoped per case\_type, not global

CiviCase defines statuses within each case\_type definition rather than as a global list.

How we handle it

The same status ID can represent different stages depending on which case\_type owns it. Dynamics uses a global Case Status picklist shared across all Case Record Types. During migration, we enumerate every active case\_type, extract its XML or PHP entityType status definitions, and build a per-type status map to the destination Case Status values. Mixing case\_type-scoped status IDs during import produces silent mis-assignments that are difficult to detect post-migration without manual record review.

medium

### Undocumented custom fields risk being missed

CiviCRM sites accumulate custom fields over time, and administrators may not be aware of the full inventory, particularly if multiple staff members have created fields without central documentation.

How we handle it

We scan all civicrm\_custom\_group and civicrm\_custom\_field database tables during scoping to produce a complete inventory, then cross-reference against the CiviCRM UI field list. Any custom field present in the database but not visible in the UI is flagged explicitly. Each identified custom field is mapped to either a Dynamics standard field (where semantic match exists) or a custom field created during schema design.

medium

### CiviRules and CiviCRM automations do not migrate to Power Automate

CiviCRM automated rules built with CiviRules, CiviRules Email Schedule, or custom PHP hooks have no direct Power Automate equivalent and do not migrate as code.

How we handle it

We deliver a written inventory of every active CiviRule, scheduled job, and custom PHP hook with its trigger, conditions, actions, and a recommended Power Automate or Power Apps substitute. The customer's Dynamics admin or a Microsoft partner rebuilds these post-migration. CiviRules are event-triggered and condition-evaluated differently from Power Automate record-triggered flows, so the inventory includes specific rebuild guidance rather than a direct translation.

## How the migration runs

1. ### Migration discovery and scoping

   We audit the source CiviCRM instance: CMS integration (Drupal, WordPress, Joomla, Backdrop), CiviCRM version, hosting type (self-hosted, CiviSpark), and API configuration.

   What this step covers

   We enumerate all active entities including contacts, activities, contributions, memberships, cases, events, grants, relationships, groups, tags, and any ECK entity types. We scan civicrm\_custom\_group and civicrm\_custom\_field tables for the full custom field inventory and identify multi-record sets that require custom object creation. We also identify activities that function as informal pipeline records by analyzing subject patterns and contribution context. For the destination, we confirm the Microsoft Dynamics 365 Sales edition (Essentials at $70/user/mo or Professional at $115/user/mo) and document which custom objects are required for nonprofit-specific data.

2. ### Schema design in Dynamics

   We design the destination schema before any data moves.

   What this step covers

   This includes creating custom objects for Contributions (contribution\_custom), Memberships (membership\_custom), Events (event\_custom), and Grants (grant\_custom) with all required fields, field types, and lookups. We create ECK entity schemas as custom objects where applicable. For contacts, we define the Lead-Contact split rule based on the customer's qualification workflow. For cases, we enumerate every case\_type and map its status options to global Dynamics Case Status values. We configure Marketing Lists or Teams for Groups. All schema is deployed to a Dynamics Sandbox first for validation before production deployment.

3. ### Sandbox migration and reconciliation

   We run a full migration into a Dynamics Sandbox using production-equivalent data volumes.

   What this step covers

   The customer reconciles record counts for each entity type against the source CiviCRM instance, spot-checks 25-50 records in each entity for field-level accuracy, and reviews the custom object data quality for Contributions, Memberships, and any ECK records. The customer signs off the schema and mapping before production migration begins. Any mapping corrections, field type adjustments, or status value corrections happen in sandbox, not in production.

4. ### Owner reconciliation

   We extract every distinct CiviCRM owner referenced on contact, activity, contribution, membership, case, and event records and match by email against the Dynamics destination User table.

   What this step covers

   Any CiviCRM owner without a matching Dynamics User goes to a reconciliation queue. The customer's Dynamics admin provisions any missing Users with appropriate security roles before production migration resumes. OwnerId references must be satisfied on all standard records before bulk import begins.

5. ### Production migration in dependency order

   We run production migration in dependency order with per-phase row-count reconciliation.

   What this step covers

   We respect the Dynamics API rate limit of approximately 6,000 requests per 300 seconds using exponential backoff and Retry-After header reading. The sequence is: Contact and Relationship records (with ConnectionRole lookups resolved), Cases (with per-type status map applied), Custom Objects for Contributions, Memberships, Events, and Grants (with parent Contact lookups resolved), Activities (Tasks and Events with WhatId resolved to Cases), then Tags. We run a delta migration after initial load to capture records modified during the migration window.

6. ### Cutover, validation, and rebuild handoff

   We freeze writes to CiviCRM during cutover, run a final delta sync, then enable Microsoft Dynamics 365 Sales as the system of record.

   What this step covers

   We validate sample records for each entity and flag data quality issues for customer review. We deliver the CiviRules, scheduled job, and PHP hook inventory with Power Automate rebuild recommendations to the customer's admin team. We offer a one-week hypercare window for reconciliation issues. We do not rebuild CiviRules as Power Automate flows inside the migration scope; that is a separate engagement.

![](https://flitstack.ai/platforms/civicrm.svg) Civicrm ![](https://flitstack.ai/platforms/microsoft-dynamics-365-sales.svg) Dynamics 365

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Dynamics 365 Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**4-8 weeks** Typical, smaller accounts

**12-20 weeks** Large or heavily customised accounts

A quote scales with record volume, custom object count, and relationship network complexity. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Civicrm to Dynamics 365 →](https://flitstack.ai/contact)

## Why teams move from Civicrm to Dynamics 365

- CiviCRM has no deal pipeline or Opportunity object; engagement tracking lives entirely as Activities attached to contact records. Microsoft Microsoft Dynamics 365 Sales provides native pipeline stages, deal amounts, close dates, probability weighting, and revenue forecasting that most CiviCRM installations approximate with Activity-based workarounds. Organizations that need structured deal tracking, pipeline visualization, and multi-stage revenue reporting move to Dynamics for the pipeline model that CiviCRM structurally cannot provide without significant custom development.
- CiviCRM free open-source download carries real hidden costs: server hosting ($50-500/month), PHP and MySQL maintenance, security patching, backup management, and periodic consultant time to handle upgrades and performance tuning. Microsoft Dynamics 365 Sales subscription at $50-$210/user/month includes the vendor-managed cloud, automatic updates, and Microsoft support, shifting operational cost from unpredictable infrastructure overhead to predictable per-seat licensing. Organizations report evaluating total cost of ownership across both models and choosing Dynamics for the operational predictability.
- Organizations already invested in Microsoft 365, Teams, SharePoint, and Outlook evaluate Microsoft Dynamics 365 Sales for native integration without third-party middleware. Dynamics enables Direct write-back to Outlook calendars, Teams meeting embedding, SharePoint document management from within records, and Power BI reporting with Dataverse as the data backbone. For organizations where the Microsoft ecosystem is the default environment, the integration depth justifies the platform investment over alternatives requiring separate connectors.
- CiviCRM requires dedicated PHP and MySQL expertise to configure effectively. Multiple G2 and Capterra reviewers describe needing a developer or consultant just to set up custom fields, configure CiviRules, manage extensions, and maintain performance. Microsoft Dynamics 365 Sales offers a configuration-first approach through the native UI with Power Apps for custom logic, reducing the developer dependency for standard operational CRM use cases. Organizations with limited technical staff move to reduce reliance on specialized CiviCRM consultants.
- Microsoft commits active development to Microsoft Dynamics 365 Sales with AI-powered insights, Copilot integration, continuous cloud updates, and a documented roadmap. CiviCRM depends on an open-source community maintaining a PHP/MySQL codebase, which means the pace of modernization, security patching, and new feature development is bounded by volunteer contributor availability. Organizations evaluating long-term platform investment view Microsoft's committed product roadmap as a more reliable foundation than a volunteer-maintained open-source project.

Questions, answered

## Civicrm to Dynamics 365 migration questions

How long does a CiviCRM to Microsoft Dynamics 365 Sales migration take?

Straightforward migrations with under 25,000 contacts, no ECK entities, and no large activity history complete in four to eight weeks. Complex migrations with ECK entity schemas, extensive relationship networks, large multi-record custom field sets, or heavy activity history extend to twelve to twenty weeks. The ECK schema design, relationship resolution, and multi-record custom field testing phases are the primary timeline drivers for complex cases.

Do CiviRules, scheduled jobs, and CiviCRM automations migrate to Dynamics?

No. CiviRules, CiviRules Email Schedule, CiviSche-dule, and custom PHP hooks do not migrate as code. Microsoft Dynamics 365 Sales does not have an equivalent to CiviRules, and Power Automate uses a different trigger, condition, and action model. We deliver a written inventory of every active CiviRule and scheduled job during migration with its trigger, conditions, and actions, plus a recommended Power Automate equivalent. The customer's Dynamics admin or a Microsoft partner rebuilds these post-migration. This rebuild work is outside the standard migration scope.

What happens to our Contributions, Memberships, and Grants after migration?

Contributions, Memberships, and Grants have no standard equivalent in Microsoft Dynamics 365 Sales because Dynamics is a commercial sales CRM, not a nonprofit CRM. We create custom objects contribution\_custom, membership\_custom, and grant\_custom with fields matching the relevant CiviCRM financial entity. If your organization also needs financial reporting, budget tracking, or grant management features, we recommend evaluating Microsoft Dynamics 365 Sales with a Service Cloud attachment or Dynamics 365 Business Central, which includes native financial management. Migrating to Sales Hub alone preserves the record data but does not replicate CiviCRM's financial reporting workflows.

How do we handle the API rate limit when migrating to Dynamics?

Microsoft Dynamics 365 Sales enforces approximately 6,000 requests per 300 seconds per user on the Dataverse Web API. CiviCRM on a self-hosted instance has no documented rate limit. We run a burst test against the destination during scoping to confirm the effective throttle ceiling, then pace our export workers to the observed safe rate using exponential backoff and Retry-After header reading. For large volume migrations, we use ExecuteMultipleRequest batch operations where supported, which counts as one request against the limit per batch rather than per record.

What scope of data does FlitStack AI migrate for CiviCRM?

We migrate Contacts (with subtypes), Activities, Custom Fields and multi-record CustomValue sets, Relationships, Groups, Cases (CiviCase), Contributions, Memberships, Events, Grants, Tags, Attachments, and ECK Entities. We do not migrate CiviMail mailing records because they are tightly coupled to the CiviCRM mailing infrastructure, SMTP configuration, and SPF/DKIM settings that do not transfer to Dynamics. We do not migrate Workflows, Sequences, Automations, Forms, Landing Pages, or Reports as code; we deliver a written inventory of these for the customer's admin to rebuild.

## Related migrations

[![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp) Migrate to **Dynamics 365** Every source we move into Dynamics 365, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/dynamics-365-sales)

### [Dynamics 365 implementation](https://flitstack.ai/services/dynamics-365-implementation)

[Set up Dynamics 365 and migrate into it as one engagement.](https://flitstack.ai/services/dynamics-365-implementation)

[See the service →](https://flitstack.ai/services/dynamics-365-implementation) [**Insightly CRM to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/insightly-crm/to/dynamics-365-sales) [**Yardi to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/yardi/to/dynamics-365-sales) [**Jobber to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/jobber/to/dynamics-365-sales) [**ActiveCampaign to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/activecampaign/to/dynamics-365-sales) [**Field Services Workflow and Logistics to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/field-services-workflow-and-logistics/to/dynamics-365-sales) [**Pipedrive to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/pipedrive/to/dynamics-365-sales) [**Civicrm to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/civicrm/to/salesforce-sales-cloud) [**Civicrm to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/civicrm/to/hubspot) [**Civicrm to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/civicrm/to/pipedrive)

## Sources: official documentation

1. [Dynamics 365 environment strategy — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/environment-strategy-guidance-product)
2. [Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)](https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/basics/import-accounts-leads-other-data?view=op-9-1)
3. [Import data (all record types) — Power Platform | Microsoft Learn](https://learn.microsoft.com/en-us/power-platform/admin/import-data-all-record-types)
4. [Execute Batch Operations on Dataverse — Microsoft Learn](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/execute-batch-operations-using-web-api)
5. [Service protection limits (Microsoft Dataverse)](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/api-limits)
6. [Entity relationship behavior — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/entity-relationship-behavior?view=op-9-1)

Get a quote

## Moving from Civicrm 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](https://flitstack.ai/contact)
