Migrate from Attio to Microsoft Dynamics 365 Sales

Attio People records map to Dynamics 365 Contact with all native and custom attributes preserved. 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.

Attio Company records map to Dynamics 365 Account. 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.

Attio Deals map to Dynamics 365 Opportunity. 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.

Attio custom objects (3 on Free, 5 on Plus, 12 on Pro, unlimited on Enterprise) migrate to Microsoft Dynamics 365 Sales custom entities. 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.

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. 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.

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. 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.

Attio Lists are workflow-context record collections with no direct Microsoft Dynamics 365 Sales equivalent. We extract list memberships from the Attio API and denormalize them into a custom multi-select picklist field on the relevant object (Contact or Account). For example, a Contact appearing on the High-Value Prospects list receives the picklist value 'High-Value Prospects'. Dynamics admins can use this field for segmentation, filtered views, and targeted workflows after migration.

Attio's two-way Gmail and Outlook sync for People and Company records generates email and calendar entries that migrate to Dynamics EmailMessage and Event records attached to the parent Contact and Account. We query the sync history via the Attio API, reconstruct the Contact and Account references, and insert via the Dynamics Web API with WhoId (Contact) and Regarding (Account) resolved before each write. Email body, timestamp, and direction (sent/received) preserve. Note that email and calendar sync in Attio only covers People and Company records; custom object activity timelines must be reconstructed from notes or external integrations.