Recurring gift columns
Every column the Recurring gifts import understands, what goes in it, and where to find it in your old platform's export.
This is the reference for the Recurring gifts import, one row per recurring gift. For the full walkthrough, start with Move recurring gifts to Givable.
Before you start: download the template and the column guide under Settings > Imports > Download a template. Only Amount and Frequency are required; every other column is optional, but the more you bring, the more exactly each gift picks up where it left off.
Common exports map themselves. The field names and report labels of the CRMs Givable connects to, and Stripe's subscription export columns, are matched to the right fields when you upload. Check the suggested mapping anyway.
Donor
Who the gift belongs to. Givable looks for the donor by Supporter Givable ID, then by a CRM id if your file has one, then by your matching rules on the email, name and phone.
| Column | What goes in it |
|---|---|
| Supporter Givable ID | The donor's Givable ID, for example S4VSTYHG. Matches that exact supporter; one that names nobody fails the row. Find it on the supporter list or in a supporter export. |
| Supporter Salesforce id | The donor's contact id in your CRM (15 or 18 letters and digits), for supporters synced from it. |
| Account Givable ID | For a company or organization gift, the account it belongs to, for example A7KQ2M9P. Matches that exact account; one that names nothing fails the row. With no donor columns, the gift goes to the account's primary contact. |
| Account Salesforce id | The same, by the account id in your CRM, for accounts synced from it. |
| Donor email | Used with the name to find the donor when there is no id. |
| Donor first name, Donor last name | Used to find the donor, and to create one when that option is on. |
| Donor phone | Used by your matching rules. |
| Donor street address, Donor street address line 2, Donor city, Donor state or province, Donor postal code, Donor country code | Optional. Used only to create a donor who isn't in Givable yet, when Create donors who are not in Givable yet is on. A new donor needs a last name and either an email or a full address. |
Recurring gift
| Column | What goes in it |
|---|---|
| Recurring gift Givable ID | Only to update a gift that is already in Givable as Migrating and hasn't started, for example RR2SXJW8. Leave it blank for a new gift. |
| Recurring gift Salesforce id | Only to update a gift synced from your CRM that is Migrating and hasn't started: the gift's id in your CRM. |
| Amount (required) | Each installment, for example 25.00. |
| Currency | A three-letter code such as USD or CAD. Blank uses your organization's base currency. |
| Frequency (required) | weekly, biweekly (every 2 weeks), monthly, quarterly, semi-annual (every 6 months) or annual. Common names from other platforms, such as yearly or annually, are recognized. |
| Day of month | 1 to 31, or "last". Blank uses the day of the last paid date or the start date. |
| Start date on Givable | The first day Givable may charge this gift: today or later, as YYYY-MM-DD or M/D/YYYY. Blank uses the import's start date, or waits until you turn the gift on. |
| Last paid date | The last installment your previous platform collected. It can't be in the future. |
| Next payment date | The next payment your previous platform would have taken. It may be in the past, and it must be after the last paid date. In Stripe, the subscription's current period end. |
| End date | Optional. No charge after it. A row whose end date has already passed is refused: that gift has ended. |
| Installments left | Optional. A whole number of at least 1; blank means open-ended: the planned installments minus those already paid. |
| Status | active or paused, in any letter case. Blank is active. Cancelled gifts aren't imported. |
Nothing is charged while a gift is Migrating, whatever these dates say. When it starts, payments missed since the Next payment date (or since the Last paid date) can be collected if you choose to, and the schedule continues on the donor's day of the month.
Allocations
A gift goes to one fund, or is split across up to five.
| Column | What goes in it |
|---|---|
| Fund | The Givable ID of the fund the whole gift goes to, for example FUQ69AD8. Blank uses the import's Default fund. |
| Benefit value | Optional. The value of anything the donor receives for each installment, which isn't receiptable. |
| Receiptable amount | Optional cross-check only. Givable works out the receiptable amount from your fund settings and flags the row when yours differs. |
| Fund 1 to Fund 5 | For a split: each fund's Givable ID. Use these instead of Fund. |
| Amount 1 to Amount 5 | The amount per installment to that fund, for example 15.00. The amounts add up to the gift's Amount. |
| Percent 1 to Percent 5 | The share of each installment, for example 60. The percents in a row add up to 100. Fill amounts or percents in a row, not both. |
| Benefit value 1 to Benefit value 5 | Optional. The non-receiptable value for that fund's share. |
Each fund's Givable ID is on Settings > Funds. Imports never create funds, and a fund name in the file isn't accepted: replace the fund or designation names your previous platform exported with these IDs before you upload.
Previous platform
These keep the link to where the gift came from. They're recorded on the gift and are never charged against.
| Column | What goes in it |
|---|---|
| Previous platform | stripe, authorize.net, paypal, iats or blackbaud. Any other platform is recorded as other. |
| Previous recurring id | The gift's id on your previous platform, for example a Stripe subscription id (sub_...). Up to 64 letters, digits, _ or -. Map this one: importing the file again updates the gift with the same id instead of creating it twice. |
| Previous customer id | The donor's id on your previous platform, for example a Stripe customer id (cus_...). |
| Previous payment method id | The card's id on your previous platform (pm_..., card_..., src_... or ba_... for Stripe). Never a card number. |
| Originally authorized on | Optional. The date the donor first set up the recurring gift. |
Never put a card number in any column. A file with anything that looks like a card number is refused, mapped or not. Cards move from processor to processor directly, then link to gifts with the payment method imports.
Common row problems
You can correct any of these in the preview: select the row's edit button, fix the value in Edit row, and select Save row.
Still stuck?
We're here for you, and no question is too small. Tell us what you were trying to do and what happened, and we'll help you get it sorted.