Donorfy to Beacon CRM migration
A Donorfy migration is about translating the supporter and fundraising picture your charity has built, not simply importing Constituents. We help you understand the records, tags and transaction structure in your Donorfy data, then agree what should move to Beacon.
- Current system
- Donorfy
- Migration focus
- Understand source records, linked data and your team’s requirements
- Before final import
- Agree and check a representative test migration
Understand your Donorfy data
Donorfy uses Constituents for people and organisations, with tags and constituent types describing relationships and attributes. Fundraising data may include appeals, Payments and Allocations, regular giving, Gift Aid details and communication preferences. We check how your team uses these features before designing the mapping.
Map records to how your charity works
Agree how constituent types, tags and preferences will be represented, and how payments and their allocations should appear in Beacon. Review regular-giving arrangements, Gift Aid evidence and appeal history separately so their meaning is not lost in a broad transaction import.
- Distinguish payment records from their allocations and fundraising purpose
- Review tag categories and constituent types with the teams who use them
- Agree how preferences, Gift Aid and regular giving should be retained
Partnerships people recommend.
This Beacon partner review describes the client’s experience with MakeITaplan. The previous CRM named on this page was confirmed separately and is not attributed to the review.
Amazing support
“Gemma guided us through setting up Beacon and it was a very smooth process. She is very nice and easy to work with, she knows the product well and efficiently organised the order in which we did everything. With the more complicated aspects, she quickly grasped what needed to be done and worked with Beacon where needed to see things through. We would recommend working with her without reservation and we are very grateful that she helped us and that we have such an improved database as a result.”
Test, review and agree the move
We can plan sample imports and review the results with the people who understand the source information. Together, we agree which records, links and key totals to check, resolve mapping questions and confirm what is in scope before any final import.
Plan for cutover and confident Beacon users
A migration also needs clear responsibilities, a decision log and an agreed point for the final source export. We can coordinate the work with your team, plan appropriate training and handover, and discuss follow-on support for new starters or changing requirements.
Related questions, answered
Can you migrate our existing data?
Yes.
We can help extract, clean, restructure, map and import data from existing systems and spreadsheets, depending on the agreed project scope.
Migration is not simply about putting old columns into new fields. We will also consider relationships, duplicates, data quality and whether the existing structure makes sense in the new CRM.
Will all of our old data be moved into Beacon?
Not necessarily. It is useful to decide which records and history the charity needs for its work, reporting and obligations. We help document those decisions and map the agreed data; your team approves what should be retained and migrated.
How can we check whether migrated data is accurate?
Agree validation checks before the final import. Review representative records and relationships, compare relevant counts or totals with the source, record issues and repeat the checks after corrections.
Can you help clean data before migration?
Yes. We can help identify duplicates, inconsistent values, missing information and other data-quality issues, then agree which corrections are in scope and who will make them.