Skip to main content

​
Overview

Each designation can carry a Salesforce ID, the ID of the matching General Accounting Unit (GAU) in Salesforce. WeGive uses it to send gifts to the right GAU and to match GAUs coming back from Salesforce. You can see the Salesforce ID on a designation’s detail page, but you can’t change it on the Edit Designation page. The field isn’t offered there on purpose: the ID is normally filled in automatically by the Salesforce sync. You can set it yourself with the Import Wizard, as described below.

​
Where the ID normally comes from

  • A designation created in WeGive: when a gift to it is synced, WeGive creates a matching GAU in Salesforce and saves that GAU’s ID on the designation.
  • A GAU created in Salesforce: when WeGive pulls GAUs from Salesforce, each one is matched to a designation by Salesforce ID. A GAU that doesn’t match any existing designation creates a new designation in WeGive. WeGive does not match on the name.

​
Set the Salesforce ID with the Import Wizard

Use this when a designation already exists in WeGive and you want to tie it to a GAU that already exists in Salesforce.
  1. Build a CSV with one row per designation. Include a column that identifies the designation, either its WeGive ID (best) or its Name, and a column with the GAU’s Salesforce ID. Copy the ID from Salesforce exactly as it appears (the 18-character ID is safest).
  2. Go to Data > Imports and click + to start a new import.
  3. Choose the Update action and the Fund object type (designations are called Funds in the Import Wizard).
  4. Upload your CSV.
  5. Map the identifier column to WeGive ID or Name, and map the ID column to Salesforce ID. (Organizations that use NPC can map NPC ID the same way.)
  6. Set Primary Identifier to the identifier you mapped in step 5.
  7. Run the import, then download the results file to check for row errors.
What to expect:
  • Update never creates designations. A row that matches nothing fails with “Fund does not exist”, and a row that matches more than one designation (for example, two with the same name) fails with “Multiple funds found”. Use the WeGive ID to avoid this.
  • Only cells with a value are written. A blank Salesforce ID cell leaves the existing ID unchanged, so an import can’t be used to clear an ID.
  • Once the ID is saved, WeGive treats the designation as already linked: later syncs update that GAU instead of creating a new one.
Every new account starts with a General Fund that has no Salesforce ID. If your Salesforce already has a General Fund GAU and you sync before linking them, WeGive can create a second GAU in Salesforce for gifts to the General Fund, and can create a second designation in WeGive when it pulls your existing GAU. To avoid that, run the import above for your General Fund (and any other designations that already have GAUs) before your first sync or first synced gift. If a duplicate has already been created, contact WeGive Support so it can be cleaned up.
Last modified on November 3, 2026