Sync data to custom objects in Salesforce

The Salesforce, Salesforce NPSP, and Salesforce Agentforce for Nonprofits integrations can now sync data to custom objects in your Salesforce org. Each one used to write only to a fixed set of standard objects, so organizations that route incoming data through a staging object, or that keep fundraising records in an object installed by a managed package, had to build their own automations to move the data. Those objects are now available as sync destinations.

You configure them on a new Custom objects tab, next to Mapping rules and Special rules in your integration settings. The tab lists every object that your connected Salesforce user can write to. Choose one, map Fundraise Up fields or a static value to its fields, and save — the controls are the same ones that you use for mapping rules. A custom object can be mapped to only one entity — donations or recurring plans. You can't map both to the same custom object. To sync both donations and recurring plans, use two custom objects.

Fundraise Up writes to your custom objects on every sync, after it finishes with the standard objects. The first sync creates a record in each mapped object, and later syncs update that record rather than creating a duplicate. Fundraise Up handles each custom object on its own, so an error in one mapping does not stop the standard sync or the other custom objects.

Your mapping rules and special rules are unchanged.

To set this up, see Set up the Salesforce integration, Set up export to Salesforce NPSP, or Set up the Salesforce Agentforce for Nonprofits integration.