Mapping constituent relationship fields

IMPORTANT NOTE: If you are exporting constituent relationship data and re-importing it in order to make a bulk update, make sure you include the LGL Constituent ID in your export. When re-importing, ensure that you set up a mapping for this field so that the bulk change you are making will occur in the correct constituent records.

Required fields

To create a relationship between two constituent records, LGL must recognize two separate constituent records in your import file. In addition, you must specify a) the direction of the relationship (for example, "relationship to" and "relationship from", and b) the name of the relationship (the value in the "Relationship type" column, such as "spouse" or "child"). 

If you are creating new constituent records, your spreadsheet must contain at least First Name, Last Name, or Organization Name data for both constituents. If you are updating records using match criteria, all fields needed for matching must be present (i.e., first and last name or organization name, and email address). if you are updating using either an External Constituent ID or an LGL Constituent ID, no name fields are required.)

NOTE: If your import spreadsheet contains a column for "Relationship to" and a column for "Relationship from" and you map these fields in your import mapping, the mapping will automatically be set to "Constituent #2". Also note that if you use the same column headers twice (such as "First name" and "Last name" in the first example below), the Flex Importer will assign the second one(s) to "Constituent #2".

Special fields

There are no special fields in this case.


Import file 1

Field mapping 1

Import file 2

Field mapping 2

Record Preview

See above and to the right two screenshots up: The defaults, or rules, placed on the "Last name" field for constituent #3, and the results of the import in Greg Brady's constituent record (Individual details).