---
title: "Attio to Dynamics 365 Migration: Field Mapping & Rollback"
description: "Migrate Attio 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/attio/to/dynamics-365-sales"
---

# Attio to Dynamics 365 migration

We migrate People, Companies, Deals, and activity history from Attio into Microsoft Microsoft Dynamics 365 Sales with the relational dependency chain reconstructed from Attio's API, custom object schema pre-built in Dynamics, and every Deals-to-Companies lookup resolved before any Opportunity record is written to production.

Short answer

FlitStack AI migrates contacts, accounts, opportunities, custom entities and notes from Attio 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.

![](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/attio/to/dynamics-365-sales#what-moves)

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

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

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

Contact Account Opportunity Custom Entity Note

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

## What moves from Attio to Dynamics 365?

Attio's flat CSV export does not include relationship join keys, so Deals arrive in Microsoft Dynamics 365 Sales orphaned from their parent Accounts unless we query relationship attributes via the Attio API before migration.

Read the full summary

We handle this by building the parent-child chain during the transform phase so that every Opportunity receives its AccountId at insert time. Attio's flexible object model (People, Companies, Deals, Custom Objects) maps to Dynamics 365's relational schema (Contacts, Accounts, Opportunities, custom entities) with the same sequencing constraints: Accounts must exist before Contacts, and Accounts must exist before Opportunities. Notes, Tasks, and historical email and calendar sync data attach to the correct Contact and Account records in Dynamics with parent-record references preserved. Attio Workflows and List memberships do not migrate as automation; Workflows require a rebuild inventory for the customer's admin to recreate in Dynamics Flow, and List memberships are denormalized into custom fields since Microsoft Dynamics 365 Sales has no native List object equivalent.

1:1

### People → Contact (and optionally Lead)

Attio People records map to Dynamics 365 Contact with all native and custom attributes preserved.

How it maps

We deduplicate by email address before import to avoid duplicate Contact creation. Role attributes on People (e.g., Primary Contact, Billing Contact) that have no direct Dynamics field migrate to custom Contact fields. If the Attio workspace uses People records for both qualified and unqualified prospects, we can split them into Lead and Contact objects by evaluating a lifecycle or status attribute during scoping, creating a custom field attio\_original\_type\_\_c for audit trail.

1:1

### Company → Account

Attio Company records map to Dynamics 365 Account.

How it maps

Domain from the Company record becomes the Account Website field and is used as the deduplication key. Company must be inserted before any Contact import so that the AccountId reference is satisfied at Contact insert time. If the Attio workspace has Companies linked to other Companies as parent-child, we replicate that as the Account.ParentId lookup chain.

1:1

### Deal → Opportunity

Attio Deals map to Dynamics 365 Opportunity.

How it maps

We resolve the parent Company relationship via Attio's API relationship attributes and write the resulting AccountId on each Opportunity at insert time. Pipeline stages from Attio map to a Dynamics Sales Process and Record Type that we configure before migration. Deal amount, close date, and status (Open, Won, Lost) migrate directly with closedate preserved as a date field rather than text.

1:1

### Custom Object → Custom Entity (customizeable entity)

Attio custom objects (3 on Free, 5 on Plus, 12 on Pro, unlimited on Enterprise) migrate to Microsoft Dynamics 365 Sales custom entities.

How it maps

We pre-create the destination schema including all custom fields, field types, and lookup relationships during the schema design phase. Attio relationship attributes linking custom objects to standard objects (Companies, People, Deals) become Dynamics lookup fields on the custom entity. Plan tier validation happens during scoping: if the source has more custom objects than the destination plan supports, we flag an upgrade requirement or consolidate objects before migration.

1:1

### Notes → Note (annotation)

Attio Notes attached to People, Companies, and Deals migrate to Dynamics Note records (annotation entity) linked via ContentDocumentLink to the parent Contact, Account, or Opportunity.

How it maps

Note body, author, and timestamp preserve. Notes on custom object records link to the custom entity using the custom entity's primary key as the objectid reference.

1:1

### Task → Task

Attio Tasks with assignee, due date, status, and description migrate to Dynamics Task records with Owner resolved via email match to the Dynamics User table.

How it maps

Tasks without a matching Dynamics User enter a reconciliation queue for the customer admin to provision before migration resumes. Status and priority values map directly to Dynamics Task State and Priority picklist values.

******What moves 8 objects

Attio Dynamics 365

- People Contact 1:1
- Company Account 1:1
- Deal Opportunity 1:1
- Custom Object Custom Entity 1:1
- Notes Note 1:1
- Task Task 1:1

\+ 2 more in the mapping below

## How Attio 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                 | Attio                                                                                      | Dynamics 365                                                                                                                  |
| ------------------------- | ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| Data model                | Flexible People-Company-Deals with user-defined custom objects and relationship attributes | Standardized Contact-Account-Opportunity hierarchy with configurable custom entities                                          |
| Lead model                | Single People object with role attributes and lifecycle properties                         | Separate Lead and Contact objects requiring explicit conversion workflow                                                      |
| Pipeline model            | Unlimited pipelines, unlimited stages, per-Deal stage assignment                           | Pipeline-stage model with Sales Processes and Record Types controlling available stages                                       |
| Custom objects            | 3 on Free, 5 on Plus, 12 on Pro, unlimited on Enterprise                                   | Custom entities available from Professional tier ($65/user/mo), no plan-gated ceiling                                         |
| Pricing model             | Per-seat with separate workspace credit consumption for AI enrichment and automation       | Per-user tiered pricing; Professional ($65/user/mo) or Premium with Copilot ($150/user/mo)                                    |
| Workflow and automation   | Credit-based workflow builder with visual trigger-action logic                             | Salesforce Flow with record-triggered, scheduled, and screen variants; no credit consumption model                            |
| Microsoft 365 integration | Gmail and Outlook two-way sync for People and Company records                              | Native Copilot for Sales embedded in Outlook and Teams; automatic email tracking, meeting capture, and AI-generated summaries |

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

### Attio CSV export flattens relationship chains

Attio's workspace export produces flat CSV files per object with no join keys for relationships.

How we handle it

A Deal CSV has no column showing which Company owns the Deal, and a Contact CSV has no column showing which Company the Contact belongs to. We handle this by querying relationship attributes via the Attio API to build the full parent-child chain before writing to Dynamics. Migrations relying on the CSV export alone arrive with Opportunities orphaned from Accounts and Contacts without Account lookups, which breaks pipeline reporting in Dynamics from day one.

medium

### Custom object count gated by Attio plan tier

Attio plan tiers cap the number of custom objects: 3 on Free, 5 on Plus, 12 on Pro, unlimited on Enterprise.

How we handle it

If the source workspace uses more custom objects than the destination Dynamics 365 plan supports (custom entities are available but the total object count per org has practical limits), migration fails on object creation. We audit the source object count and API name during scoping and either recommend an Attio Enterprise upgrade or consolidate source objects before migration begins.

medium

### Attio field types do not auto-match Dynamics field types

Attio allows user-defined attribute types including multi-select, rating scales, currency, and free-text.

How we handle it

Dynamics 365 enforces field types at the schema level, and Dynamics field types differ in precision, max length, and picklist constraints. Multi-select attributes may need to become text fields or option sets; currency fields require decimal precision alignment; date fields require format normalization. We validate field types against Dynamics constraints during the mapping phase and flag any type mismatches before production migration to avoid bulk insert rejections.

high

### Attio Workflows do not migrate to Dynamics Flow

Attio Workflows are credit-consuming automation objects that trigger on record changes or list events.

How we handle it

Dynamics 365 uses Salesforce Flow with record-triggered, scheduled, and screen variants, and the underlying logic structures are incompatible. We do not migrate Workflows as code. We deliver a written inventory of every active Attio Workflow documenting its trigger, conditions, action blocks, and monthly credit consumption so the customer's admin or a Dynamics partner can rebuild equivalent logic in Flow. Credit consumption context helps the admin estimate Flow action count as a sizing reference.

## How the migration runs

1. ### Discovery and scoping

   We audit the Attio workspace via API across all plan tiers, custom objects, relationship attributes, List memberships, and email/calendar sync volume.

   What this step covers

   We validate the custom object count against plan tier to flag any Enterprise-gated objects and recommend consolidation if needed. We produce a written migration scope document listing every object, record count estimate, relationship chain count, and a Dynamics 365 Professional versus Premium edition recommendation based on object count, custom entity volume, and whether Copilot AI is in scope. This phase establishes the migration baseline and pricing fixed-fee quote.

2. ### Schema design in Dynamics 365

   We create the destination schema in Microsoft Dynamics 365 Sales before any data moves.

   What this step covers

   This includes custom entities for each Attio custom object, custom fields typed to match Attio attribute types (with picklist normalization), and lookup fields resolving the relationship chain to standard entities (Account, Contact, Opportunity). If the customer chooses a Lead-Contact split strategy, we add a custom field on Lead and Contact to carry the original Attio object type for audit. We also create custom fields on Contact and Account to receive denormalized List membership values. Schema deploys into a Dynamics Sandbox first for validation.

3. ### Sandbox migration and reconciliation

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

   What this step covers

   The customer's admin or RevOps lead reconciles record counts against the Attio source (Contacts in, Accounts in, Opportunities in, Notes in, Tasks in), spot-checks 20-30 records per object for attribute accuracy, and validates that relationship chains are intact (every Opportunity has an AccountId, every Contact has an AccountId where applicable). Sign-off on the sandbox run authorizes the production migration date.

4. ### Relationship chain extraction and transform

   We query every relationship attribute via the Attio API to build the full parent-child chain map.

   What this step covers

   This produces a lookup table of Deal-to-Company IDs and Contact-to-Company IDs that we apply as AccountId on each Opportunity and Contact insert in Dynamics. We validate all field types against Dynamics constraints, normalize date formats, and resolve Owner references by email match to the Dynamics User table. Owners without a matching User enter a queue for admin provisioning before record insertion resumes.

5. ### Production migration in dependency order

   We run production migration in the correct dependency sequence: Accounts (from Companies) first, then Contacts (with AccountId resolved), then Opportunities (with AccountId resolved from the relationship chain map), then Notes and Tasks (with owner references resolved), then custom entities (with their lookup fields pointing to the parent standard records), and finally activity history from Attio's email and calendar sync API.

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins. We use the Dynamics Web API with batch operations, rate-limit handling, and exponential backoff.

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

   We freeze writes in Attio during the cutover window, migrate any records modified since the last sync, then enable Microsoft Dynamics 365 Sales as the system of record.

   What this step covers

   We validate record counts and relationship chains one final time against the Attio source. We deliver the Workflow inventory document to the customer's admin team for Dynamics Flow rebuild. We support a one-week hypercare window for reconciliation issues raised by the sales team. We do not rebuild Attio Workflows, Lists as active segmentation, or Sequences as Salesforce Sales Engagement cadences inside the migration scope.

![](https://flitstack.ai/platforms/attio.svg) Attio ![](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

**3-5 weeks** Typical, smaller accounts

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

A quote scales with object count, relationship chain complexity, and historical activity volume. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from Attio to Dynamics 365

- Teams already running Microsoft 365 shift to Microsoft Dynamics 365 Sales for native Copilot integration inside Outlook and Teams. Rather than switching contexts to log activity, Copilot captures emails, meetings, and CRM updates directly within the tools sellers already use. Reviewers on G2 and comparison guides cite this friction reduction as the primary driver for switching, especially in organizations where Microsoft productivity tools are the daily operating environment.
- Attio's object-level flexibility becomes a liability at scale. Teams cite steep learning curves for non-technical sales staff, thin native integrations with GTM tools, and reporting that lacks pipeline depth compared to established platforms. Microsoft Dynamics 365 Sales delivers enterprise architecture with Power Platform integration, Power BI reporting, and an established partner ecosystem for organizations outgrowing Attio's developer-friendly model.
- Attio's workspace credit model creates unpredictable monthly costs when automation runs at volume. A single workflow consuming 800 credits on 100 executions drains more than half the monthly allocation on a Plus plan. Microsoft Dynamics 365 Sales per-user pricing is predictable regardless of workflow volume, and Power Automate (included in many Microsoft 365 licenses) handles automation without a separate credit bucket.
- Organizations with complex GTM motions outgrow Attio's reporting depth. Weak pipeline analytics, limited date-based segmentation, and constrained data visualization are consistent themes in user reviews. Microsoft Dynamics 365 Sales with Power BI delivers enterprise-grade pipeline reporting, territory analysis, and multi-dimensional revenue forecasting that scales with the business rather than constraining it.
- Companies with global operations, multi-currency requirements, or enterprise compliance mandates choose Dynamics 365 for its security certifications, data residency options, and built-in audit trails. Attio's feature set targets smaller, technically-forward teams, while Dynamics 365 scales to the operational complexity of upper mid-market and enterprise organizations without requiring a separate security and compliance architecture.

Questions, answered

## Attio to Dynamics 365 migration questions

How long does an Attio to Microsoft Dynamics 365 Sales migration take?

Simple migrations with under 10,000 People records, no custom objects, and no complex relationship chains complete in three to five weeks. Migrations with multiple custom objects, Deals-to-Account relationship resolution, large email and calendar sync histories, or multi-entity workspaces extend to eight to twelve weeks. Very large or multi-org destinations receive individual scoping.

What migrates and what does not migrate from Attio to Dynamics 365?

We migrate People, Companies, Deals, Custom Objects, Notes, Tasks, and activity history (email and calendar sync) with full attribute preservation and relationship resolution. Attio Workflows and Sequences do not migrate as automation code. We deliver a written Workflow inventory with trigger, conditions, actions, and credit consumption for the customer's admin to rebuild in Dynamics Flow. Attio Lists have no direct Dynamics equivalent; list memberships are denormalized into custom multi-select fields on Contact and Account so the data is queryable but not a native list.

We already use Microsoft 365. Is Microsoft Dynamics 365 Sales worth the switch?

For organizations already running Outlook, Teams, and Microsoft 365, Microsoft Dynamics 365 Sales delivers the strongest integration value. Copilot for Sales runs directly inside Outlook and Teams, capturing email and meeting context without requiring sellers to open a separate CRM window. Organizations not yet in the Microsoft ecosystem may find the platform investment harder to justify relative to alternatives with lower per-user pricing.

How does FlitStack AI handle Attio's relationship chains during migration?

Attio's CSV export does not include relationship join keys, so Deals appear without their parent Company and Contacts without their parent Account. We resolve this by querying Attio's relationship attribute API before migration to build a complete Deal-to-Company and Contact-to-Company lookup table. We apply this lookup during the transform phase so that every Opportunity receives its AccountId at insert time. Without this step, Opportunities arrive orphaned from Accounts and pipeline reporting in Dynamics returns zero values.

Do we lose historical email and calendar activity data during migration?

No. Attio's two-way Gmail and Outlook sync generates activity records that we migrate to Dynamics EmailMessage and Event objects attached to the parent Contact and Account via the Dynamics Web API. We reconstruct the Contact and Account references from the Attio API at migration time. Note that email and calendar sync in Attio covers People and Company records only; custom object activity history must be reconstructed from notes or external integrations since Attio does not extend sync to custom objects.

Can FlitStack AI migrate Attio custom objects to Dynamics 365?

Yes. We migrate Attio custom objects to Microsoft Dynamics 365 Sales custom entities with all custom fields, field types, and lookup relationships preserved. The destination schema is created during the approach phase before any data moves. We flag during scoping if the source workspace has more custom objects than the Attio plan tier permits, since exceeding plan limits on the source does not prevent migration but requires plan upgrade or consolidation.

What happens to Attio Workflows and automation after migration?

Attio Workflows do not migrate to Dynamics Flow because the automation models are architecturally different. We do not rebuild them inside the migration scope. We deliver a written inventory of every active Attio Workflow with its trigger conditions, action blocks, monthly credit consumption, and a recommended Dynamics Flow equivalent for the customer's admin to implement post-migration. The credit consumption data helps the admin size the equivalent Flow in terms of action count and trigger frequency.

## 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) [**Twenty CRM to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/twenty-crm/to/dynamics-365-sales) [**Customer.io to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/customer-io/to/dynamics-365-sales) [**Drivecentric to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/drivecentric/to/dynamics-365-sales) [**Housecall Pro to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/housecall-pro/to/dynamics-365-sales) [**HoneyBook to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/honeybook/to/dynamics-365-sales) [**Leadforce CRM to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/leadforce-crm/to/dynamics-365-sales) [**Attio to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/attio/to/salesforce-sales-cloud) [**Attio to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/attio/to/hubspot) [**Attio to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/attio/to/odoo-crm)

## 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 Attio 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)
