Dynamics 365 Sales → Attio

Catalog plan outline

General guidance from the Afterstack catalog for Dynamics 365 Sales → Attio. Not Dynamics 365 Sales or Attio vendor documentation.

Migration friendliness

Dynamics 365 Sales 5/10 · Attio 7/10

Speed to live

Dynamics 365 Sales 3/10 · Attio 7/10

Catalog migration difficulty

Dynamics 365 Sales high · Attio not set

Data to export from Dynamics 365 Sales

• pipeline and deal records
• custom objects
• sequences and cadences
• call and voice logs
• synced email and calendar links
• workflow rules
• saved reports
• campaign and automation records
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: pipeline, accounts, outbound

How the catalogs differ

• Attio is flagged for custom objects. Collapse unused fields before loading them.
• Attio is not flagged for: call and voice logs, campaign and automation records, installed marketplace apps.
• Dynamics 365 Sales is flagged with an open API, which is the export path to test.
• Attio is flagged with an open API for the load.
• Dynamics 365 Sales is cataloged as a fit for: Microsoft 365 campuses.
• Attio is cataloged as a fit for: Product-led and sales-led startups that treat the data model as the product.

Phases

1. Export

   Take Dynamics 365 Sales as the source of truth for this pair. Export pipeline and deal records; custom objects; sequences and cadences; call and voice logs; synced email and calendar links; workflow rules; saved reports; campaign and automation records; installed marketplace apps; AI assistant configuration; records for the catalog use cases: pipeline, accounts, outbound. Microsoft’s enterprise CRM — Copilot on a platform that still feels like Dynamics.

2. Map

   Load into Attio only after the field map is written down. A CRM that treats your data model as the product. Attio is flagged for custom objects. Collapse unused fields before loading them.

3. Prove a sample

   Attio scores 7/10 on speed to live and 7/10 on migration friendliness. Run one sample load and one report the team already uses in Dynamics 365 Sales before a full cutover.

4. Cut over

   Dynamics 365 Sales scores 5/10 on migration friendliness and is marked high difficulty in the catalog. Keep Dynamics 365 Sales readable until the team is working in Attio. Dynamics 365 Sales is the procurement-safe CRM when the rest of the stack is already Microsoft: Outlook, Teams, Dataverse, Azure. Copilot drafts and summarizes on top of a model that was not designed as an AI-native CRM. Teams leave when they wanted a quieter sales OS, not another 365 SKU.

Dynamics 365 Sales to Attio: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not Dynamics 365 Sales or Attio vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from Dynamics 365 Sales

Dynamics 365 Sales stores accounts, contacts, leads, and opportunities in Dataverse. The file export Microsoft documents for that model-driven app, opened 2026-10-18, is Export to Excel. The static-worksheet article is the one that produces a snapshot you can hand to someone who cannot sign in. Static worksheet exports every page of the current view. Static worksheet (Page only) exports the page you are looking at. A model-driven app lists up to 50 rows per page by default, and a static export can include up to 100,000 rows at a time. The file keeps the view's columns, order, sorting, and widths. You cannot change columns on a system view unless you are a System Administrator or System Customizer, or you build a view in Advanced Find. Currency leaves as a number with no currency sign. Date and time values display as a date, while the cell still holds the time. Calculated and roll-up columns can be edited in the sheet and cannot be imported back into Power Apps. Secured columns behave the same way. Virtual tables are not supported. A dynamic worksheet or PivotTable keeps a live connection and re-authenticates on refresh, which is the wrong artifact for a one-time load. Excel Online can edit rows back into the app and, by design, cannot File > Save As. The pricing page the same day lists Sales Professional at $65.00 per user per month paid yearly, Sales Enterprise at $105.00, and Sales Premium at $150.00 with 1,000 Copilot Credits per user per month. Microsoft Relationship Sales is variable and requires a 10-seat minimum. Footnote 2 says reporting and dashboards include export to Excel. A Free label sits above the Professional card. No trial length is printed. The catalog starting price of 65 matches Professional. The catalog note, updated 2026-10-19, also lists Enterprise at $105 and Premium at $150. The catalog trial flag is not confirmed by a day count on that page, so it was left true.

• Export to an Excel static worksheet — checked 2026-10-18
• Export data to Excel in Power Apps — checked 2026-10-18
• Dynamics 365 Sales pricing — checked 2026-10-18

How Attio imports

