What Actually Happens to Your Donor Data in an NPSP Migration?
The donor data will not be lost when you transfer from Salesforce NPSP to Nonprofit Cloud, but it won’t appear on the new system as an exact copy either.
That distinction is critical.
Moving from NPSP alters the way Salesforce handles your donors, households, gifts, recurring commitments, soft credits, and financial summaries. It’s not just a case of transferring your records from one database to another since you are in fact experiencing a basic change in the way the data model is organised. The history you have of your donors remains very valuable; the actual work involved is in converting that history so that it fits with the structure of Nonprofit Cloud.
The Core Difference: Translating Data, Not Just Moving Records
It is found, mapped, transformed, loaded and then verified when you are moving your data.
If you’re using an NPSP setup, you’ll most likely be working with a network of Contacts, Household Accounts, Opportunities, Payments, Recurring Donations, Opportunity Contact Roles, and custom rollups. Nonprofit Cloud gets rid of most of those old workarounds and instead makes use of purpose-designed fundraising objects such as Gift Transactions, Gift Commitments, Gift Commitment Schedules, Gift Designations, and Gift Soft Credits.
The real question then is not whether or not a record can be moved, but rather where it should be placed in the new architecture and what happens to the business logic connected with it.
Why NPSP Data Doesn't Map One-to-One
A simple procedure involving an export, followed by an import, and nothing else, almost never works in this instance.
NPSP and Nonprofit Cloud handle fundraising activities in a different manner. For instance, an NPSP Opportunity can refer to a completed donation, a pledge, a recurring payment, or a record relating to a grant pipeline. Before mapping each record to a specific Salesforce object, your migration team needs to understand what each of these things actually means in operational terms. Conducting thorough discovery at the beginning prevents serious issues when the production deployment occurs.
People and Household Structures
In Nonprofit Cloud, Person Accounts replace the conventional Contact together with Household Account method and as a result change the way in which relationships, affiliations, and household groupings are organised.
Before moving a single contact, review:
- Individual donor profiles and household links
- Primary and secondary addresses
- Organizational affiliations and personal ties
- Duplicate records and record IDs
- Existing flows, triggers, and third-party integrations
Treat this step as an operational reset by getting rid of the duplicate contacts, fixing any defective household connections, and sorting the missing data before carrying out the migration.
Donations and Gift History
Raising funds in NPSP focuses on Opportunities, which are backed by Payments. Nonprofit Cloud handles this by maintaining separate records for Gift Transactions (these refer either to the money actually received or to the instalments paid) and Gift Commitments (these cover ongoing pledges or planned giving).
When mapping gift history, ensure you preserve:
- Gift amounts, dates, and payment methods
- Primary donor and campaign attribution
- Fund designations and transaction statuses
- Refund logs and linked commitments
- External transaction/gateway IDs
A successful migration does not consist merely in matching the total number of records since it also has to preserve the original financial context.
Recurring Donations
With NPSP recurring gifts, each installment is used to create individual Opportunities in accordance with the installment schedule. Nonprofit Cloud keeps the amount that a donor had promised to give separate from the amount they actually paid by using Gift Commitments and Gift Transactions.
Before carrying out the migration, check the active and historical schedules, the frequencies of the payments, the payment methods, the failed transactions, and the automated receipts. The existence of a recurring record in the new environment does not mean that your automated processing is working correctly.
Soft Credits & Attribution
NPSP makes use of opportunity contact roles in the case of soft credits, and Nonprofit Cloud has dedicated gift soft credit objects.
If your organisation makes use of soft credits to record donations from peer-to-peer fundraisers, board members, corporate matchers, or individuals within households, then you should carefully work out these relationships. It is important to remain clear about who earned the credit, why they received it, and the exact dollar amount or percentage split; otherwise, although your total fundraising figures might still add up correctly, your donor stewardship data will be damaged.
Fund Designations & Allocations
The act of transferring the entire amount of $10,000 is only half the job when a donor divides the sum of $10,000 among three different projects—for example, $5,000 for scholarships, $3,000 for local programming and $2,000 for general operations.
Nonprofit Cloud features Gift Designations for keeping track of how funds are designated (rather than using NPSP tools like GAU Allocations). If the designation details are lost during the migration, your finance and development teams will not be able to reconcile the restricted funds.
Lifetime Giving & Summary Rollups
Fields such as Lifetime Giving, Total Gifts, or Last Gift Date are shown as standard text fields on a donor profile, but in reality they are controlled by underlying rollup logic.
When setting up the new system, don’t copy the calculated rollup values directly into your text fields. Rather, migrate the raw transaction history first, set up the calculation logic in Nonprofit Cloud, and then verify that the system computes the metrics accurately according to the source data.
Reports, Flows, and External Systems
It makes no difference whether your data is moved intact if your daily operations cease on the first day.
All reports, scheduled flows, Apex triggers, payment gateways, accounting tools, and email marketing platforms place heavy reliance on the standard NPSP objects. If an automated process is expecting a new Opportunity every time a gift is received, inserting the gift into a Gift Transaction will disrupt the sequence. Integrations and automations should be examined and re-designed as an integral part of the main project and not be dealt with later.
How to Properly Validate Your Data
It is not sufficient simply to check that the record counts agree between the old and the new systems; a solid validation plan should include six layers:
- Make sure that the donors, the commitments, the transactions, the soft credits, and the designations all appear in the target system.
- Make sure that the relationships concerning households, organizational affiliations, and campaign linkages are still valid.
- Perform a financial reconciliation by comparing the totals broken down by fiscal year, campaign, gift type, and fund designation with those in your earlier environment.
- Go through the operational and fundraising reports in both systems by comparing each line of the output.
- When carrying out tests of business processes, have your fundraising staff carry out real day-to-day scenarios—for instance, checking a donor’s history, updating a recurring gift, or recording a soft credit.
- In order to verify the integration, test data must be swapped between Salesforce and your payment processors, marketing tools, or accounting platforms.
Should you move all of your historical data?
That is not true in all situations. Every legacy record has to pass three basic tests:
- Really, is this data needed for compliance, for operations, or for stewardship?
- Must the data undergo a structural transformation if it is to become useful?
- Where should it fit into our future-state architecture?
Some records must be migrated without any changes, while others will have to be cleaned up, and it is usually best to keep obsolete or outdated records in a data lake or in cold storage. The objective is not to recreate your current NPSP database in Nonprofit Cloud, but instead to migrate the relevant historical data and at the same time set up a lean and efficient system for the future.
Final Takeaway
If you’re running NPSP today, there is no need to treat migration as an emergency.
Salesforce says NPSP remains supported, while direct feature and enhancement development has moved on.
That gives Salesforce admins time to plan properly.
Use that time to understand your current architecture, identify dependencies, clean up your data, and determine what your organization actually needs from its next Salesforce environment.
The most important question isn’t “Should we migrate from NPSP?” It’s: “What would migration mean for our data, users, integrations, reports, and future roadmap?”
Once you can answer that, the migration decision becomes much easier to scope.
If you want to evaluate your current environment, talk to Aplusify about a Salesforce nonprofit migration assessment.
Struggling to figure out how to migrate your NPSP?
The process of moving from NPSP to Nonprofit Cloud is not simply a matter of transferring files since it involves a structural change and success can only be achieved through careful discovery, careful mapping, intelligent redesign of processes and extensive validation.
If you are going ahead with a move to Salesforce Nonprofit Cloud, Aplusify will be able to give you help. For example, if you need us to audit your NPSP setup and draw up a detailed plan for your fundraising data or if you want us to re-design the flows, reports, and integrations, our certified Salesforce experts will ensure that the transition goes smoothly.
Frequently Asked Questions
By no means, since NPSP and Nonprofit Cloud make use of different data structures and therefore the data has to either be manually checked or be processed using special ETL tools when it comes to auditing, mapping, transforming, and validating it.
Recurring gifts are part of the fundraising model of Nonprofit Cloud, the total commitment (Gift Commitment) being separated from the schedule and the individual payments (Gift Transactions).
The soft credits are moved from the NPSP Opportunity Contact Roles to Nonprofit Cloud’s native Gift Soft Credit objects in order to keep the donor recognition and attribution logic unchanged.
Yes, provided that you transfer the original transaction history and configure Nonprofit Cloud’s calculation logic appropriately so that it recalculates the totals from the source records.
Not automatically. Historical data should be evaluated based on fundraising, reporting, stewardship, compliance, and operational requirements before deciding what to migrate or archive.
Author Bio
- Vikash Kadyan
- Assistant Marketing Manager
Vikash is assistant marketing manager at Aplusify, dedicated to helping nonprofits modernise their tech stack and unlock next-generation fundraising capabilities.