Product Data Import in Dynamics 365: Avoiding Duplicate Records
Importing a supplier catalog into Dynamics 365 without checking existing records creates duplicates that split inventory and pricing. Here's how to import safely.
The Dynamics 365 import wizard is genuinely easy to use — map a spreadsheet’s columns to fields, hit import, done in ten minutes. That ease is exactly why duplicates slip in so easily. The wizard checks that your data fits the schema. It doesn’t check whether the product you’re importing already exists in the system under a different number.
Where it goes wrong
A supplier sends an updated catalog. Someone maps the columns and runs the import. If that supplier’s part numbering differs even slightly from what’s already in Dynamics — a dash removed, a suffix added, a different case — the import creates new product records instead of updating existing ones. Inventory for what should be one item is now split across two records. Pricing rules applied to one don’t apply to the other. Reporting quietly undercounts.
This compounds with every import. A distributor running quarterly updates from a dozen suppliers can accumulate hundreds of duplicate product records a year, each one invisible until someone notices stock counts don’t add up.
What a safe import actually requires
Before any row becomes a new product record, it needs to be checked against what already exists — using manufacturer part number or GTIN where available, and normalized attribute matching (description, specs, unit of measure) where identifiers are missing or inconsistent. Matches above a confidence threshold update the existing record; everything else queues for a quick human check rather than silently creating a duplicate.
That check has to happen on every import, not just the first one. A one-time cleanup after duplicates accumulate is real work; catching them at the point of import is a fraction of the effort and prevents the report-reconciliation headache entirely.
| Import approach | Result |
|---|---|
| Direct wizard import, no identity check | New product record created regardless of existing match |
| Identity check before import | Existing record updated; only genuinely new products created |
Already have a Dynamics import that’s creating duplicates? Book a 30-minute call and bring a recent import file.
Related reading
FAQ
Does the Dynamics 365 import wizard prevent duplicate products?
No. It validates that data matches the expected schema but doesn’t check whether an incoming row already exists as a product record under a different identifier or spelling.
How do you prevent duplicates when importing supplier data into Dynamics 365?
Match incoming rows against existing records using part numbers or GTINs where available and normalized attributes where they aren’t, before the import creates a new record — updating a confident match instead of duplicating it.
Claro
Stop maintaining this by hand
Claro keeps product and supplier data trusted as catalogs change — matching, deduplication, enrichment, and validated write-back into the systems you already run.
Book a demo