MuchLoved Data Integration
Charity Toolkit has built an integration between MuchLoved and Donorfy. It automatically syncs tribute and donation data, weekly or daily, to keep your CRM system up to date with new donors, tributees and guardians.
Works with 
Subscribe to Charity Toolkit's MuchLoved integration and each month we'll run weekly or daily schedules (you decide) to identify new donations and pull them across to your CRM system. You'll never need to run manual CSV exports and imports again.
Once your subscription is set up the Charity Toolkit team will build out a branch of the integration for you. If needed, a member of the team will get in touch to finalise and branch customisations and once complete the integration runs immediately.
CRM Contacts
The integration identifies existing contacts in your database, or creates new ones if no match is found. This includes donors, tribute guardians and tributees (the deceased), all of whom are connected to give you the complete picture.
Donations
Automatically sync donations from all tributes to your CRM system on a regular schedule. Donations are mapped per frequency (regular or one-off gifts) and are clearly labelled as having come from our integration.
Reporting and Logs
Data entering your CRM system is clearly labelled with MuchLoved identifiers so you can isolate the integration's activity in your reporting, or reference it for the complete fundraising picture.
We also share logs with your CRM system in the event that a donation transmission failed, was incomplete, or otherwise needs your attention.
Customisations
Whilst the integration is ready to go out of the box, it is possible to adapt some aspects of how it works. When Charity Toolkit build your branch, we will ask your preference for things like consent and communication mapping, donation mapping, Gift Aid reference, and legacy contact updates.
Beyond that, we are open to bespoke customisation requests – get in touch and we may be able to help.
The Charity Toolkit MuchLoved integration runs on either a weekly or daily transmission schedule, depending on which monthly subscription you choose.
Subscription includes transmission of all donations, support and troubleshooting and automatic rollout of updates and new features.
Got a question? Want to know more about the integration? Take a look at the topics below to learn more.
Charity Toolkit does not collect fees per transaction it processes, nor does it present tipping or self-interested donation mechanics to your users. The monthly operational subscription is all we charge.
Third party platforms and services associated with this product will likely themselves charge you for their use - always check their terms.
This integration can only connect the necessary systems with authorisation established through their respective API configurations. The credentials (and some customisation settings where applicable) needed to do this need to be shared with us so we can properly associate the integration with your Charity Toolkit account
If you don’t have these details available at the point of registration a member of the Charity Toolkit team will be in touch shortly after your registration to guide you on obtaining them.
The integration product is robust and centralised for all our customers. Unique mappings and configurations are available for customising how the data appears in your CRM system, but how the integration works is largely fixed in place. It is always worth asking for special requests though, as we have been able to entertain some in the past.
Yes, we can sync donation, tribute and guardian data from past transactions. As part of the integration setup we will ask you for a start date to commence the sync from, which can be in the past. Any records already processed into your CRM system will be duplicated though, so make sure the sync date you give us is before your last export/import process.
In a back-dated sync, the first 1000 transactions are free. There is a charge of £10 per every 1000 transactions processed thereafter.
Yes. If for whatever reason a transmission was unsuccessful, let us know and we can run it again.
On occasion, CRM systems experience blips which mean our integration can't reach them, or our integration is interrupted. We have safeguards and retry protocols in place, including a 10-day look-back for unhandled donations, but even so, it is possible that data transmission can't be completed. If this is the case, here are some things to consider:
- If the reason for the failure was poor identity data, the integration will endeavour to assign the donation to a MuchLoved-orientated anonymous record in your CRM, and will append to their timeline an Activity breaking down the data handled and the cause of the fault.
- If the reason for the failure was poor transaction data, the integration will endeavour to append to the timeline of a MuchLoved-orientated anonymous record in your CRM an Activity breaking down the data handled and the cause of the fault.
Conversely, for every successful donation, an Activity breaking down the data handled is also added to the donor's record for your reference.
Charity Toolkit's MuchLoved integration stores none of the data collected from MuchLoved, bar transaction ID numbers. We keep these numbers for operational purposes, debugging and our own deduplication. No identity data from your donors, guardians or tributees is stored.
MuchLoved handles Gift Aid claims for you, so as part of the integration setup we will ask your preference on how you want this reflected in your CRM system. The integration can either sum Gift Aid values with donation values, or it can omit Gift Aid values entirely.
When a donation is received by the integration, it will create a trio of contact records in your CRM system. In Donorfy the integration will:
- Create a Constituent record for the Donor and will place the transaction on their timeline.
- Create a Constituent record for the Guardian and will connect the transaction to them.
- Create a Constituent record for the Tributee (the deceased) and will make them the beneficiary of the transaction, and will connect them to the Guardian record. This constituent will be archived and marked as reason "deceased".
If the data from MuchLoved finds existing record matches in your CRM system, the integration will use these rather than create new records.
If the data from MuchLoved does not find existing record matches in your CRM system, the integration will create new records. The matching process compares First Name, Last Name, Email Address, Postal Address and Phone Number; if there are too many variations between these fields as they appear in the MuchLoved data and the CRM system data no match will be found and a new record will be made.
When the integration creates a Tributee record in your CRM system it will use a uniquely created faux email address (since no genuine email address will be supplied by MuchLoved) for future matching purposes. If a record already in you CRM system has passed on and is now receiving donations in MuchLoved, the integration will create them as a new (duplicate) Tributee record. The cleanest way to deduplicate these records is to merge them, ensuring that the uniquely created faux email address gets transferred to the legacy record.