Import Data Tool - Mapping

The data contained in your source file will be displayed on this page so that you can create a “map” from your source fields to the Panorama Donor Management fields.  This map will give the Donor Management tool the instructions it needs to know where to put the data you’re importing.

Before you begin the mapping process, you can choose how many constituents, addresses, email addresses, and phone numbers you have for each row of data in your source file.  For example, your source file contains multiple rows and each row of data contains one constituent name, two addresses (home and work addresses), two email addresses (personal and work emails), and three phone numbers (mobile, home, and work numbers) then you would choose the appropriate numbers using the drop-down selections.  “Each import file row includes up to 2 addresses and 2 people, each with up to 2 email and 2 phone numbers.”

The mapping table displays the column names along with a preview of the data that is in your source file.  The mapping table shows you the first two rows of data and you can use the arrow icons to move through the rows of data in your source file.

To map the fields, choose an Entity that contains the field that you want to map and then select the Mapping Field in the Donor Management that correlates to the field in your source file.  For example, if you have a “First” column in your source file (for first name), you would choose the Entity >> Constituent and then choose the Mapping Field >> FirstName.  If you have a “city” field in your source file, choose the Entity >> Address and then choose the Mapping Field >> AddressCity.  Proceed through all your import fields and map as many as you desire to the Donor Management fields.  If you do not want to map a field, then choose Mapping Field >> DO NOT IMPORT from the selection.

The Ignore Nulls option instructs the Donor Management tool to ignore columns that have a blank or null value.  This is helpful if you are updating existing constituents and do not want to clear out information of records already in the Donor Management.  For example, you already have “John B. Smith” in the Donor Management as a constituent.  You want to import additional information and update John’s constituent record but your update import file does not contain a Middle Name value in your source file.  If you select the Ignore Nulls option, Donor Management will not clear out John’s middle name when importing and updating his record.  If you do not select the Ignore Nulls option, Donor Management will update John’s middle name to whatever it is in the source file, even if it is blank.

As a shortcut, you can click the Mark all remaining unmapped fields as DO NOT IMPORT

Click the Next button to continue the import process.

Note: If you are importing data that will be updating information already in the Donor Management, you may be prompted to identify an Import Key.  This import key is used to match data in your source file with records already in the Donor Management.  Donor Management will automatically use the Display Name field if that field is mapped.  If you are not mapping the Display Name, then you will be prompted to identify a key.  For example, if you are updating constituent information in the Donor Management, you may want to choose the first and last name fields as your import key since the combination of both of those fields is better than just a first or last name.  To avoid complications caused by identical names, use a unique identifier that is found in both your source file and in the Donor Management.  This will guarantee that you are updating the correct record in the Donor Management.