This article shows how to set up Raise integration with Donorfy. The Raise integration automatically brings data from Access Raise into Donorfy. When something happens in Raise, such as a new supporter signing up, donating, recurring gift, shop purchase or event tickets purchased, that information is sent to Donorfy and recorded automatically eliminating manual data entry and keeping your records in sync.
Overview
⚠️Important: This integration is currently in early access, and we'd love to hear your feedback as we continue to develop it. If you don't see the integration option in your environment, please reach out to support to get access.
What gets sent from Raise to Donorfy
Supporter Information (Members → Constituents): Raise Member information and communication preferences.
When a Supporter is created or updated in Raise, their details are sent to Donorfy as a Constituent record. This includes:
Name (Title, First Name, Last Name).
Email address.
Phone numbers (landline and mobile).
Postal address (address lines, postcode, country).
Communication preferences (whether the supporter has opted in or out of contact by email, post, SMS, and phone, along with any custom consent purposes).
If the supporter already exists in Donorfy, their record is updated rather than duplicated. Communication preferences are only updated if the incoming data is more recent than what Donorfy already holds.
📌Note: For events, currently only the lead name (primary member) is pushed through to Donorfy. Additional attendees added during the event booking process in Raise are not added to Donorfy.
2. One-off donations with full allocation breakdowns.
When a payment is made in Raise, it is recorded in Donorfy as a transaction. The following information is captured:
Payment amount (the total the supporter paid).
Currency .
Date of payment.
Processing fees charged by the payment provider.
Campaign - determined by the appeal name set in Raise.
Supporter details - if the supporter doesn't already exist in Donorfy, they are created automatically (see section 1 above).
Furthermore, when a transaction is made it may have several components. Donorfy records each of these as a separate line item (Allocation) on the transaction:
Donation - The core donation amount.
Products - Any merchandise or items purchased (matched to Donorfy products by name where possible).
Postage - Shipping or postage charges.
Processing fee offset - An optional amount the supporter paid to cover payment processing fees.
Reconciliation - A small balancing line item added automatically if the components don't exactly match the total payment (this is rare).
3. Recurring Payment Instructions and subsequent payments.
When a supporter sets up a recurring donation in Raise, a recurring payment instruction (RPI) is created in Donorfy. This includes:
Recurring amount (how much is collected each time).
Currency .
Start Date.
Collection frequency (Monthly, Quarterly, Half-Yearly, or Annually).
Collection Day (the day of the month the payment is taken).
Subscription reference (a unique ID linking the Raise subscription to the RPI in Donorfy).
Campaign (determined by the appeal name set in Raise).
Donor's comment (any message the supporter included with their gift).
Supporter details (if the supporter doesn't already exist in Donorfy, they are created automatically (see section 1 above) .
If the supporter chose to cover processing fees, this is recorded as a separate allocation line item on the RPI.
Where the payment is part of a recurring gift, Donorfy also:
Records a collection against the Recurring Payment Instruction (RPI).
Updates the expected payment for that month for that RPI.
Links everything together for reporting purposes.
4. Shop and Events payments
As per the one-off payments details above, payments for shop and event ticket purchases are added to Donorfy. Where the payment is related to an event a Soft Credit is added to the transaction to link the payer and the event participants.
5. Gift Aid status and processing fees, including ‘cover our costs’.
When the integration with Raise is enabled, the Gift Aid tool is disabled within Raise. The donation allocation will be flagged as eligible for Gift Aid recovery in Donorfy.
The process checks for existing Declarations and if non already exist then a new one is added. The eligible transaction is then added to the Active Claim under Financial > Gift Aid.
If the transaction has had Gift Aid already claimed within Raise, then the Transactions is added and the Allocation set as Potentially Gift Aid-able? = No.
Key Things to Know
No duplicates - the integration checks for existing supporters before creating new records.
Name and product matching - Campaigns are matched by appeal name, and Products and Funds are matched by name where possible. If no match is found, the configured defaults are used.
Communication preferences are protected - Donorfy will not overwrite newer consent data with older data from Raise.
Test mode is available - you can run the integration in test mode to verify everything works before going live. The data received from Raise is logged on the Raise integration 'History' tab, so you can see what would have happened.
How the data maps from Raise into Donorfy
Data Processing
Data syncs automatically, typically within a few minutes depending on system load.
No manual imports or exports required.
All activity is logged in the History section.
Campaign and Product Matching
Raise appeals are matched to Donorfy campaigns by name (case-insensitive).
Shop products and Events tickets are matched to Donorfy products and funds by name.
When no match is found, integration default settings are used (Integrations, Raise, Settings).
📌Note: Unmatched transactions can be reassigned later in Donorfy.
Constituent Matching
The system matches constituents using:
Email address.
First and last name.
Phone numbers (landline and mobile).
Address (line 2 and postcode).
For more information about full constituent mapping, see the Duplicates Overview.
Address Mapping
Raise website fields are mapped to appropriate Donorfy address fields with no duplicate entries.
Postcode matching trims leading/trailing spaces and matches case-insensitively.
Configure Integration
Before you begin
Please ensure you have :
Admin access to both your Raise and Donorfy accounts, or coordinate with a colleague who has these user permissions.
All Appeals have a matching Donorfy Campaign (same name) with a default Product and Fund configured, otherwise transactions may sync without a Product or Fund assigned or fall back to the integration defaults.
Step 1: Configure Integration Settings in Donorfy
Log into your Donorfy account and navigate to Integrations.
Click Raise, then click Settings.
Configure the following required fields ( marked with asterisks):
Transactions Defaults:
Default Campaign*- for transactions when no specific match is found.
Default Payment Method*- payment method for all Raise transactions.
Default Bank Account* - where Raise payments are deposited.
Allocation Defaults:
For Shop and Events Products:
Products Default Product* : when product names don't match.
Products Default Fund* : fund for product purchases.
For Postage:
Postage Default Product* : Used for postage charges.
Postage Default Fund* : Fund for postage allocations.
For Cover Our Costs in Raise
Processing Fee Offset Default Product* : used when donors cover fees.
Processing Fee Offset Defaults Fund* : Fund for processing fee allocations.
Recurring Payment Defaults:
RPI Default Campaign* : Campaign for recurring payments when no match found.
RPI Default Product* : Product for recurring payment allocations.
RPI Default Fund* : Fund for recurring payment allocations.
Configure Gift Aid Settings if applicable:
Enable Gift Aid Claimed in Raise? if you process Gift Aid in Raise to prevent double claiming.
Set Add test payments from Raise to Donorfy? to No (recommended) to exclude test transactions.
Click Save Changes.
Step 2: Testing the Integration
Enable Test Mode
Turn on Test Mode in the Donorfy integration settings.
Turn on Integration enabled to begin receiving test data.
Scroll down to Save changes.
What Test Mode does:
Receives and validates events from Raise.
Logs all activity with a [TEST] prefix.
Does NOT create any actual transactions, constituents, or RPIs.
Shows exactly what would be created.
📌Note: Transaction logs show allocation types (Donation and Processing Fee offset) but do not include Fund or Product details. If a constituent doesn't already exist in Donorfy, the transaction will appear attached to an unknown constituent until one is created.
Enable Integration in Raise
Log into your Raise admin area.
Navigate to Integrations, then Donorfy.
Enable the Donorfy integration- this will start sending data to Donorfy.
Review Test Data
In Donorfy, go to Integrations, then click Raise.
Click History.
Review the logged activity, all entries should have a [TEST] prefix.
Check that:
Constituent matching works as expected.
Transactions show the correct allocations: Donation and Processing Fee offset ( cover cost).
In Raise, go to Integrations, then click Donorfy.
Click Logs and review the activity log.
Step 3: Go Live (Disable Existing Integration First)
⚠️Important: If you currently use a third-party integration for Raise and Donorfy synchronisation, you must disable it before turning off Test Mode to prevent data synchronisation gaps.
To disable existing integration, contact your current integration provider to disable their service.
Turn off Test Mode
In Donorfy, go to Integrations, then click Raise.
Click Settings.
Set Test Mode to No.
Ensure Integration enabled remains Yes.
Scroll down and click Save changes.
The integration will now create actual transactions, constituents, and RPIs in Donorfy.
Review Live Data
In Donorfy, go to Integrations, then click Raise.
Click History, then review the logged activity.
📌Note: All entries are now created in Donorfy and you can click through to open the constituent and see all transaction history. If you expand the transaction you will now see all allocations and the product and fund allocations.
Check that:
Appeals are matching to campaigns correctly.
Products are matching or using defaults appropriately.
Constituent matching is working as expected.
Allocations are being assigned to correct funds.
In Raise, go to Integrations then click Donorfy.
Click Logs, then review the activity log.
Monitoring and Troubleshooting
Regular Monitoring
Check the History log regularly in both Raise and Donorfy for any errors or validation issues.
Verify that campaign and product matching is working as expected for new campaigns.
Review constituent updates.
Best Practices
Keep appeal and product names consistent between Raise and Donorfy for automatic matching.
Review reconciliation allocations.
Getting Help
If you encounter issues, contact Donorfy Support via the chat feature within Donorfy with:
Specific date and time of the issue.
Error messages from the History page.
Details of what you were trying to accomplish.
Your current integration configuration settings.