Managing duplicate records with RE & LO integration

Lanetta Gilder

Hello!

I hope all is well. Can someone advise on the how to manage duplicate records with the Luminate Online and Raiser's Edge integration? At the organization working with, there are several "anonymous" records with only email information that came over from Luminate. I'm not sure if its because of the original integration or not, but it apparently created multiple records with only email addresses and nothing else (no first or last name). Is it best to clean up the records in RE instead of Luminate? With the current situation, is it advised to de-dup/merge the "anonymous" records in RE and then manually add the various email addresses with no name to Luminate? Please advise. 


How do you manage records that only obtain email information in Luminate? Do you not bring them over in to RE? For email addresses with no name, how would you handle them in Luminate?


Looking forward to the responses and feedback! Thanks again! Take care, be safe and have a good day!

Jeremy Reynolds

Generally speaking, all de-duping is done in RE and it'll push back to LO to merge and deactivate the non-master record.


That said, it's worth revisiting your processes if you're getting email addresses with no other contact info. If you're collecting them into LO and they already exist, LO shouldn't make a dupe (even if you've got allow multiple records with same email selected). If they aren't already in LO, but are in RE, that's a configuration error. Same goes for if LO is collecting more than the email but not transmitting everything through connector.


Assuming all is on the up-and-up, take a look in your RELO settings...there's an option there to auto-process linked records, so anything coming through will skip showing in your constituent window. Saves a metric ton of time when you do something like import a CSV into LO and mass-update records.


Or perhaps you're saying that you're importing email lists straight into RE? Not sure where your lists are coming from in that scenario, but even that shouldn't be making dupes if imported correctly, at least that I know of.