ActiveCampaign to Dynamics 365 migration
We migrate Contacts, Accounts, Deals, and Engagement history from ActiveCampaign into Microsoft Microsoft Dynamics 365 Sales with Accounts created before Contact imports, Deals mapped to Opportunities with pipeline and stage probability preserved, and every ActiveCampaign custom field mapped to a typed Dynamics 365 field before cutover.
FlitStack AI migrates lead or contacts, accounts, opportunities, record type + sales process and multi-select picklist or topics from ActiveCampaign 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 ActiveCampaign to Dynamics 365?
Moving from ActiveCampaign to Microsoft Microsoft Dynamics 365 Sales is a migration from a marketing-automation-first platform into a dedicated sales CRM with deep Microsoft 365 integration.
Read the full summary
ActiveCampaign uses a flat contact-based data model with Deals attached via a Pipeline; Microsoft Dynamics 365 Sales separates Leads from Contacts, uses Accounts as the parent business entity, and attaches Opportunities as the deal record. We resolve the Contact-to-Lead-or-Contact routing during scoping, pre-create the Dynamics 365 schema (custom fields, Opportunity pipelines, sales processes) before any data moves, and load records in dependency order: Accounts first, then Contacts with AccountId resolved, then Opportunities with AccountId, OwnerId, and the appropriate RecordTypeId. Engagement history (email, calls, meetings, tasks) migrates to Dynamics 365 activity entities via the Dataverse API. Automations, Email Templates, Forms, and Landing Pages do not migrate; we deliver a written inventory of every automation requiring rebuild in Microsoft Dynamics 365 Sales or Power Automate.
Contact → Lead or Contact (split required)
ActiveCampaign Contacts with no associated Deal and Lifecycle Stage of subscriber or lead map to Salesforce Lead.
How it maps
ActiveCampaign Contacts attached to Deals or with Lifecycle Stage of customer map to Dynamics 365 Contact tied to an Account. We compute the split using the ActiveCampaign lifecyclestage property and contact_type during migration scoping, preserving the original stage in a custom field hs_original_lifecycle__c for audit.
Account → Account
ActiveCampaign Accounts map directly to Dynamics 365 Account.
How it maps
The Account name and domain become the Account Website and primary dedupe key. We load Accounts before Contacts so AccountId is available at Contact insert time to satisfy the parent lookup.
Deal → Opportunity
ActiveCampaign Deals map to Dynamics 365 Opportunity.
How it maps
The pipeline assignment maps to a Record Type and Sales Process we configure in the destination before migration. Deal stage probability percentages migrate to Opportunity StageProbability, overriding the Dynamics 365 default so historical deals retain their forecast value.
Pipeline → Record Type + Sales Process
Each ActiveCampaign pipeline becomes a Dynamics 365 Opportunity Record Type with a corresponding Sales Process that whitelists the relevant stage values.
How it maps
Stage names, order, and probability percentages transfer from ActiveCampaign pipeline definitions to the Dynamics 365 stage configuration.
Tag → Multi-Select Picklist or Topic
ActiveCampaign tags migrate to Dynamics 365 as multi-select picklist values on Contact and Lead.
How it maps
The customer chooses during scoping whether to consolidate high-volume tags into a single custom field or distribute them across topic-based categorization aligned with the new Microsoft Dynamics 365 Sales workflow.
Custom Field (Contact) → Custom Field (Contact/Lead)
ActiveCampaign custom contact fields map to Dynamics 365 custom fields on Contact or Lead.
How it maps
We pre-create the destination schema in the Dataverse environment before migration, matching ActiveCampaign field types to appropriate Dynamics 365 field types (text, number, date, picklist).
- ContactLead or Contactsplit
- AccountAccount1:1
- DealOpportunity1:1
- PipelineRecord Typetransformed
- TagMulti-Select Picklist or Topictransformed
- Custom FieldCustom Field1:1
+ 4 more in the mapping below
How ActiveCampaign 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 | ActiveCampaign | Dynamics 365 |
|---|---|---|
| Lead vs Contact model | Single Contact object with Lifecycle Stage property; no separate Lead object | Separate Lead and Contact objects; unqualified prospects as Lead, qualified buyers as Contact attached to Account |
| CRM depth | Marketing automation platform with secondary CRM; deal and pipeline features less mature than dedicated CRMs | Sales-focused CRM with enterprise pipeline management, forecasting, Copilot AI, and conversation intelligence built in |
| Pipeline structure | Multiple pipelines with custom stages and probabilities | Record Types and Sales Processes control stage values; unlimited record types at all paid tiers |
| Custom objects | Custom Objects available only on Enterprise or Pipelines/Sales Engagement add-on | Custom entities available via Dataverse schema from Essentials tier onward |
| Pricing model | Per-contact billing including unsubscribes and bounces; escalates steeply past 1,000 contacts | Per-user named licensing; predictable cost scaling tied to seat count not contact volume |
| Microsoft 365 integration | 900+ third-party integrations via API; no native Microsoft stack connection | Native integration with Outlook, Teams, SharePoint, and Copilot for Sales inside Outlook |
| Automation model | Visual automation builder with triggers, conditions, and CRM actions; not exportable | Power Automate for workflow automation; Sales Cadences for sales engagement sequences |
ActiveCampaign to Dynamics 365 field mapping
The 29 most-used fields of 29 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
emailContactEmailAddressLead/Contact -
firstNameContactFirstNameLead/Contact -
lastNameContactLastNameLead/Contact -
phoneContactTelephone1Lead/Contact -
orgidContactAccountIdAccount
| ActiveCampaign field | Dynamics 365 field | Mapping | Note |
|---|---|---|---|
Contact.email | Lead/Contact.EmailAddress | direct | Lowercase and trim; used as dedupe key. |
Contact.firstName | Lead/Contact.FirstName | direct | Trim whitespace; Dynamics 365 enforces 50 character limit. |
Contact.lastName | Lead/Contact.LastName | direct | Trim whitespace; required field on both Lead and Contact. |
Contact.phone | Lead/Contact.Telephone1 | direct | Phone format pass-through; strip non-numeric characters if Dynamics format validation is enabled. |
Contact.orgid | Account.AccountId | lookup | Resolved via Account mapping table by Account name match. Unresolved accounts go to a reconciliation queue for admin provisioning. |
Contact.bouncerScore | Contact.msdyncrm_bounce_score__c | direct | ActiveCampaign bounce score migrates to a custom decimal field since Dynamics 365 does not have a native bounce scoring equivalent. |
Contact.crmaccnt_cdeal_id | Contact.ParentRecordId | lookup | Links Contact to the primary associated Account record in Dynamics 365 via the native account relationship. |
Account.name | Account.Name | direct | Dynamics 365 limit 250 characters. |
Account.phone | Account.Telephone1 | direct | Pass-through; strip formatting if validation is enabled. |
Account.city | Account.Address1_City | direct | ActiveCampaign's single address field maps to the Dynamics 365 Address1 composite. |
Account.state | Account.Address1_StateOrProvince | direct | Validate against Dynamics 365 State and Country picklists if enabled in the destination. |
Account.country | Account.Address1_Country | direct | Country picklist validation applies if State and Country picklists are enabled. |
Account.website | Account.WebSiteURL | direct | Prefix with https:// if the ActiveCampaign value lacks a scheme. |
Account.numberofemployees | Account.NumberOfEmployees | direct | Integer field; pass through. |
Deal.title | Opportunity.Name | direct | Dynamics 365 Opportunity name limit 200 characters. |
Deal.value | Opportunity.EstimatedValue | direct | Currency field; confirm currency alignment between ActiveCampaign and Dynamics 365 org before migration. |
Deal.stage | Opportunity.StageId | lookup | ActiveCampaign deal stage IDs resolve to Microsoft Dynamics 365 Sales Process stage IDs configured per the customer's pipeline structure during scoping. |
Deal.pipeline | Opportunity.RecordTypeId | lookup | Each ActiveCampaign pipeline maps to a Dynamics 365 Opportunity Record Type pre-configured before migration. |
Deal.closedate | Opportunity.EstimatedCloseDate | direct | Date field; ISO format in both systems. |
Deal.probability | Opportunity.StepId | direct | ActiveCampaign stage probability percent maps to the probability field on the Microsoft Dynamics 365 Sales Process stage. |
Deal.crmaccnt_contact_id | Opportunity.ParentContactId | lookup | Resolved via Contact mapping table by email match. |
Engagement (Email).subject | EmailMessage.Subject | direct | Dynamics 365 limit 1,000 characters. |
Engagement (Email).body | EmailMessage.Description | direct | Plain text body migrates verbatim; HTML body migrates to the HTML body field if present. |
Engagement (Call).duration | Task.ActualDurationMinutes | direct | ActiveCampaign call duration in seconds converts to minutes for the Dynamics 365 duration field. |
Engagement (Meeting).title | Appointment.Subject | direct | Dynamics 365 limit 200 characters. |
Engagement (Meeting).starttime | Appointment.ScheduledStart | direct | ISO 8601 datetime; timezone preserved. |
Engagement (Meeting).endtime | Appointment.ScheduledEnd | direct | ISO 8601 datetime. |
Engagement (Task).title | Task.Subject | direct | Dynamics 365 limit 200 characters. |
Engagement (Task).status | Task.StateCode | transform | ActiveCampaign task statuses (not completed, completed) map to Dynamics 365 Task StateCode and StatusCode values configured during scoping. |
What to watch for in a ActiveCampaign 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.
ActiveCampaign automations do not migrate to Power Automate
ActiveCampaign does not expose automation workflow definitions via its public API for export.
How we handle it
The only path for automations is manual rebuild. We do not attempt to import automation JSON as it is not accessible through the API. During scoping, we inventory every ActiveCampaign automation with its trigger, conditions, and actions and deliver a written handoff document mapping each to a Power Automate flow recommendation. The customer's admin rebuilds these in Power Automate post-migration.
Deal notes are not exportable via ActiveCampaign API
The ActiveCampaign deal export endpoint and standard API do not include deal notes.
How we handle it
When migrating Deals to Dynamics 365 Opportunities, we flag this gap during scoping and alert the customer that deal notes will not transfer unless a separate manual extraction workaround is performed before migration. Notes cannot be recovered post-migration.
Contact billing counts all statuses including suppressed records
As of November 2025, ActiveCampaign counts the total number of contacts including unsubscribes, bounces, and unconfirmed contacts toward the contact limit.
How we handle it
This affects scoping: the customer's actual billable contact count may be significantly higher than the active emailable count. We include suppressed-record cleanup recommendations in the migration scope so the Dynamics 365 import starts from a clean contact list and the customer understands the billable footprint.
Dynamics 365 schema must be designed before data migration begins
Microsoft Dynamics 365 Sales requires custom fields, entities, and sales processes to be created in the Dataverse environment before any data is loaded.
How we handle it
Unlike some CRM migrations where fields can be added mid-migration, Dynamics 365 enforces a pre-configuration step. We create the full destination schema including all custom Opportunity fields, Record Types, and Sales Processes in a Sandbox first, validate with the customer, and only then proceed to production data migration.
Lead versus Contact routing requires scoping decision
Microsoft Dynamics 365 Sales distinguishes between Leads (unqualified prospects) and Contacts (qualified individuals attached to Accounts).
How we handle it
ActiveCampaign has one Contact object with a Lifecycle Stage property. We define the routing rule during scoping based on the customer's lifecycle stage matrix and apply it as the first transform during migration. Records routed to Lead are created with the Account name in the Lead Company field; records routed to Contact are created with an AccountId lookup satisfied by the Account load phase.
How the migration runs
Discovery and migration scope
We audit the source ActiveCampaign environment across tier (Starter, Plus, Pro, Enterprise), contact volume (including suppressed record counts post-November 2025 billing change), custom contact fields, custom deal fields, pipeline count and stage definitions, deal notes volume, and engagement history volume.
What this step covers
We pair this with a Dynamics 365 edition decision: Essentials ($70/user) covers basic CRM with Leads and Contacts; Sales Premium ($150/user) is required for Copilot AI, predictive scoring, and conversation intelligence. The discovery output is a written migration scope with record-count estimates and a Dynamics 365 edition recommendation.
Schema design and Dataverse pre-configuration
We design the destination schema in Dynamics 365 Dataverse.
What this step covers
This includes creating all custom fields on Contact, Lead, Account, and Opportunity to match the ActiveCampaign field inventory; configuring Record Types and Sales Processes per ActiveCampaign pipeline; setting stage probability values; and defining the Lead-Contact routing rule based on the customer's lifecycle stage matrix. Schema is deployed into a Sandbox org first for validation by the customer's Dynamics 365 admin.
Sandbox migration and reconciliation
We run a full migration into the Dynamics 365 Sandbox using production-equivalent data volume.
What this step covers
The customer's admin reconciles record counts (Accounts in, Contacts in, Opportunities in, Activities in), spot-checks 25-50 records against the ActiveCampaign source, and approves the schema and mapping before production migration begins. Mapping corrections happen in Sandbox, not in production.
Owner reconciliation and User provisioning
We extract every distinct ActiveCampaign owner referenced on Contact, Account, and Deal records and match by email against the Dynamics 365 destination org's User table.
What this step covers
Owners without a matching User go to a reconciliation queue. The customer's admin provisions any missing Users. OwnerId references must be resolved before Opportunity imports proceed because the Owner field is required on the Opportunity record.
Production migration in dependency order
We run production migration in record-dependency order: Accounts first (from ActiveCampaign Organizations), Contacts second with AccountId resolved from the Account load phase and Lead-Contact split applied, Opportunities third with AccountId, OwnerId, and RecordTypeId resolved, Activity history (email, calls, meetings, tasks) via Dataverse API.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Deal notes are flagged as a gap if not manually extracted before the migration window.
Cutover, validation, and automation handoff
We freeze ActiveCampaign writes during cutover, run a final delta migration of any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record.
What this step covers
We deliver the Automation and Workflow inventory document to the customer's admin team with Power Automate rebuild recommendations. We support a one-week hypercare window for reconciliation issues. We do not rebuild ActiveCampaign automations as Power Automate flows inside the migration scope; that 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 record volume, custom field count, and the scope of engagement history migration. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for ActiveCampaign to Dynamics 365 →Why teams move from ActiveCampaign to Dynamics 365
- ActiveCampaign's per-contact billing counts unsubscribes, bounces, and unconfirmed records toward the limit as of November 2025, making it expensive for lists above 1,000 contacts. Microsoft Dynamics 365 Sales uses per-user named licensing that scales predictably with headcount rather than contact volume, removing the billing surprise that drives mid-market teams to migrate away from ActiveCampaign.
- Microsoft Dynamics 365 Sales Premium at $150/user/month includes Copilot AI across all surfaces, predictive lead and opportunity scoring, conversation intelligence through Teams, and relationship analytics. ActiveCampaign gates AI-powered features behind Enterprise tier and charges additional per-feature fees, making the AI value proposition less transparent at lower tiers.
- For organizations already running Microsoft 365, Microsoft Dynamics 365 Sales is the only CRM with native Outlook email tracking, Teams meeting embedding, and SharePoint file attachment inside the opportunity record without middleware connectors. ActiveCampaign requires API integrations to connect with Microsoft tools, and those integrations need ongoing maintenance.
- ActiveCampaign's CRM features feel secondary to its marketing automation core; reviewers on G2 and Capterra consistently cite limited pipeline customization, weak reporting, and insufficient deal-tracking depth compared to dedicated sales CRMs. Microsoft Dynamics 365 Sales was built as a sales platform from the ground up, with enterprise pipeline management, territory forecasting, and multi-currency support available from Essentials tier.
- As teams scale from SMB to mid-market, ActiveCampaign's contact-based pricing combined with per-seat user costs creates compounding expense. Microsoft Dynamics 365 Sales per-user pricing is more predictable and includes Dataverse storage, standard reports, and the full Sales app at all tiers rather than gating features behind add-on fees.
Questions, answered
ActiveCampaign to Dynamics 365 migration questions
How long does an ActiveCampaign to Microsoft Microsoft Dynamics 365 Sales migration take?
Most migrations land between four and eight weeks for accounts under 15,000 Contacts, 3,000 Deals, and no custom objects. Migrations with custom fields across multiple objects, multiple ActiveCampaign pipelines, large engagement histories (over 200,000 activity records), or Accounts that need to be reconciled against a pre-existing Dynamics 365 environment move to ten to sixteen weeks because of Dataverse schema pre-configuration, Owner-to-User reconciliation, and pipeline stage mapping work.
Do ActiveCampaign automations, email templates, and forms migrate to Dynamics 365?
No. ActiveCampaign automations are JSON-based workflow definitions that are not accessible via the public API for export. Email templates, forms, and landing pages similarly cannot be exported as transferable code. We deliver a written inventory of every active ActiveCampaign automation with its trigger, conditions, and actions, plus a recommendation for each to be rebuilt as a Power Automate flow or Microsoft Dynamics 365 Sales Cadence. The customer's admin or a Microsoft partner handles the rebuild post-migration.
Do we lose historical engagement data (calls, emails, meetings, tasks) when migrating from ActiveCampaign?
No. We migrate the full engagement history via the Dynamics 365 Dataverse API. Emails land as EmailMessage records linked to Tasks; calls land as Task records with the Call subtype and duration preserved; meetings land as Appointment records; tasks land as Task records. Activity timestamp ordering is preserved by setting the original engagement date. Note: ActiveCampaign deal notes cannot be exported via API and will not transfer unless manually extracted before the migration window.
How does the Contact-to-Lead-or-Contact routing work?
ActiveCampaign has one Contact object; Dynamics 365 separates Leads (unqualified prospects) from Contacts (qualified individuals attached to Accounts). We define the routing rule during scoping based on the customer's ActiveCampaign lifecycle stage matrix and any deal association. Contacts that are Leads in ActiveCampaign route to the Dynamics 365 Lead entity with the original lifecycle stage preserved in a custom field. Contacts attached to Deals route to the Dynamics 365 Contact entity with AccountId resolved from the Account load phase. The customer approves the routing rule before migration begins.
Can we keep ActiveCampaign for marketing automation while moving sales to Dynamics 365?
Yes. A hybrid stack is a common pattern for this migration. ActiveCampaign continues to handle email marketing, SMS, and automation workflows; Microsoft Dynamics 365 Sales handles the sales process from Lead through Opportunity. We recommend the native ActiveCampaign-to-Dynamics 365 sync (available via the ActiveCampaign integration in Microsoft AppSource) to keep new Leads flowing from ActiveCampaign into Dynamics 365. The customer maintains both subscriptions during the transition period.
What happens to our ActiveCampaign tags during migration?
Tags are a flat label system in ActiveCampaign. We export the full tag taxonomy and reassign tags during import as multi-select picklist values on the Contact or Lead record in Dynamics 365. Tags migrate 1:1 with no value transformation required. During scoping, the customer decides whether to keep all tags, consolidate high-volume tags into a smaller set, or adopt a topic-based taxonomy aligned with the new Dynamics 365 workflow.
Why does Dynamics 365 require schema pre-configuration before migration?
Unlike some CRM platforms where custom fields can be added during import, Microsoft Dynamics 365 Sales enforces a pre-configuration step through the Dataverse schema. Custom fields, Record Types, Sales Processes, and relationship definitions must exist in the environment before data is loaded. We handle this in a Sandbox first, validate the schema with the customer, deploy to production, and only then begin data migration. This adds a planning step but prevents field-missing errors during the production load.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Civicrm to Dynamics 365Mapping · history · rollbackInsightly CRM to Dynamics 365Mapping · history · rollbackYardi to Dynamics 365Mapping · history · rollbackField Services Workflow and Logistics to Dynamics 365Mapping · history · rollbackPipedrive to Dynamics 365Mapping · history · rollbackZendesk Sell to Dynamics 365Mapping · history · rollback ActiveCampaign to Zoho CRMMapping · history · rollbackActiveCampaign to HighLevelMapping · history · rollbackActiveCampaign to HubSpotMapping · 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 ActiveCampaign 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