Send new and changed gift history after the initial load

For GiveCampus constituent data and imports.

For the ordinary gift-history feed, begin with the required historical load, then send new or changed gifts using the same approved configuration and stable constituent/gift identifiers. An unchanged historical gift does not need to be resent merely to remain in the default imported-gift history. A changed gift should retain the configured identity so it updates the existing record rather than creating a second gift.

Before using a changes-only feed, inspect the configuration's Missing Gift Deletion behavior. Imported gifts and their designation selections are preserved by default when omitted; a configuration with deletion of missing imported gifts enabled has a different source-file contract and may require a complete file. Do not assume the default applies to every existing integration. Also review other associated record types in a mixed file: their cleanup rules can differ from gifts. Validate a small representative import and its errors before scheduling the feed. See the existing sections on delta files, native/imported overlap and gift identity for the related boundaries.