Salesforce NPSP to Non Profit Cloud(NPC) Migration : 2026 Guide
⏱ 6 min read
Salesforce has long been a trusted platform for nonprofits, helping organizations manage donor relationships, programs, fundraising, and impact data. For years, the Nonprofit Success Pack (NPSP) served as the foundation for this work.Today, Salesforce is investing heavily in Nonprofit Cloud and its newer nonprofit capabilities, giving organizations a more modern platform for constituent management, fundraising, programs, reporting, and automation.
For nonprofits considering a move from NPSP to Nonprofit Cloud, the challenge is not simply moving records from one Salesforce org to another. The transition can involve data transformation, metadata migration, Person Accounts, fundraising structures, automation, integrations, reporting, and process redesign.
This guide explains the key differences, migration steps, data considerations, testing requirements, and best practices you should understand before making the transition.
Need expert help? Explore Kizzy Consulting’s Salesforce for Nonprofits services for help with Salesforce implementation, migration, automation, integrations, and nonprofit CRM optimization.
Why Upgrade from NPSP to Nonprofit Cloud?
Salesforce is moving toward a more modern nonprofit platform designed around connected data, automation, scalability, fundraising, program management, and improved reporting.
For organizations evaluating an NPSP to Nonprofit Cloud migration, the potential benefits include:
- A modern person-centric data model for constituent management
- More flexible fundraising and gift management
- Improved program and case management capabilities
- Better reporting and analytics foundations
- More modern automation capabilities
- Greater alignment with Salesforce’s long-term nonprofit product direction
However, the transition should not be treated as a simple version upgrade. A successful migration requires organizations to understand how their existing NPSP data, metadata, relationships, automations, and integrations will work in the new environment.
For additional context, see Kizzy Consulting’s guide on Salesforce Nonprofit Cloud vs. NPSP.
What Changes When You Move from NPSP to Nonprofit Cloud?
The move from Salesforce Nonprofit Success Pack to Nonprofit Cloud is more than a traditional CRM upgrade. It can change how nonprofit data, relationships, fundraising transactions, automation, reporting, and integrations are structured and managed.
The biggest migration considerations typically fall into five areas:
- Data transformation: Existing NPSP records may need to be mapped and transformed to fit the Nonprofit Cloud data model.
- System provisioning: The new Nonprofit Cloud environment must be correctly provisioned and configured before migration begins.
- Configuration redesign: Existing NPSP workflows, rollups, naming conventions, relationships, and business processes may need to be redesigned.
- Metadata migration: Custom fields, objects, flows, reports, layouts, permissions, and other Salesforce components need to be reviewed alongside the underlying data.
- Integration compatibility: Third-party applications and data tools may need to be updated to work with Person Accounts and Nonprofit Cloud-specific objects.
Because of these changes, the goal should not be to reproduce every part of your old NPSP environment. The better objective is to use the migration as an opportunity to simplify processes, remove technical debt, improve data quality, and build a stronger Salesforce foundation.
1. Start with the Right Foundation
Before migrating anything, you need to set up and provision your Nonprofit Cloud environment properly.
Work with your Salesforce Account Executive and implementation partner to confirm that the required licenses, features, permissions, and prerequisites are in place before beginning migration activities.
Key setup considerations include:
- Confirming the appropriate Nonprofit Cloud licensing
- Provisioning the target Salesforce environment
- Enabling required features and capabilities
- Configuring Person Accounts and relevant nonprofit functionality
- Reviewing Salesforce prerequisites
- Preparing a sandbox for migration testing
Starting migration work before the target environment is properly configured can create unnecessary rework and make data validation more difficult.
For a broader implementation roadmap, see Kizzy Consulting’s step-by-step Salesforce Nonprofit Cloud implementation guide.
2. Prepare and Clean Your Data
Your NPSP data may not map one-to-one with the Nonprofit Cloud data model.
That makes data preparation and cleansing one of the most important stages of the migration.
Before moving data, ask:
- Which records do we actually need to migrate?
- Which fields map directly?
- Which fields require transformation?
- Which relationships need to be recreated?
- Which duplicate records should be merged?
- Which legacy fields and components can be retired?
- Which historical records need to remain available for reporting?
Cleaning the source environment before migration can reduce duplication, improve reporting quality, and prevent unnecessary technical debt from entering the new environment.
For organizations struggling with fragmented donor information, see How Salesforce Nonprofit Cloud Solves Scattered Donor Data.
3. Understand the NPSP vs. Nonprofit Cloud Data Model
One of the biggest changes between NPSP and Nonprofit Cloud is the underlying data model.
Contacts and Person Accounts
In an NPSP environment, individuals are commonly represented as Contacts associated with Accounts. Nonprofit Cloud uses Person Accounts as a central representation for individuals.
This means your migration strategy needs to account for how existing contact information, relationships, addresses, and associated records will be transformed.
Fundraising and Gift Data
Fundraising is another major area of change.
While Opportunities can still be relevant for certain fundraising scenarios, Nonprofit Cloud introduces a more structured framework for representing gifts and transactions.
- Gift Designations can represent the purpose or allocation of a gift.
- Gift Commitments can represent pledged or committed donations.
- Gift Transactions can represent actual gift transactions and payments.
Existing NPSP fundraising data may therefore require transformation rather than a simple one-to-one migration.
Tribute and Relationship Data
Tribute information and constituent relationships also need careful planning. Data that was previously stored together may be represented through separate records or relationships in the new environment.
Every important relationship should have a defined source, target, transformation rule, and validation method before production migration begins.
4. Choose the Right Migration Tools
Once your source data has been cleaned and mapped, you need the right tools to export, transform, validate, and import records.
Common Salesforce migration tools include:
- Salesforce Data Loader: Useful for exporting, importing, updating, and deleting Salesforce records at scale.
- Salesforce Inspector: Helpful for administrators and technical users who need to inspect, export, and manage Salesforce records.
- Salesforce CLI and VS Code: Useful for retrieving, deploying, and managing metadata and Salesforce components.
- Custom transformation scripts: Useful when source data requires complex transformations before it can be loaded into the target environment.
The right approach depends on your organization’s data volume, complexity, technical resources, transformation requirements, and testing strategy.
5. Migrate Your Components and Metadata
Your Salesforce org is not made up of records alone. It also contains custom objects, fields, automation, reports, layouts, permissions, Apex, Lightning Web Components, and other metadata.
Use Salesforce development tools such as VS Code and the Salesforce Extension Pack to retrieve and deploy relevant components.
Depending on your implementation, this may include:
- Flows and automation
- Email templates
- Lightning Web Components
- Apex code
- Reports and dashboards
- Custom objects and fields
- Validation rules
- Permission sets
- Lightning Pages
This stage is also an opportunity to review and optimize existing configuration instead of migrating every legacy customization unchanged.
6. Create a Migration Mapping Plan
Before importing production data, document how important NPSP objects, fields, relationships, and processes will map to Nonprofit Cloud.
A practical migration mapping should define:
- Source: The NPSP object and field
- Target: The Nonprofit Cloud object and field
- Transformation: Logic required to change the source value
- Dependencies: Records that must exist first
- Validation: How the migrated result will be checked
- Exception handling: What happens when a record cannot be migrated automatically
This makes complex transformations easier to manage and gives your team a repeatable process for sandbox testing and production deployment.
7. Reconfigure NPSP Automations Instead of Simply Rebuilding Them
Nonprofit Cloud introduces different approaches to several functions that organizations may be accustomed to handling through NPSP.
Naming Conventions
Organizations that rely on NPSP automated naming behavior may need alternative approaches in Nonprofit Cloud, such as predefined values in Quick Actions or record-triggered flows.
Rollups and Data Processing
Rollup requirements should also be reviewed. Nonprofit Cloud can use the Data Processing Engine to calculate, summarize, and process data, providing a different approach to some requirements previously handled with NPSP rollup functionality.
Reciprocal Relationships
Relationships between constituents may require additional configuration. Where relationships were previously handled through NPSP functionality, NPC implementations may require flows or other automation to maintain the desired behavior.
The migration is therefore an opportunity to redesign automation around the new platform rather than carrying unnecessary technical complexity forward.
8. Modernize Fundraising and Program Tracking
Fundraising and program management should be reviewed carefully during migration.
While Opportunities may continue to have a role in major-gift scenarios, Nonprofit Cloud introduces a more structured approach to gift management through objects such as:
- Gift Designations – represent specific fund purposes.
- Gift Commitments – represent donation pledges or commitments.
- Gift Transactions – represent actual gift transactions.
Program Management and Case Management also require careful review because the relationships and processes can differ from an existing NPSP implementation.
For a broader overview of nonprofit Salesforce capabilities, visit Salesforce for Nonprofits by Kizzy Consulting.
9. Check Integration Compatibility Before Go-Live
Third-party integrations are one of the most frequently overlooked parts of an NPSP to Nonprofit Cloud migration.
An integration that works correctly with NPSP may depend on objects, fields, relationships, or APIs that differ in Nonprofit Cloud.
Before go-live, create an integration inventory covering:
- The application or integration name
- Objects and fields it reads or writes
- API version and authentication method
- Inbound and outbound data flows
- Nonprofit Cloud compatibility status
- Required configuration or vendor updates
- Sandbox testing results
Pay particular attention to integrations involving fundraising, gift transactions, Person Accounts, donor information, payment systems, reporting, and external databases.
For help with Salesforce-to-system integrations, see Kizzy Consulting’s Salesforce Integration Services.
10. Understand Data Migration vs. Metadata Migration
Moving Salesforce records is only one part of the project. A complete NPSP to Nonprofit Cloud migration also requires careful consideration of metadata.
Data Migration
Moves records such as constituents, gifts, transactions, programs, relationships, and historical information into the target environment.
Metadata Migration
Moves or rebuilds the Salesforce configuration that makes the system operational, including fields, objects, flows, reports, permissions, layouts, and automation.
Both need to be considered together. A record can migrate successfully while still being unusable if the configuration, relationships, automation, or permissions supporting that record have not been recreated correctly.
11. Modernize Your Layouts and Automation
Upgrading your Salesforce environment is the perfect opportunity to modernize how users interact with the system.
- Convert outdated Workflow Rules and Processes into Salesforce Flow where appropriate.
- Review old automation that no longer serves a business purpose.
- Replace outdated page layouts with modern Lightning Pages where appropriate.
- Reduce duplicate automation and unnecessary customizations.
- Improve user navigation and data-entry experiences.
The goal should be a cleaner Salesforce architecture rather than simply rebuilding the technical debt accumulated in the NPSP environment.
12. Always Test in a Sandbox First
It may be tempting to migrate data and components directly into your production environment, but that is a risky approach.
Instead, use a sandbox environment to test your migration before production deployment.
Sandbox testing should validate:
- Data accuracy
- Person Account conversion
- Gift and fundraising data
- Relationships
- Flows and automation
- Reports and dashboards
- Permissions
- Third-party integrations
- User workflows
- Data quality and duplicate handling
Your nonprofit users should also participate in user acceptance testing. Technical validation alone is not enough; the people who actually use Salesforce every day need to confirm that the new environment supports their workflows.
13. Measure the Migration by Business Outcomes
A successful migration is not simply one where the last record loads successfully. The real measure is whether your nonprofit operates better after the transition.
After migration, evaluate whether your organization has achieved:
- Cleaner constituent and fundraising data
- More reliable reporting
- Fewer manual processes
- Better visibility across fundraising and programs
- Improved user experience
- More maintainable automation
- Better integration reliability
- A scalable Salesforce foundation for future growth
This is what turns an NPSP migration into a modernization project rather than simply a platform replacement.
A Practical NPSP to Nonprofit Cloud Migration Checklist
Related Salesforce Nonprofit Resources
- Salesforce Nonprofit Cloud vs. NPSP – Compare the two Salesforce nonprofit platforms and understand the major differences.
- Step-by-Step Salesforce Nonprofit Cloud Implementation Guide – Explore a practical roadmap for implementing Nonprofit Cloud.
- How Salesforce Nonprofit Cloud Solves Scattered Donor Data – Learn how a connected Salesforce foundation can improve donor data management.
- Salesforce for Nonprofits – Explore Salesforce solutions for donor management, fundraising, programs, volunteers, and impact reporting.
- How Nonprofits Can Leverage Salesforce in 2026 – Explore current Salesforce strategies for nonprofit efficiency, data, and fundraising.
- How Agentforce Helped a Nonprofit Reduce Manual Work – See how Salesforce AI automation can improve nonprofit operations.
- Agentforce for Case Management in NGOs – See how AI-powered workflows can simplify nonprofit case and enrollment processes.
- Salesforce Integration Services – Explore Salesforce integration strategies for connected systems and data flows.
Conclusion: Making Your NPSP to Nonprofit Cloud Migration a Success
Upgrading from NPSP to Salesforce Nonprofit Cloud is a significant step, but with the right planning, the transition can become an opportunity to modernize your entire nonprofit CRM environment.
The most important thing to remember is that this is not simply a data migration project. Your team needs to consider the new data model, Person Accounts, fundraising structures, metadata, automation, integrations, reporting, permissions, and user workflows.
A successful migration starts with discovery and data preparation, continues through structured mapping and sandbox testing, and ends with a Salesforce environment that is easier to use, maintain, report on, and scale.
If you want a cleaner migration, investing in planning, data quality, migration mapping, integration testing, and user acceptance testing will significantly improve your chances of a successful go-live.
Looking for a partner to help with NPSP to Nonprofit Cloud migration?
Kizzy Consulting can help nonprofits assess their existing Salesforce environment, plan data and metadata migration, configure Nonprofit Cloud, review integrations, test the migration in a sandbox, and prepare for production go-live.
Frequently Asked Questions About NPSP to Nonprofit Cloud Migration
What is an NPSP to Nonprofit Cloud migration?
An NPSP to Nonprofit Cloud migration is the process of moving a nonprofit’s Salesforce data, metadata, relationships, configurations, and business processes from Nonprofit Success Pack to Nonprofit Cloud. The project involves more than transferring records because the underlying data model and platform capabilities are different.
What is the biggest difference between NPSP and Nonprofit Cloud?
One of the biggest differences is the underlying data model. NPSP commonly uses Contacts and household-based structures, while Nonprofit Cloud uses Person Accounts and newer objects and relationships for managing constituents, fundraising, and nonprofit operations.
Do all NPSP records migrate directly to Nonprofit Cloud?
No. Some NPSP records require transformation or restructuring before they can be used in Nonprofit Cloud. Contacts, opportunities, gift information, tribute data, relationships, and custom objects should be reviewed individually to determine the correct target structure.
What is the difference between data migration and metadata migration?
Data migration moves Salesforce records such as constituents, gifts, transactions, and program information. Metadata migration moves the configuration that makes Salesforce work, including custom fields, objects, flows, validation rules, layouts, reports, permissions, and other components.
Do NPSP workflows and automations need to be rebuilt?
Not necessarily in the same form. Existing workflows, processes, rollups, naming conventions, and relationship automations should be reviewed during discovery and redesigned where appropriate using Nonprofit Cloud capabilities such as Flow and the Data Processing Engine.
Can third-party integrations work with Nonprofit Cloud?
Many integrations can work with Nonprofit Cloud, but compatibility should be verified before migration. Integrations built around NPSP-specific objects, fields, relationships, or APIs may require configuration changes, vendor updates, or replacement before they are ready for the new environment.
Should I migrate directly from NPSP to production?
No. A sandbox should be used to test data mappings, metadata, automation, integrations, reports, permissions, and user workflows before production deployment. Multiple testing and validation cycles can help identify migration issues before they affect live nonprofit operations.
How long does an NPSP to Nonprofit Cloud migration take?
The timeline depends on the size and complexity of the Salesforce org, the amount and quality of data, customizations, integrations, fundraising requirements, and testing needs. A detailed discovery and migration assessment is the best way to establish a realistic timeline for your organization.
Can Kizzy Consulting help with an NPSP to Nonprofit Cloud migration?
Yes. Kizzy Consulting can help nonprofits assess their existing Salesforce environment, plan data and metadata migration, configure Nonprofit Cloud, review integrations, test the migration in a sandbox, and prepare the environment for production go-live.
Ready to Plan Your NPSP to Nonprofit Cloud Migration?
Get help assessing your current Salesforce org, migration requirements, data model, integrations, and go-live readiness.
