Gift history, soft credits and recurring schedules have to reconcile with finance to the dollar before a donor database can safely be switched off.
Nonprofit migrations usually retire a legacy donor database, event and volunteer spreadsheets, grant tracking files and sometimes a separate program or case management tool. We bring constituents, households and organizations into Salesforce, then gifts, pledges, recurring donations, soft credits and tributes, followed by grants, volunteers and program participation. Gift history is reconciled against finance, fund by fund and period by period, before cutover. Acknowledgment and receipting history comes across so donors are not thanked twice or asked for gifts they already made, and communication preferences are carried over with care.
Nonprofit data carries more relational nuance than most CRM data. Households, spouses who give jointly, donor-advised funds, matching gifts and tribute gifts all create credit that must be split correctly between hard and soft credit. Recurring and pledged gifts have payment schedules that cannot be interrupted. Finance reconciles fundraising totals to the general ledger, so migrated gift data has to match audited figures. Program data may include sensitive information about clients served, which needs stricter access than donor records. And donors remember how they have been treated, so a migration that loses a preference or resets a long giving history is noticed quickly.
Every gift, pledge, payment and write-off is mapped with fund, campaign, appeal and date, then reconciled to finance totals by fund and fiscal period. Donors keep their full giving history, and development staff can report on lapsed, upgraded and retained donors without rebuilding past years by hand. Restricted and unrestricted designations are preserved exactly, since finance and auditors depend on them.
Monthly and other recurring donations are migrated with schedule, amount and payment processor references so charges continue on time after cutover. We coordinate the switch with the payment processor, test a sample of donors end to end, and monitor the first scheduled run closely. Failed and paused schedules are migrated with their status so staff can follow up with those donors.
Joint donors, family foundations, donor-advised funds and matching gift employers are linked so hard and soft credit fall where the organization's gift policy says. Household naming and salutations are rebuilt from the source so letters and acknowledgments address people the way they expect, including widowed donors and couples who use different surnames. Matching gift claims that are still pending with employers are migrated as open items so the follow-up does not lapse.
Foundation and government grants move with deadlines, deliverables and reporting requirements, while program participants and services delivered come across under restricted access. That lets development, program and finance teams share one platform while protecting information about the people the organization serves, and grant reports can draw on program outcomes directly. Declined grant applications are kept as well, since the funder relationship and the reasons still inform the next proposal cycle.
We run nonprofit migrations with development operations, finance and program leads at the table. The gift policy is documented first, including credit rules, since mapping depends on it. Constituents load before gifts, and gifts before soft credits and tributes. Finance signs off on reconciled totals for each test load, and gift officers review their portfolio donors in a sandbox. Cutover avoids year-end giving season and major campaign deadlines. Recurring gift processing is paused and resumed on a documented schedule, and the legacy database stays available read-only for audit and historical lookups.
Recurring gift tokens and schedules are remapped to Salesforce records so donors are charged correctly, and payment card data itself never passes through migration files.
Gift batches, funds and general ledger codes are reconciled against migrated history, and the ongoing export to finance is rebuilt so both systems report the same totals.
Donation forms, peer-to-peer pages and event registrations are reconnected to the new records, with historical transactions matched to constituents rather than loaded as fresh donors.
Fundraising reports built on migrated data will be compared to the audited financial statements. Reconcile totals by fund and fiscal period before cutover, document known differences, and resolve them with finance so board reports do not start with an unexplained gap.
Anonymous gifts, do-not-solicit flags and name exclusions from published donor lists must survive the move. Map each one explicitly, test acknowledgment and publication outputs, and remember that one mistaken public listing can damage a relationship that took a long time to build.
Information about the people a program serves can be highly sensitive, and some may be covered by HIPAA or other rules. Keep it separate from fundraising visibility, grant access by role, and involve program leadership in approving what is migrated.
Neither, if the cutover is planned properly. We identify the last charge date processed in the old system, pause scheduling for a defined window, migrate schedules and payment references, and let the first Salesforce run pick up exactly where the old one stopped. Finance reviews that first batch before it settles, and any exceptions are handled donor by donor.
Cleanup during migration is usually cheaper than cleanup afterward. We standardize addresses, merge duplicate constituents, fix household structures and retire unused codes, but always with gift history preserved. Changes that affect credit or reporting are reviewed with development leadership, and a log shows what was merged or recoded so questions can be answered later by anyone on the team.
They are worth migrating because they reveal engaged supporters who may not yet be donors. Volunteer shifts, hours and roles come across as engagement records, and event attendance is linked to campaigns. We keep the level of detail your team will actually report on and summarize older activity where individual records add little value for planning or recognition.
Not necessarily. Some organizations keep program data separate for privacy or funder reasons and share only outcome summaries with Salesforce. Others consolidate to see donors, volunteers and participants together. We look at sensitivity, reporting obligations and staff capacity, and phase program data later if the fundraising migration should go first. Either way, participant data is never exposed to fundraising users by default.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.