Skip to content
Get a quote

Customer.io to Dynamics 365 migration

We migrate People, Events, and Custom Objects from Customer.io into Microsoft Microsoft Dynamics 365 Sales by resolving the anonymous-profile-to-Lead split up front, preserving event history in Dataverse custom entities, and mapping every Customer.io trait to a typed Dynamics 365 field before cutover.

Short answer

FlitStack AI migrates contact or leads, accounts, custom event entities, contact field or custom fields and static view or dynamic lists from Customer.io 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: 3-5 weeks.

By

Source Customer.io
DestinationDynamics 365
Contact or LeadAccountCustom Event EntityContact Field or Custom FieldStatic View or Dynamic List
Mapped field by field · sample run · one-click rollback

What moves from Customer.io to Dynamics 365?

Moving from Customer.io to Microsoft Microsoft Dynamics 365 Sales is a platform-type migration: Customer.io is an event-driven behavioral messaging platform, while Microsoft Dynamics 365 Sales is a relational CRM.

Read the full summary

The two systems use fundamentally different data models — Customer.io stores identity-first Profiles with a full event timeline and nested traits; Dynamics 365 separates Leads, Contacts, and Accounts into a normalized relational schema. We resolve this structural gap during scoping by designing the Lead-versus-Contact split rule, pre-creating Dataverse custom entities for event history and behavioral traits, and mapping the Customer.io userId to the appropriate Dynamics 365 primary key. We migrate active People records as Contacts or Leads, Customer.io Companies as Accounts, Custom Objects as Dataverse custom entities, and the full event timeline as a custom event entity linked to the Contact. We do not migrate Campaigns, Journeys, Workflows, Segments, or Broadcasts as code; we deliver a written inventory of every active workflow and segment for the customer to rebuild in Microsoft Dynamics 365 Sales or Power Automate. Push notification migration is not applicable to this destination pair because Microsoft Dynamics 365 Sales has no native push channel and device tokens cannot be imported from Customer.io.

1:N split

Person (Profile) → Contact or Lead (split required)

Customer.io Profiles with a clear email address and business identity map to Dynamics 365 Contact.

How it maps

Anonymous Profiles (identified by anonymousId only with no email) map to Dynamics 365 Lead or are flagged for manual review. We compute the split using the presence of a valid email property in the Customer.io identify() payload and apply a minimum trait count threshold (e.g., more than two traits) as a secondary qualification signal. The original Customer.io userId is stored in a custom field cio_user_id__c on both Lead and Contact for cross-system reconciliation.

1:1

Company (Custom Object) → Account

Customer.io Companies stored as object_type_id namespaces map to Dynamics 365 Account.

How it maps

The company name maps to Account Name; domain maps to Website; city and country map to Address fields. If the Customer.io Company has a relationship to a Person via the group() call, we create the Account first, then resolve the AccountId lookup when importing the Contact. If multiple Customer.io Persons reference the same Company object, we deduplicate on Company ID to create one Account.

1:1

Custom Event → Custom Event Entity (Dataverse)

Customer.io events created via track() have no direct Dynamics 365 equivalent because Sales does not have a native event store.

How it maps

We pre-create a Dataverse custom entity (e.g., cio_event) with fields for event_name, event_timestamp, user_id (lookup to Contact), and a properties JSON column or individual attribute fields for the most common event property keys. We export the full event schema during scoping, map property keys that appear in more than 10 percent of events to named columns, and store the remainder in a JSON properties field. Events are the highest-volume object in a Customer.io migration and are batched in chunks of 5,000 records during import.

1:1

Trait (attribute) → Contact Field or Custom Field

Customer.io traits set via identify() migrate to typed Dynamics 365 Contact fields.

How it maps

