Like the import of donor records, it is recommended to import gifts in batched processes - first creating the gift(s), then matching against a unique gift ID in order to update gift values.
The giving mapping destinations within Upload Dataset work exactly like the mappings within a form (such as an Online Giving form) - and in fact use the same engine to import the data.
Leveraging a Source Format, Planned and Pledged gifts should be imported first. This allows for Received gifts to then be imported, fulfilling any of the planned or pledged gifts. Once the hard-credited gifts have been imported, soft credit can be imported.
Historical Gift Imports - Recommended Method
There are several methods to import historical gift data into Slate and have it all tied together. Our recommended approach is to import External IDs for every pledge, planned gift, and gift. This allows for the most flexibility for future imports - enabling easy updates if an import is completed and several fields were inadvertently left out.
If an institution's current system doesn't assign unique IDs to each gift, pledge, and planned gift, a custom identifier can be created using a combination of data points (such as a record's unique ID + gift date + fund ID) before importing into Slate. The External ID field can handle a maximum of 64 characters.
Best Practice
Importing in the following order - and as separate files - will make mapping the imports more manageable - as well as allow for the appropriate fulfilling of planned and pledged gifts:
- Opportunities
- Pledges
- Planned Gifts
- Gifts
- Soft Credits