Attio's migration article is the door that actually names this source. The Import2 list includes the entry MS Dynamics, on any paid Attio plan, and only an admin can run it. The article says the migration started from Attio's Migrate button is free for Attio users. You open Workspace settings, choose Migrate CRM, and pick the source. Import2 then asks for an account, a sample load, and a full load. The sample creates non-system attributes from the source. Objects map to Attio objects, not to lists. If a person already exists, matched on email, or a company already exists, matched on domain, attribute values on that record are not refreshed. Notes and tasks from the former CRM are still added. Call recordings are outside the service. Undo removes the records that were added and does not remove lists, attributes, or other structures. Phone values need a leading plus and a country code. Domains must be a root such as a hostname, not a full URL, and Attio stores only that root. The article does not paste a Dynamics field dictionary under the MS Dynamics bullet, unlike the Salesforce section, which names Contacts, Accounts, Leads, and Opportunities and excludes Cases. Do not copy that Salesforce list onto Dataverse. If the workspace already has mailbox-synced people, the article's preparation is to disconnect those mailboxes and delete existing people and companies before the run, or accept that existing rows will not take new attribute values. CSV remains the fallback, on every plan, with a required header and ceilings of 100,000 rows, 100 columns, and 100 megabytes, and it still refuses notes. Attio's pricing page shows Free at $0, Plus at $44 per user per month or $35 annually, Pro at $99 or $79 annually, Enterprise with no printed fee, and a 14-day Pro trial. Import2 itself is not on the free plan. The catalog's $0 start, free-plan flag, and those paid figures match the page.

• Attio migrate from another CRM — checked 2026-10-18
• Attio CSV import — checked 2026-10-18
• Attio pricing — checked 2026-10-18

Object and field mapping

• MS Dynamics is a named Import2 source. The article does not list Dataverse tables under that name. Treat account, contact, lead, and opportunity coverage as unknown until the sample migration shows the objects.
• A static worksheet contains only the columns in the view. A system view's columns stay fixed unless a System Administrator, a System Customizer, or an Advanced Find view changes them.
• Attio's company match, stated generally on the migration article, is the domain. A Dynamics account name is not that key. A website column has to be a root domain, or the row errors.
• Attio's person match is the email. Dynamics contact email is the column to test in the sample, not the account telephone.
• Currency exports as a bare number. Attio will not infer a currency symbol that the worksheet removed.
• Calculated and roll-up values can sit in the sheet and are not writable back to Dataverse. They are also not a live formula in Attio.
• The 100,000-row static export cap and Attio's 100,000-row CSV cap are separate ceilings. A view that hits the Microsoft cap is truncated before Attio sees it.
• Leads and opportunities may need their own views. Page-only export grabs 50 rows unless you change the view. That is not a full table.
• Copilot summaries, Sales Close Agent, and the 1,000 Premium credits are license features. They are not columns in the static worksheet article.

What will not carry over

• A Dynamics field map. Import2 names MS Dynamics and does not publish one.
• Call recordings. The migration article excludes them.
• Attribute updates on people and companies that already match. Notes and tasks can still be added.
• Lists and attributes created during a run, if you later undo. Undo deletes imported records only.
• Live refresh from a dynamic worksheet. That file stays connected to Dataverse. It is not a cutover extract.
• Virtual tables. Export to Excel does not support them.
• Security roles, business process flows, and Power Automate flows.
• A trial length. The pricing page did not print one. The catalog trial flag was left unchanged.
• Relationship Sales pricing. The page says contact a specialist, with a 10-seat minimum.

Cutover checklist

1. Decide Import2 versus a worksheet. Import2 requires a paid Attio plan and an admin. The free Attio plan can take a CSV and cannot run Import2.
2. In Dynamics, build a view that already has the columns you want. Do not expect to add columns on a system view at export time.
3. Choose Static worksheet, not Page only, unless you intend to export one 50-row page.
4. Stay at or under 100,000 rows per export. Split the view with a filter if the table is larger.
5. Do not use Excel Online Save As. The article says that path errors. Save the static file from the download.
6. Strip currency formatting expectations. The sheet has numbers only.
7. Run Import2's sample before the full load. Inspect the attributes it creates. Archive the ones you do not want.
8. If people already exist from mailbox sync, either clear them the way the article describes or accept that their attributes will not update.
9. Format phones with a leading plus and country code before a CSV fallback.
10. Keep Dynamics as the system of record until the sample's accounts and contacts have been counted.
11. Quote Professional at $65, Enterprise at $105, and Premium at $150 per user per month paid yearly. The catalog's 65 matches Professional, and the note lists Enterprise and Premium.
12. Quote Attio from its pricing page, including the 14-day Pro trial. Import2 is not on the $0 plan.

Common pitfalls

• Copying the Salesforce Import2 object list onto Dynamics. That section is source-specific, and it excludes Cases. The MS Dynamics bullet has no such paragraph.
• Exporting a dynamic worksheet and treating the refresh link as a file you can reload later offline.
• Hitting the 50-row page default by choosing Page only.
• Expecting calculated columns to round-trip. They export, and they cannot be imported back.
• Running Import2 on the free Attio plan. The article limits it to paid plans and to admins.
• Undoing a migration and assuming the new attributes disappeared. They remain.
• Reading the Free label on the Dynamics pricing page as a $0 product. The priced cards start at $65. No day count was printed.

Related catalog pages

• What should replace Dynamics 365 Sales? — Switch narrative
• Attio product page — A CRM that treats your data model as the product.
• CRM & sales category — Catalog hub for this category