String traits map to Single Line of Text, boolean traits to Two Options, date traits to Date and Time, numeric traits to Decimal or Whole Number, and array traits to Multiple Lines of Text (JSON serialized) or a custom multi-select field depending on the customer's preference. Traits with more than 10 unique values across the dataset map to Option Set fields. We flag any trait with a null rate above 80 percent so the customer can decide whether the field is worth migrating.

configuration

Segment → Static View or Dynamic List

Customer.io Segments are dynamic audience definitions with rule-based inclusion criteria (trait conditions, event conditions, membership time).

How it maps

We export the full segment rule set as a structured JSON document and translate it into a Dynamics 365 Advanced Find fetchXML query or a Power Automate flow that rebuilds the segment membership on a schedule. Segments do not migrate as active audience data; they migrate as rule documentation for the customer's admin to implement in Dynamics 365.

configuration

Campaign / Journey → Campaign (documentation only)

Customer.io Journeys and Campaigns contain entry triggers, branching conditions, wait steps, and multi-channel message actions that have no direct Microsoft Dynamics 365 Sales equivalent.

How it maps

Sales Cloud has a Campaign object for tracking marketing campaign membership but no native Journey builder. We export the Journey structure as a written document including trigger type, step sequence, channel per step, and condition branches. The customer's admin rebuilds the campaign logic in Dynamics 365 Customer Insights - Journeys, Power Automate, or a third-party marketing tool.

What moves10 objects
Customer.ioDynamics 365
  • PersonContact or Leadsplit
  • CompanyAccount1:1
  • Custom EventCustom Event Entity1:1
  • TraitContact Field or Custom Field1:1
  • SegmentStatic View or Dynamic Listtransformed
  • CampaignCampaigntransformed

+ 4 more in the mapping below

How Customer.io 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.

DimensionCustomer.ioDynamics 365
Record modelIdentity-first Profiles with userId, anonymousId, and event timeline unified in one objectNormalized Lead and Contact objects with explicit conversion step, linked to Account and Opportunity
Behavioral dataNative Events (track()) with properties and timestamps stored per ProfileNo native event store; behavioral data requires custom entity on Dataverse
Audience logicDynamic Segments built from trait conditions and event conditionsStatic Views and Dynamic Lists filtered via fetchXML; no native segment equivalent
Campaign modelVisual Journey builder with entry triggers, branching, and multi-channel actionsNo native campaign builder; marketing automation lives in separate Customer Insights - Journeys SKU
Pricing modelPer stored profile regardless of engagement; inactive and deleted-within-cycle profiles still billedPer-user named license; storage is org-wide not per-contact
Push notificationsFull native support with SDK-based device token registrationNo native push channel in Microsoft Dynamics 365 Sales ; requires separate mobile app SDK integration
Microsoft ecosystemAPI-first with Segment and Mixpanel integrations but no native Microsoft 365 tie-inNative Outlook email tracking, Teams collaboration, SharePoint document management, and Dataverse integration across all Microsoft 365 apps

What to watch for in a Customer.io 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

Microsoft Dynamics 365 Sales has no native push notification channel

Customer.io supports push notifications via its mobile SDK, but Microsoft Microsoft Dynamics 365 Sales does not include a push notification channel.

How we handle it

Device tokens registered in Customer.io cannot be imported into Dynamics 365 and will not route push messages. If your Customer.io implementation includes push messaging, the channel must be rebuilt using a separate push provider (Firebase Cloud Messaging, Apple Push Notification Service) integrated via Power Apps or a custom Azure Function. We flag all device token data during scoping and exclude it from the migration scope as it cannot be used in Microsoft Dynamics 365 Sales .

high

Anonymous profiles and event-only records have no clean Lead equivalent

Customer.io stores anonymous users identified by anonymousId with no email address and a full event history (page views, app opens, etc.).

How we handle it

Dynamics 365 Lead requires at minimum a name or email to create a valid record. We establish a split rule during scoping: Profiles with a valid email address become Contacts (or Leads for unqualified prospects); anonymous-only Profiles with event history only are stored in a dedicated Dataverse custom entity (cio_anonymous_event) linked to a placeholder Account so that behavioral data is not lost. This is a design decision that requires customer sign-off before migration begins.

