Dynamics 365 CSV: Import Entities and Export Clean CRM Extracts

Dynamics 365 Speaks Dataverse — CSV Is Still the Migration Language

CRM and ERP admins in the US, UK, Australia, Canada, and Europe still move accounts, contacts, leads, and custom entities with CSV (and Excel templates) through Power Platform import wizards. The platform is powerful; the file must match logical names, option-set values, and lookup references — or rows fail quietly while dashboards look “complete.”

Export vs Import

Two different risk profiles.

Step-by-Step: Export a Clean Extract

Reporting / handoff path.

• Build (or reuse) a system view with only the columns you need.
• Export to Excel/CSV per the current Dynamics / Power Apps UI.
• Archive raw as entity-dynamics-YYYY-MM-DD.csv.
• Open in Online CSV Editor; keep GUIDs and account numbers as text.
• Convert to Excel for stakeholders who will not touch Dataverse.
• Document the view name — exports are not “the whole table.”

fullname,emailaddress1,telephone1,parentcustomerid,statuscode
Alex Rivera,alex@acme.example,+1-415-555-0100,Acme Corp,Active
Sam Chen,sam@beta.example,+44-20-7946-0958,Beta Ltd,Active

Step-by-Step: Import with a Data Map

Do not skip the map.

• Download the Excel/CSV template for the entity when available.
• Align source columns to Dataverse fields (logical names help).
• Resolve option sets to exact labels or values the map expects.
• Resolve lookups (Account, Owner) with names/GUIDs that exist.
• Prefer ISO dates; watch timezone on DateTime fields.
• Import a small pilot; review failures; fix; then full load.
• Decide create vs update strategy (alternate keys / duplicate detection).

Lookups, Owners, and Option Sets

The three ways imports “succeed” incorrectly.

• Lookup by name is fragile if duplicates exist — prefer GUID when possible.
• Owner must be a valid user/team; display names alone often fail.
• Option set typos create blank fields or rejected rows.
• Business process flows / required fields: missing values fail late.

Locale and Encoding

Global Dynamics tenants.

• UTF-8 for names with diacritics (DE, FR, ES).
• Semicolon CSVs from European Excel: convert before US-centric parsers.
• Currency and decimal commas: normalize before numeric fields.
• Phone numbers: keep as text; leading zeros matter in UK/AU.

Security and Compliance

CRM extracts are personal and commercial data.

• Limit who can export large contact sets.
• Redact before sending to freelancers.
• Align retention with GDPR/UK GDPR and your DPA.
• Prefer browser-side cleanup for sensitive slices.

Common Mistakes

Admin regret list.

• Importing into the wrong environment (sandbox vs prod).
• Updating by email without a defined alternate key → duplicates.
• Excel scientific notation on GUIDs and long IDs.
• Assuming export includes related records automatically.
• Ignoring failed-row reports after “import completed.”

Best Practices

Treat every import like a production change.

• Version CSVs with entity + environment + date.
• Keep a field map spreadsheet outside Dynamics.
• Always pilot; always read failure logs.
• Freeze source systems after cutover.
• Cleanse in Online CSV Editor before the wizard.

Why Use Convert CSV Online?

Convert CSV Online is free, browser-based, and requires no account for everyday conversions. Prep Dynamics import sheets in the Online CSV Editor, fix delimiters, and convert exports to Excel for stakeholders — useful for US, UK, AU, CA, and EU CRM teams.

Conclusion

Dynamics 365 CSV imports succeed when fields, option sets, and lookups match Dataverse reality. Export from intentional views, map carefully, pilot every load, and protect CRM PII.