NetSuite says the record already exists
Find the existing record before deciding whether to add a new one or update what is already there.
A custom record already uses this identifier
Message looks like
There is already a Custom Record Entry with that name
What it means
Another custom record already uses this name or identifier, so NetSuite will not create a second one.
Import context: General imports.
Check this first
Search the record type for the value and decide whether the row should update the existing record instead.
Show the steps
Steps for this error
- Search the custom-record type for the external ID or name used by the failed row.
- Decide whether the row should update that record or create a different one.
- Use Update with the existing record’s verified identifier, or assign a genuinely new identifier for Add.
If that looks right
Documentation checked September 16, 2026.
An entity already uses this external ID
Message looks like
This entity already exists
What it means
The external ID on the row already belongs to another entity, and two entities cannot share one.
Import context: Leads and prospects.
Check this first
Search entities for the failing external ID and decide whether the row should update that record instead.
Show the steps
Steps for this error
- Another entity already uses the external ID being assigned. Find it with an entity saved search filtered to External ID is the failing value, showing ID, name, and type.
- Decide whether the row should update that record instead of reusing the identifier.
- Correct the external ID in the file and retry one row.
If that looks right
Documentation checked September 16, 2026.
A revaluation already uses this item, location, and date
Message looks like
An Inventory Cost Revaluation Already Exists for this Item, Location, and Date
What it means
A revaluation already exists for this item, location, and date, and each combination can only be used once.
Import context: Inventory cost revaluations.
Check this first
Find the existing revaluation and decide whether to update it or change the date.
Show the steps
Steps for this error
- Each revaluation must use a unique combination of item, location, and date. Look for an existing revaluation with the same three values.
- Change the date or update the existing record instead of adding another for the same combination.
- Retry one row.
If that looks right
Documentation checked September 16, 2026.
The transaction already exists
Message looks like
This record already exists
What it means
A transaction with this identifier already exists, so an Add import will not create another one.
Import context: Transactions.
Check this first
Find the existing transaction and decide whether the row should update it instead.
Show the steps
Steps for this error
- Search the target transaction type for the external ID or transaction identifier in the failed row.
- Decide whether the row is a new transaction or an update to the one found.
- Use the verified existing identifier for Update, or supply a new unique identifier for Add.
If that looks right
Documentation checked September 16, 2026.
Related errors
- NetSuite cannot identify the record to import
- NetSuite cannot match an item in a CSV import
- The item unit or record type does not match
- NetSuite could not match a record or parent item
Book a free 30-minute look at your import error
Bring the error and your file to a screen share and I will dig into it live. Thirty minutes is usually enough to find what is wrong and tell you what fixing it takes. Sometimes that settles it on the call; when it does not, you leave with a straight answer instead of a mystery. No cost and no obligation.
An import that keeps failing is often the first visible sign of a larger setup problem. Most of my client work starts exactly here: somebody mid-import, a file that will not load, and nobody on their side to email. If a migration or implementation sits behind this error, that is the work I do every week.