We had Customer Support inactivate a large number of constituent records in our LO database. When a record is made inactive/removed in LO, it is no longer considered a valid usable record. If any of these removed constituents were somehow added/imported to LO again (recent engagement, donation,etc) a new constituent record will be created. The new record can not be merged with the existing "removed" record (which has the same email address).

There’s not a duplicate detection tool to identify and merge active and removed records. The present duplicate management tool in LO only checks for active records and does not consider the removed record a dupe as it is no longer a valid record.

However that "removed record" opt in/out status can still get updated after being made inactive. This can possibly cause a compliance issue, as the new record does not obtain that change.

Current fix - The removed record would have to be re-instated by Support, in order for it to get detected and merged with the newer record. We would prefer a more effective and easier solution to this issue.