medium

Customer.io Workflows and Journeys do not migrate to Dynamics 365

Customer.io Journeys and Workflows are event-triggered, visual automation sequences with branching logic, delay steps, and multi-channel message actions.

How we handle it

Microsoft Dynamics 365 Sales has no native equivalent Journey builder; marketing automation lives in the separate Customer Insights - Journeys SKU or Power Automate. We do not migrate Workflows or Journeys as code. We deliver a written inventory of every active Journey including trigger conditions, step sequence, channel assignments, and branch logic. The customer's admin or a Dynamics partner rebuilds them in Customer Insights - Journeys or Power Automate post-migration. Broadcasts and Segments similarly require rebuild and are delivered as documentation.

medium

Event history volume can exceed standard Dynamics 365 data import tooling capacity

Customer.io event data (track() calls) can represent millions of records for active products.

How we handle it

Microsoft Dynamics 365 Sales data import via the UI and the standard Data Management Framework has per-job size limits. We use Dataverse bulk import with batched entity creation requests, exponential backoff on throttling responses, and parent-record lookup resolution to ensure events attach to the correct Contact or Account. Events are imported after Contacts and Accounts so that the lookup resolution is satisfied at import time. We scope event history retention with the customer (e.g., last 12 months) to keep the import within manageable time and cost bounds.

low

Customer.io profile pricing model has no direct Dynamics 365 analog

Customer.io pricing is based on total stored Profiles including inactive and recently deleted records.

How we handle it

Microsoft Dynamics 365 Sales pricing is per-user named license. When migrating from Customer.io to Dynamics 365, the customer may be moving from a per-contact pricing model to a per-user model. We flag the active-to-inactive ratio during scoping so the customer understands whether their Dynamics 365 per-user cost will be higher or lower than their Customer.io profile billing. This analysis is part of the pre-migration business case, not a migration configuration decision.

How the migration runs

  1. Discovery and source audit

    We audit the Customer.io workspace across object types (People, Companies, Custom Objects), event schemas (all track() call names and top property keys), active Journeys and Workflows, Broadcast history, and delivery log scope.

    What this step covers

    We pair this with a Dynamics 365 environment audit: existing entities, custom fields, security roles, and whether Customer Insights - Journeys is licensed. The discovery output is a written migration scope covering record counts per object, event history volume, a preliminary object mapping, and a Lead-Contact split rule proposal based on the customer's email capture rate.

  2. Schema design and custom entity provisioning

    We design the destination Dynamics 365 schema on Dataverse.

    What this step covers

    This includes pre-creating custom entities for Customer.io event history (cio_event), anonymous event records (cio_anonymous_event), and any Custom Object namespaces that have no standard Dynamics 365 equivalent. We define custom fields on Contact and Account to carry Customer.io identifiers (cio_user_id__c, cio_company_id__c) and to preserve original Lifecycle Stage values. Schema is deployed into a Dynamics 365 Sandbox environment first for validation before any data moves.

  3. Sandbox migration and reconciliation

    We run a full migration into the Dynamics 365 Sandbox using representative data volume.

    What this step covers

    The customer's RevOps or IT lead reconciles record counts (Contacts in, Leads in, Accounts in, event records in), spot-checks 25-50 records against the Customer.io source, and reviews the anonymous-profile handling decision. Schema corrections, field type adjustments, and split rule refinements happen here. No production data moves until the sandbox sign-off is received from the customer's project owner.

  4. Event schema profiling and audience mapping

    We analyze the full Customer.io event schema to identify the most common property keys across all track() events.

    What this step covers

    Properties appearing in more than 10 percent of events are mapped to named columns on the custom event entity; less common properties are serialized into a JSON properties column. We also export segment rule sets as structured JSON documents for the customer's admin to implement as Power Automate flows or Advanced Find views post-migration.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Customer.io Companies), Contacts and Leads (with the anonymous split applied and AccountId resolved), custom entities (event history, Custom Objects), then message delivery history as Campaign Member records.

    What this step covers

    Each phase emits a row-count reconciliation report. We use Dataverse bulk import with batch chunking and exponential backoff on throttling responses. During cutover we freeze Customer.io writes, run a final delta migration of any records modified during the migration window, then hand off Dynamics 365 as the system of record.

  6. Cutover, validation, and rebuild handoff

    We freeze the Customer.io integration during cutover, validate record counts in Dynamics 365 against the source, and confirm the anonymous-profile handling matches the signed-off split rule.

    What this step covers

    We deliver the Journey and Workflow inventory document, the segment rule documentation, and the transactional template content export. We support a one-week hypercare window for reconciliation issues raised by the customer's team. We do not rebuild Customer.io Workflows or Journeys as Power Automate flows inside the migration scope; that work is documented and handed off as a separate rebuild task.

