Understanding Data Access: Fundraise Up vs. CRM

Exporting data: reporting vs. querying

Limitation: filtering is limited to preset options

Exports support filtering, but only by the preset filters available for the selected export type or template. They are not designed for open-ended querying across every available field.

• Example: You cannot export only donations where “Supporter covered fees = Yes.”
• The Fundraise Up way: Choose an export template (for example, Successful donations) and use the available preset filters such as Date, Payment method, or Campaign.
• The CRM way: If you need segmentation based on supporter behavior or custom field values, sync your data to a CRM where advanced querying is supported.

Limitation: exports do not include change history

Many exports are snapshots of your data at the moment the export is generated.

• Example: If a supporter updates their email today, an export run tomorrow will show only the new email address. It will not show the previous value or that a change occurred.
• Note: For recurring plans, you can also use the Recurring plan changes export type, where each row represents a single change event (what changed, when, and who made the change).
• Recommendation: If you need broader change tracking beyond what’s available in export types, compare multiple exports externally, or use the Audit Log for investigating specific changes.

Limitation: exports are flat datasets

Exports are designed as flat rows for analysis and operational workflows. They are not designed to reconstruct full data history or complex relationships across objects.

Change tracking: what you can and cannot do

Fundraise Up does not provide CRM-style change history through exports.

• Changes to supporter records, recurring plans, and other objects cannot be tracked through a single export.
• To reconstruct change history, organizations typically compare time-based “snapshots” of exported data or build external logic to store changes over time.

Tracking changes with the Audit Log

For transparency and troubleshooting, Fundraise Up includes an Audit Log in Settings → Audit Log.

What the Audit Log can do

The Audit Log is designed for investigation. It helps you understand:

• Who made a change (a team member or the system)
• What changed (before and after values)
• When it happened

What the Audit Log cannot do

The Audit Log is not a reporting or segmentation tool.

• It is primarily meant for manual review in the Dashboard.
• It is primarily meant for manual review in the Dashboard, or for pulling event data programmatically via the API, depending on your workflow.
• You cannot use it to generate bulk lists such as “all supporters who changed their address last month.”

If you need a long-term record of changes outside the Dashboard, use an external system and capture events over time.

API and automation

For organizations looking to build custom workflows or work with data programmatically, Fundraise Up offers several paths for connectivity.

• Fundraise Up Zapier app triggers: If you need to trigger an action in another app (like sending a "Welcome" email in Mailchimp or adding a row to a Google Sheet) the moment a donation occurs, we recommend using Zapier. The Fundraise Up Zapier app triggers push data to your other tools in real time.
• Data retrieval via API requests: For more technical needs, such as pulling a specific supporter’s details or syncing records to a custom-built database, you can use API requests. More details can be found in the API documentation.

API limitations (what it does not replace)

• The API is not a “data warehouse” for bulk analytics.
• If you need full historical change tracking, you typically must store events or snapshots externally over time.

Recommended approaches

Use the approach that matches what you are trying to accomplish.

Fundraise Up is the source of truth for transactions. For long-term supporter history, complex reporting, and historical change tracking, a CRM or analytics platform is typically the better fit.