Released: February 19, 2026
Earlier this month, we released enhancements to handling identities in imports. As part of a broader suite of updates, this release introduced stricter controls around matching and identity field updates—strengthening data integrity and preventing unintended changes to critical identity fields.
Today, we released a further refinement which restores some former functionality. When multiple identities are used to match a contact, imports can now update an Identity field if it is empty or null—allowing you to create new identities (such as a Common App ID). However, existing Identity values that are already populated will remain protected and cannot be overwritten or modified.
This update builds on the recent enhancements to identity handling within imports by introducing a controlled refinement to identity field updates.
When multiple identities are used to match an existing contact during an import:
Identity fields can now be populated if they are currently empty or null.
This allows imports to create new identity values, such as adding a Common App ID to an existing contact.
Identity fields that already contain a value remain protected.
Existing identity values cannot be overwritten or modified through imports.
This ensures that identity matching remains strict and reliable, while still allowing institutions to enrich records with newly available identifiers when appropriate.
This update strikes a balance between flexibility and protection by allowing new identity values to be added when missing, while continuing to safeguard existing identity data from unintended changes. Institutions can confidently enrich contact records—such as adding a Common App ID—without risking overwrites of established identifiers. The result is stronger data integrity, more reliable matching, and greater confidence in the import process overall.
