External references: how PVology prevents duplicate records
Short answer: Every record that comes in keeps the other system's ID as an external reference. The next import or sync finds it by that reference first, then by the mapping's ID field or dedupe keys (such as a project code, web domain or e-mail). A name alone never matches, and an ambiguous match waits for a person.
Verified for PVology 0.61.0 · updated 2026-10-11
When to use this
You import or sync the same records more than once, or see a record skipped with Ambiguous match.
Sign in to read the full help article
This is a free preview. Creating a PVology account is free.
Need more help? Contact PVology