Skip to main content

​
Fund Data Mapping

This page details the field-level mapping between WeGive fund records and Blackbaud Raiser’s Edge NXT fund records.
Fund sync is pull-only. WeGive fund records are never pushed to Raiser’s Edge — the push method exists only as unused, unimplemented code. Funds referenced by a transaction need to already exist in Raiser’s Edge, with the Raiser’s Edge ID linked on the WeGive side, before that transaction can sync. See Configuration Options.

​
Field Mapping (Raiser’s Edge → WeGive)

That’s the complete mapping — WeGive’s funds table doesn’t have columns for a fundraising goal, category/subcategory, GL account, cost center, parent/child fund hierarchy, campaign or appeal linkage, or tax-deductibility status at the fund level, so none of those sync.

​
What Isn’t Mapped

No code path exists for: fundraising goals or progress tracking, fund categories or hierarchy, GL account/cost center/department attribution, tax/IRS classification fields, custom fields or tags, or recognition/stewardship text fields.

​
Sync Behavior

Pulled on the same fixed 15-minute cron as everything else in this integration. A fund’s raisers_edge_id is the only thing that determines whether an incoming Blackbaud fund updates an existing WeGive fund or creates a new one.

​
Getting Help