Customer.io Dynamics 365
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Dynamics 365Rollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
8-12 weeksLarge or heavily customised accounts

A quote scales with record volume, event history preservation scope, and custom entity complexity. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Customer.io to Dynamics 365 →

Why teams move from Customer.io to Dynamics 365

  • Customer.io bills by total stored Profiles — inactive records and those deleted within the billing cycle still count against the monthly total. Teams with large early-growth user tables pay for hundreds of thousands of profiles that never receive campaigns. Microsoft Dynamics 365 Sales per-user licensing is more predictable for sales-focused teams because inactive users can be assigned Team Member read-only licenses at $8 per seat or deactivated entirely without inflating the bill. Reviewers on G2 and Capterra consistently cite the profile-count billing surprise as the reason they evaluate alternatives.
  • Customer.io has no native CRM functionality — teams must run a separate CRM and sync it via integration, creating duplicate record management, sync lag, and two billing lines for what could be one platform. Microsoft Dynamics 365 Sales brings Leads, Contacts, Accounts, Opportunities, and Activity tracking into a single product with native Outlook and Teams integration, eliminating the overhead of maintaining a parallel CRM alongside the messaging platform.
  • Organizations already invested in Microsoft 365 (Azure AD, Teams, SharePoint, Power Platform) move customer engagement data into Dynamics 365 to unify customer records across sales, service, and marketing without maintaining a separate data silo. Reddit discussions on Dynamics 365 migration highlight tighter Outlook email tracking, Teams meeting capture, and SharePoint document management as key integration advantages over Customer.io's API-first but Microsoft-disconnected model.
  • Customer.io's visual Journey builder, event-triggered workflows, and segment-based audience logic require developer involvement to configure and maintain at scale, creating a ceiling for non-technical marketers. Microsoft Dynamics 365 Sales with Power Automate provides workflow capabilities at a lower technical门槛 for day-to-day sales process automation, and the low-code Power Apps layer extends the CRM without deep development resources for common business use cases.
  • As companies scale, they consolidate vendor relationships to reduce procurement overhead, vendor management time, and per-platform administrative costs. Moving from Customer.io plus a separate CRM to a single Microsoft Dynamics 365 Sales instance with Customer Insights - Journeys (or a third-party marketing tool of choice) reduces the number of customer data platforms from two to one, simplifying audit, compliance, and vendor risk review cycles.

Questions, answered

Customer.io to Dynamics 365 migration questions

How long does a Customer.io to Microsoft Microsoft Dynamics 365 Sales migration take?

Migrations under 10,000 active Profiles with no event history preservation land between three and five weeks and complete in the sandbox-validate-then-migrate pattern. Migrations with full event timeline preservation (over 100,000 event records), multiple Custom Object types, large Company objects, or a complex anonymous-profile split decision move to eight to twelve weeks because of Dataverse custom entity setup, event schema profiling, and bulk import batching with parent-record lookup resolution.

