Importing 1,000 Constituents with the same last name

Brooke DennisLister

My organization is in the process of switching our emails from a third party to RE. We have just over 1,000 email addresses that are missing a last name. Since RE requires a last name, would it be okay to import the list with the same last name (my boss wants to use "TBM" as the last name). 

Thoughts? Comments? Is there a better way to import these? 

Dariel Dixon

You need to think about how you plan on using this information.  I think this is a bad idea.  If you don't have a complete name, you'll never be able to add any other action.  If a gift comes, unless it ties back to that specific email address, it will never be able to be actionable.  There's a reason that field is generally required.


On top of that, it might make duplicate management next to impossible.

Candy Sangster

I agree with Dariel. I too think this is a bad idea. You will create a ton of duplicate records along with several other issues. 

Brooke DennisLister

Thank you all so much for answering! I didn't think it was a good idea either, so getting confirmation helped save me!! Thank you!!!! 

Candy Sangster

Glad to hear it! They say it takes a village to raise a child and I think the same statement applies to database work!

Phillip Bicknell

Um, belatedly, I take a different view from others, sorry.


You haven't said that the email addresses might be related to existing records that don't have an email address in them. So I don't understand why people are saying you'd be creating duplicates.


When we lack a last name for a constituent, we use a full-stop (period). And for broadcast emails we use just the first name as salutation - which is presumably what you did on the third-party system.


Obviously, over time, you might acquire more info on these supporters - most likely if they donate - and then you'll be de-duplicating. But I'm quite used to having supporters who only do advocacy and social shares/comments, and since they could be key influencers (or connected to others who are) there's every reason to continue communicating with them.

Karen Diener

Phillip Bicknell‍ thank you for your reply.  IMHO, you should never apologize for having a different perspective!


I was thinking the same thing - that these would not be actual duplicates, because they are unique email addresses.  Although I personally would not be happy with all of these records in my database, if there was no other option, I would tolerate it.

Brooke DennisLister‍ do you know with certainty that these email addresses do not exist in RE?  And do you have any other information about these people aside from their email address, such as which emails they received, opt out information, click-through rates, open rates, or their response to an email?  What would your alternative be if you didn't import them to RE?  Would they just stop receiving emails from your organization, since you are switching from a third-party to RE?  I feel like all of that is worth taking into consideration.


Karen