What is a known limitation of the NPSP MergeContacts feature?

The limitation of the NPSP MergeContacts feature related to encrypted contact names indicates that when a contact's name is stored in an encrypted format, the merge process cannot access this data correctly. Encryption is a security feature designed to protect sensitive information, such as personal identifiers, by converting them into a format that is not readable without proper decryption. This makes it impossible for the MergeContacts feature to function correctly because it relies on being able to read and manipulate the contact's name.

In this context, the other options do not align with the capabilities and functionalities of the MergeContacts feature. For instance, it does work with standard and custom objects, rather than being limited to just custom objects. Additionally, while the MergeContacts feature may prioritize certain fields, it does not strictly limit itself to only basic fields; it can handle a variety of data types. Lastly, the feature is not limited to specific field data types—they should comply with established data handling rules, but are not exclusively limited in that way.