Industries/ Non-profits/ Connected donor systems
Record each gift once, and it reaches every system that needs it
Gifts, Gift Aid declarations, consent and unsubscribes move between your donation platform, CRM, email tool and accounts on their own. Nobody copies a donor's details across by hand, and when a sync fails, a named person is told rather than the gift quietly going missing.

- Used by
- Fundraising, database and finance staff
- Takes the place of
- Weekly exports, retyping and matching names in spreadsheets
- Connects to
- Donation platforms, charity CRM, email tool and accounts package
- Built with
- Our connecting systems service
Where it hurts today
A normal week, before it exists
Every Monday someone downloads last week's gifts from the donation platform, opens the CRM in another window and imports or types them in. Donors who used a slightly different email become new records. Event sponsorship arrives through a different platform with a different export. By the time it is all in, the thank-you letters are a week late, and the major donor who gave on Thursday has already had a generic email.
Consent and declarations drift apart. A supporter unsubscribes in the email tool, but the CRM still shows them opted in, so the next appeal export puts them back on the list. A Gift Aid declaration made on the donation page never reaches the CRM, so the gift is left out of the claim. Nobody can say for certain which system holds the true answer for any one supporter.
Finance sees a different picture again. The platform pays out net of its fees in a single bank line, and the finance officer has to split that line into gifts, appeals and restricted funds in the accounts package, using a report that never quite matches the CRM. At year end, fundraising income and the accounts disagree, and two people spend days finding out why.
What it does
Connected donor systems, feature by feature
What the connections do, each one agreed with the people who own the data.
- 01
Donations sync to your CRM automatically
Each online gift arrives in your CRM with the donor, amount, date, appeal code and channel, matched to the existing supporter record where there is one. Thank-you letters and receipts can start the same day rather than after the Monday import.
- 02
Duplicate donor records caught early
When a gift arrives from an email or address the CRM does not recognise, it is matched to an existing supporter under rules you agree, such as the same email and postcode. Borderline cases go to a short review list for your database officer, because a wrong merge is harder to undo than a missed one.
- 03
Gift Aid declarations travel with the gift
The declaration, its date and the wording the donor saw arrive with the gift. Where a platform can also claim Gift Aid itself, we agree with your finance lead which system makes the claim, so each gift is claimed by one system, not two and not none.
- 04
Unsubscribes and suppressions reach everywhere
An unsubscribe in the email tool, a no-more-post request taken on the phone, or a suppression collected from the UK's Fundraising Preference Service is written to the CRM and pushed to the other systems. The next appeal list is drawn from the same answer everywhere.
- 05
Platform payouts split for finance
Payouts are broken back into individual gifts, platform fees and appeals, coded to the right income and restricted fund codes, and posted to your accounts package as entries that match the bank line. The finance officer checks the posting rather than rebuilding it.
- 06
A record of every sync
Each run is logged: what came in, what changed, what was held back and why. When something fails, a named person is told and the item waits in a queue for review, so a missed gift does not disappear quietly.
A day with it
How the day runs instead
A normal week for a fundraising team once the systems keep each other up to date.
- Monday, 8amDatabase officer
Opens the review list instead of an export. Over the weekend the gifts from both donation platforms reached the CRM, and five need a decision: two possible duplicates, one gift with no appeal code and two declarations missing a postcode.
- Monday, 11amFundraising manager
Sees Saturday's sponsored walk income in the CRM against the event, participant by participant, without waiting for the platform's report. Thank-you emails to the walkers started on Sunday from the CRM's own templates.
- WednesdaySupporter care officer
Takes a call from a donor who wants no more phone calls but still wants the magazine. The change is made once in the CRM, and by the afternoon the telephone appeal list leaves them out while the magazine mailing keeps them in.
- ThursdayEmail lead
Builds the appeal email list. Last month's unsubscribes are already in the CRM, so the list drawn from it matches what the email tool will accept, and nobody is put back on a list they asked to leave.
- Month endFinance officer
Finds the platform payout already posted to the accounts package, split into gifts, fees and restricted funds, with a link to the gifts behind it. They compare it with the bank line and approve it.
What it connects to
Works with what you already run
The usual four, plus any others you run. We start with what you already pay for.
Donation and event platforms
Online gifts, regular gifts, event registrations and sponsorship come in with declarations and consent attached, for example from JustGiving where your charity has access to its data API, or from any platform with a dependable export.
Charity CRM
The CRM stays the record of each supporter, their giving and their consent. Every connection reads from it or writes to it through its API, rather than creating another list that someone has to remember to update.
Email marketing tool
Lists are built from the CRM, and unsubscribes, bounces and preference changes come back to it, so the two always agree on who can be emailed and about what.
Accounts package
Payouts, fees and fund codes are posted as entries that match the bank, for example to Xero or QuickBooks where your plan includes API access, so fundraising and finance report the same income.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- Online gifts from your main donation platform reaching the CRM automatically
- Matching to existing supporter records, with a review list for borderline cases
- Gift Aid declarations and consent carried across with each gift
- Unsubscribes from your email tool written back to the CRM
- A log of every sync, with an alert to a named person on failure
Once it is in use
- Platform payouts split and posted to your accounts with fund codes
- Event and sponsorship platforms connected alongside the main one
- Phone and post suppression requests pushed to every connected system
- A quarterly report comparing income totals across the CRM and accounts
Buyer's guide
Before you commission one
Four decisions worth making before you commission connected donor systems.
- 01
Ready-made connector or custom integration
Check the connectors your CRM and platforms already offer. Many charity CRMs list ready-made integrations with popular donation platforms, and if one moves the fields you need, including declarations, appeal codes and consent, use it. Custom integration earns its place where ready-made connectors miss those fields, cannot handle duplicates or do not cover a platform you rely on.
- 02
What to gather first
List every system that holds supporter data, who has the admin login and whether your plan includes API access. Collect your appeal codes, fund codes and consent wording, and pull a sample of last month's gifts from each platform. If your accounts follow the Charities SORP, its 2026 edition applies to periods beginning on or after 1 January 2026, a sensible moment to agree income and fund codes.
- 03
Who owns it
A database officer or fundraising operations lead should own the review list and the matching rules. Finance owns income and fund codes. Your data protection lead owns what moves where. If nobody in the charity can name who owns a sync, problems sit unnoticed until a donor or an auditor finds them.
- 04
How you will know it is working
Watch whether gifts appear in the CRM without anyone importing them, whether the review list stays short, whether unsubscribes match across the CRM and email tool when you spot-check, and whether fundraising and finance agree on income at month end without a reconciliation meeting. Thank-you letters going out sooner after each gift is another good sign.
Terms worth knowing
The words you will meet
- API
- An application programming interface: the door a system provides so other software can read and write its data safely. Whether your CRM, platform or accounts package offers one, and whether your plan includes it, decides how much can be connected and how cheaply.
- Deduplication
- Finding records that describe the same person, such as one supporter entered three different ways, and merging them under agreed rules. Good deduplication sends doubtful matches to a person, because merging two different donors loses history that is very hard to rebuild.
- Suppression list
- The people you must not contact by a given channel, such as those who unsubscribed, asked for no post or used the UK's Fundraising Preference Service. A suppression only works if every system that sends messages reads from the same list.
Handled with care
The details that matter here
Connecting systems moves personal data between them. These are the details we take most care over.
Which system owns each answer
Before anything is connected, we agree with you which system is the record for each thing: supporter details, consent, declarations, gifts and income codes. That decision is written down, so a clash between two systems has a known answer rather than whichever ran last.
Where consent came from
In the UK, the charitable purpose soft opt-in has let charities email and text supporters without consent since 5 February 2026, but only for details the charity collected directly. Details gathered by a third-party fundraising platform do not qualify, so we record the source of every contact detail and keep the two kinds apart.
Declarations handled exactly
HMRC expects each Gift Aid declaration, and any cancellation with its date, to be kept for six years after the period it relates to, and longer for enduring declarations still in use. We test every mapping with your finance and fundraising leads on real examples before switching it on, and nothing is changed silently afterwards.
Cleaning up before connecting
Most charity databases carry years of duplicates and old consent records. We review the data with your database officer first, agree what to merge, what to leave and what to flag, and run the first sync on a copy so the result can be checked before it touches live records.
Guides
Worth reading first
Questions
What buyers ask first
Should we replace our charity CRM instead of integrating it?
Usually not. If your CRM holds your supporters reasonably well, connecting it to the platforms around it is cheaper and less disruptive than moving everything. Where the CRM really is the problem, we would recommend choosing and configuring an established charity CRM rather than building one, and we can help with that choice. We would not build a donor database from scratch.
Can online donations sync to our CRM automatically?
Usually, yes. Many donation platforms offer an API, a ready-made connector to popular CRMs or a dependable scheduled export, and some, such as JustGiving, provide a data API for charities and CRM providers. What matters is what comes across: Gift Aid status, consent, appeal codes and fees. We check those on real gifts before relying on any route.
How do you stop Gift Aid being claimed twice?
By deciding up front which system makes the claim. Some donation platforms can claim Gift Aid for you, and your CRM may claim it too. We agree with your finance lead which one claims each kind of gift, mark gifts already claimed when they arrive, and carry that status into the claim file, so the person signing the claim can see what is included and why.
What happens when a CRM sync fails?
It is held, not lost. Each failed item waits in a review queue with the reason, such as a missing field or a supporter the CRM could not match, and a named person on your team is alerted. Once it is fixed, the item is sent again without creating a second gift. A short weekly summary also shows anything still waiting, so a quiet problem surfaces even if nobody is looking.
Who can change the integration once it is running?
You decide. Simple settings, such as which appeal code maps to which fund, can be changed by your database officer from a short settings page. Changes to what moves between systems are made by us or another developer, recorded and tested on a copy first. Everything is documented, so another supplier could take it over if you ever needed them to.
Ready to record each gift just once?
Tell us which donation platforms, CRM, email tool and accounts package you use, and where the retyping happens. We reply within 48 hours.
More for non-profits
What else we build for non-profits
Websites staff can update
A fast, accessible site with donation pages, events, news and campaigns that staff and volunteers can update themselves, built to accessibility guidance and with consent wording and declarations such as Gift Aid in mind where they apply.
Member and supporter portals
Members renew, update their details, book events and download receipts on their own, and supporters manage their own contact preferences, so the office stops retyping changes that arrived by email, letter and phone.
Volunteer apps
Shift sign-up, check-in, incident and safeguarding forms on volunteers' own phones, working offline in a hall with no signal, and simple enough for someone who joined last week to use without any training.
Admin that runs itself
Thank-you letters, renewal reminders, grant deadline chasers and the data preparation behind tax-relief claims, handled by software and checked by a person, so a small team spends its hours on people rather than on paperwork.
Answers for volunteers
Your handbook, safeguarding policy and how-to guides behind a search that answers plain questions and shows exactly which document each answer came from, so volunteers stop waiting for a coordinator to reply.


