Gift Amount versus Designation Amount

In the School Dashboard → Data Import gifts configuration, Amount is the full gift total. Designation Amount is the portion allocated to that designation.

How do I import one gift split across designations?

When mapping the gift file, include the gift's constituent identifier, Gift Transaction ID, required gift fields, and the Designations fields. Put each designation on its own row. Repeat the same constituent identifier, transaction ID, and full gift Amount on each row; enter that designation's individual share in Designation Amount. Each designation amount must be greater than zero.

For example, a $120 gift split equally between Fund A and Fund B uses two rows. Both rows have the same constituent ID and gift transaction ID and an Amount of 120. The Fund A row has Designation Amount 60, and the Fund B row has Designation Amount 60. This represents one $120 gift with two $60 allocations, not two $120 gifts.

The gift's identity includes its parent constituent and the fields configured as unique, normally Gift Transaction ID. Within that gift, the designation name, Backend, and Write In values distinguish designation selections. These designation fields have built-in identity rules even though they do not offer a Unique Field checkbox. Do not invent a new gift ID for each allocation simply to prevent the repeated gift from matching. Keep gift-level values consistent; when rows resolve to the same gift in one import, the first gift-level record is retained.

Do not put multiple fund names into one Designation cell separated by semicolons and assume the importer will split them into separate allocations. Map separate designation records and check a representative gift in the import results.

Must an imported designation already exist in Online Giving?

No. For this school-level historical gift import, the designation name and Backend can be retained even when there is no matching school-level Online Giving designation. A matching Backend links the imported allocation to that designation; an unmatched allocation remains unlinked. It is not sent to Blackbaud Gifts to Review solely because its Backend is unknown to the GiveCampus designation catalog.

This is different from exporting a GiveCampus gift to Raiser’s Edge NXT, where fund mapping errors can prevent export. Identify whether the question concerns importing historical gifts into GiveCampus or exporting new gifts to NXT before applying fund-matching troubleshooting.

Review a sample imported gift and its allocations before running a full file.