Donations import
Each row holds supporter, donation and payment. File format, values and deduplication are described in CSV Imports.
Supporter columns
The same as in the supporters import, except tags and
note, which here are called supporter tags and supporter note.
Campaign, donation, and payment columns
| Column | Required | Description |
|---|---|---|
campaign name | yes (or a fallback campaign) | Campaign name. Matched by title (case-insensitive). If it does not exist, it is created. |
donation external ref | no | External reference of the donation. Rows with the same value merge into a single donation. |
payment method | yes | Label of the manual payment method. If it does not exist, it is created. |
amount | yes | Payment amount, format x.xx (e.g. 10.00). |
payment date | yes | Payment date, ISO 8601. |
donation tags | no | Donation tags (cell in quotes if it contains multiple values). |
custom_<key> columns can be custom fields of type supporter or donation
(see Custom fields).
Fallback campaign
In the import dialog you can set a fallback campaign for rows with an empty
campaign name. Without either, the row is discarded.
Grouping payments into a donation
To put several payments under one donation (e.g. a monthly contribution) use the
same donation external ref on all its rows. Without donation external ref
each row is a one-off donation.
The donation's amount and date come from the first row in the file with that reference.
Only manual payments can be imported, not Stripe, PayPal or other automatic methods. The grouping donation is always one-off, even if the payments are actually recurring: the collected total does not change.
Payment methods
payment method is looked up by label, case-insensitive, among the
organization's manual methods. If it does not exist, it is created.