With the core data elements in place—as well as the general architecture of the record—additional qualitative data can be imported.
Leveraging the custom unique ID field imported in Step 2, these additional data points can match directly to existing records. For example, a secondary import file might look like the following upon upload to Slate:
|Unique ID||Constituency Type||Gift Officer||Class Year||Job 1 Name||Job 1 Key|
|123456789||Alum, Donor, Friend||gwashington||1976||Department of Defense||998877|
Testing the Import Process
When testing the import of secondary data, follow the process below to most efficiently ensure that the data is imported in the manner desired:
1. Upload the file in a production environment.
2. Map the data from the file to the appropriate destinations within Slate, including both field value and static mappings.
3. DO NOT run the import.
4. Refresh the test environment.
5. Run the import in the test environment. Evaluate if the data was imported as desired.
6. If any tweaks are needed, make the change in production, refresh test, and run the import in test.
7. Repeat this process until the data is as desired in the test environment.
8. Once the data is importing as desired, run the import in the production environment.