An asset registry polluted by duplicates skews everything that depends on it. When the source of the problem is an import connector, fixing it takes proven methods. Here's how.
The asset registry (Assets) is meant to be the inventory's source of truth. But when an import connector creates duplicates, the inventory lies: skewed reports, biased decisions, eroded trust.
You can't just bulk-delete the duplicates: you have to understand why the connector generates them (its duplication logic), or they reappear. And you must distinguish a duplicate from a legitimate twin - without losing valid data.
Diagnose the connector's deduplication logic at the source, then execute a sequenced, coordinated cleanup plan that eliminates the duplicates without touching valid data — and prevents their recurrence.
Nimbax diagnosed and fixed a duplicate problem of this kind, restoring a reliable inventory and stabilizing the import process.
Cleaning duplicates without fixing their cause is like draining a bathtub without turning off the tap. Diagnosing the connector comes before the cleanup.
An Atlassian expert gets back to you directly.
