Odoo import troubleshooting · practical browser tool
“No matching record found … in field …” is usually a relation problem, not just a CSV problem.
Odoo imports can fail because the CSV itself is malformed, or because a value in the CSV points to a related record that the target database cannot identify. Treat those as different failure classes.
No matching record found for name '…' in field '…'
No matching record found for external id '…' in field '…'
What Odoo is trying to do
Fields such as Country, Product Category, Unit of Measure, Vendor, Attribute, and many other relational fields point to records elsewhere in the database. Odoo’s import documentation explains that relation fields can be matched by name, Database ID, or External ID, and that the related records generally need to exist before the importing record can link to them.
Three checks before changing the CSV blindly
- Confirm the file structure. Make sure delimiter, quoting, row width, headers, encoding, and External IDs are structurally clean.
- Check the target relation. Verify the referenced country/category/vendor/UoM/attribute/etc. actually exists in the database you are importing into.
- Use an unambiguous identifier. Odoo documents External IDs as the safer mechanism when names are duplicated or when relations must be recreated across imports.
What Odoo Import Doctor can help with
The free browser-local Odoo Import Doctor can verify structural CSV issues such as delimiter and row-width consistency, malformed quoting, blank/duplicate External IDs, encoding problems, and optional header comparison against an Odoo export/template.
It cannot know whether a related record exists in your private Odoo database. That remains a target-database check and should stay UNKNOWN until Odoo tests it.
Preflight the CSVUse Odoo’s Test step before Import
Odoo’s official import workflow includes a Test step before Import. That is where database-specific field mappings, relation values, permissions, custom modules, and existing-record state can be validated against the actual target database.
Official Odoo 18 import/export documentation
When the error mentions External ID
Do not assume an External ID that works in one database exists in another. Odoo documents External ID as a unique identifier used to recreate or update relations, but the referenced ID still has to resolve in the target environment. Exporting a known-good sample from the target database is often the cleanest way to learn the exact importable field labels and identifiers.
This page is an independent troubleshooting guide and is not affiliated with or endorsed by Odoo. It does not guarantee a successful import; database-specific validity remains with the target Odoo instance.