Mapping contact info: Email addresses
NOTE: If you are exporting email address data and re-importing it in order to bulk update it, make sure you include the LGL Constituent ID and the LGL Email ID in your export. When re-importing, ensure that you set up a mapping for these fields so that the bulk change you are making will occur in the correct constituent and email address record.
The key with email address data is to place no more than one email address per cell in any given column. The Flex Importer looks for the pattern of an email address based on the "@" symbol and dot (".") symbol. If there are multiples of either of these characters, the email address would be classified as invalid.
Email address is required.
Examples showing how to map email addresses
Please refer to the examples below to see how to format your data in multiple cases. For each example, follow the mapping shown in the corresponding screenshots as you're mapping your own fields in the Flex Importer.
Example #1: A column for each email address type
Example #2: Two columns for each email address type