Do Customer.io Journeys, Workflows, Segments, and Broadcasts migrate to Dynamics 365?

No. Customer.io Journeys and Workflows are event-triggered visual automation sequences with branching conditions and multi-channel message actions that have no direct Microsoft Dynamics 365 Sales equivalent. Segments are dynamic rule-based audiences that require rebuild in Dynamics 365 Advanced Find, Power Automate, or Customer Insights - Journeys. Broadcasts and transactional message templates do not migrate as reusable templates. We deliver a written inventory of every active Journey, Workflow, Segment, and Broadcast with its trigger, conditions, actions, and channel assignments so the customer's admin or a Dynamics partner can rebuild them post-migration.

What happens to my Customer.io event history during migration?

Customer.io event history (track() calls with properties and timestamps) migrates into a Dataverse custom entity that we pre-create during schema design. Events are linked to the corresponding Contact or Lead via a lookup field populated at migration time. Event schema profiling happens during scoping: property keys appearing in more than 10 percent of events are mapped to named columns; the remainder is stored as a JSON properties field. We scope event history retention with the customer (e.g., last 12 or 24 months) to manage import volume and cost. Microsoft Dynamics 365 Sales does not have a native event store, so event history requires this custom-entity approach.

Can we keep Customer.io for push and in-app messaging while moving CRM data to Dynamics 365?

Yes. A hybrid stack is a common pattern: Customer.io continues to handle push and in-app messaging while Dynamics 365 becomes the system of record for Leads, Contacts, Accounts, and Opportunities. We configure the Customer.io-to-Dynamics 365 integration during migration so that new Customer.io audience members with valid email addresses flow into Dynamics 365 as Contacts or Leads on a scheduled sync. The customer continues paying for Customer.io at the messaging layer while moving sales seat licensing to Dynamics 365. Push device tokens continue to live in Customer.io and are excluded from the Dynamics migration scope.

How are anonymous Customer.io profiles handled in Dynamics 365?

Customer.io stores anonymous users with an anonymousId and no email address who have behavioral data (page views, app events) but no identity. Dynamics 365 Lead requires at minimum a name or email to create a valid record. We establish a split rule during scoping: Profiles with a valid email address become Contacts (qualified) or Leads (unqualified); anonymous-only Profiles with event history are stored in a dedicated Dataverse custom entity (cio_anonymous_event) linked to a placeholder Account. This approach preserves behavioral data without creating invalid Dynamics 365 records. The customer's admin reviews and approves the split rule before production migration begins.

Does Dynamics 365 have a built-in marketing automation equivalent to Customer.io Journeys?

Microsoft Dynamics 365 Sales alone does not have a native Journey builder. Microsoft markets marketing automation as a separate SKU called Customer Insights - Journeys (formerly Dynamics 365 Marketing), which includes email marketing, lead scoring, event management, and a Journey canvas. If the customer licenses Customer Insights - Journeys, the Journey rebuild uses that product. If not, the Journey rebuild uses Power Automate for simpler workflows or a third-party marketing tool. We document every Customer.io Journey in detail so the customer's admin has a complete specification regardless of which rebuild path they choose.

What data cannot be migrated from Customer.io to Microsoft Dynamics 365 Sales ?

Five categories of data do not migrate: Push notification device tokens (Microsoft Dynamics 365 Sales has no native push channel and tokens cannot be reused); Workflow and Journey automation as executable code (delivered as documentation for rebuild); Customer.io workspace configuration including SSO, IP allowlists, and billing settings (account-level, not migratable); Segments and Broadcasts as active audience data (delivered as rule documentation); and transactional message templates as reusable Dynamics 365 templates (delivered as content documentation for manual rebuild). We flag each of these during scoping so there are no surprises at cutover.

Get a quote

Moving from Customer.io 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