Every Dynamics 365 project I have ever been on had the same unofficial integration platform: Excel. The sales manager wants the pipeline in a spreadsheet, the migration team has customer lists in workbooks, and someone in finance maintains “the real numbers” in a file called final_v7.xlsx. You can fight this, or you can learn the three built-in Excel features that make it painless: export, templates, and import. This post is a tour of all three — no add-ins, no third-party tools.
Export: four flavors, not one
On any view, open the command bar overflow (the ⋮ button) and expand Export to Excel. Most people click the top option and never notice there are actually several distinct exports.
Static Worksheet is the one everyone knows — a snapshot of the view as it looks right now, up to 100,000 rows. The moment it downloads, it starts going stale. Static Worksheet (Page only) exports just the rows on the current page. The interesting ones are the other three: Open in Excel Online opens the data in the browser and lets you edit and save changes back into Dynamics; Dynamic Worksheet gives you a workbook with a live connection, so hitting Refresh in Excel pulls the current records instead of the ones from last Tuesday; and Dynamic PivotTable does the same but drops the data straight into a pivot. If somebody on your team re-exports the same view every Monday morning to update “their” spreadsheet, a dynamic worksheet replaces that ritual entirely.
One thing worth knowing: the export respects the view. Columns, filters, sort order — what you see is what lands in the workbook. So before exporting, shape the view first (I wrote about editing view columns and filters a few months back). It is much faster than deleting spreadsheet columns after the fact.
Excel templates: the report that formats itself
The plain export gives you raw rows. Excel templates give you the formatted version — your charts, your pivot tables, your conditional formatting — refilled with fresh data on demand. The same overflow menu has an Excel Templates section.
The workflow is simple: Download Template gives you a workbook wired to the entity’s columns; you open it in Excel and build whatever you want on top of the data table — pivot charts, summary sheets, formatting; then Upload Template brings it back. From then on, anyone can pick that template from the menu and get a freshly populated copy from whatever view they are standing on. Templates uploaded from here are personal; an administrator can share them with the whole organization from Settings, the same place Word templates live. If you have a monthly account review deck that always starts life as an export plus twenty minutes of formatting, this is the feature that deletes the twenty minutes.
Import: the road back in
Getting data out is half the story. The same menu has Import from Excel (with CSV and XML variants), and this is the supported, no-code way to load records — whether that is a migration of a few thousand accounts or a one-time list of leads from an event.
The wizard asks for the file and an owner for the imported records, then walks you through field mapping. A few hard-earned tips. First, start by exporting the target entity to Excel and using that file as your import shape — the column headers match the display names, so the mapping step maps itself. Second, watch your lookups: a column that points at another record (say, Primary Contact) has to match an existing record’s name exactly, and ambiguous matches will fail the row. Third, option set values must match the labels in the system, not whatever shorthand lived in the source spreadsheet. And fourth, do a ten-row test import before the ten-thousand-row real one — failed rows can be downloaded, fixed and re-imported, but a small rehearsal saves a lot of cleanup.
Imports run in the background, and you can check progress and row-level errors under Data Management > Imports in the admin settings. Duplicate detection rules apply during import too, which is exactly when you want them — I covered how those rules work in an earlier post.
Wrapping up
Excel is not going away, so it pays to use the integration Microsoft already built instead of the copy-paste economy that grows up around every CRM. Use dynamic worksheets for the recurring exports, an Excel template for anything that needs formatting, and the import wizard — after a small test run — whenever a spreadsheet needs to become records. All of it is in that one overflow menu that most users never expand.
