TLDR
Most Salesforce-to-GrantPipe migrations finish in under 60 days without consultants. The integration provides a phased migration path — map NPSP contacts to GrantPipe donors, opportunities to gifts and pledges, and soft credits to GrantPipe's soft-credit model — with a parallel-run period so neither system is abandoned cold.
Salesforce NPSP is the most widely deployed nonprofit CRM in the world — and the most commonly outgrown. Mid-sized nonprofits that implemented it five or ten years ago often find themselves maintaining a system that requires a consultant to change a picklist value, where grant compliance lives in a spreadsheet because NPSP was never designed for it, and where the annual Salesforce bill has become the largest line item in the operations budget.
GrantPipe’s Salesforce integration provides a structured migration path. The wizard maps the core NPSP objects — contacts, opportunities, soft credits — to GrantPipe equivalents, runs a pilot migration for validation, and supports a parallel-run period so the cutover is not a leap of faith.
What the integration does
GrantPipe authenticates to Salesforce via OAuth 2.0 using a Connected App. The migration wizard scans your org for NPSP objects and custom fields, displays record counts, and guides you through field mapping decisions. Standard NPSP mappings (Contact → Donor, Opportunity/Donation → Donation, Opportunity/Grant → Grant, Soft Credit → Soft Credit) are pre-configured. Custom fields require one-time mapping setup.
A pilot migration to a GrantPipe sandbox environment lets you validate the mapping quality before running the full migration. The full migration can be staged — donors first, grants second, historical data third — or run in a single pass. A parallel period where both systems are active allows you to compare report outputs and confirm data integrity before committing to cutover.
Roadmap status
The Salesforce migration integration is available in GrantPipe as a core migration pathway. Given Salesforce NPSP’s installed base, this is the highest-priority migration integration. The migration wizard covers standard NPSP configurations. Heavily customized orgs or Agentforce-integrated configurations may require additional scoping before migration begins.
Data flows
Migration mode:
- Salesforce NPSP → GrantPipe (one-directional, batch migration)
- Parallel period: both systems active, manual comparison
Post-migration:
- Salesforce is decommissioned; GrantPipe is the system of record
Setup steps
- Create a Salesforce Connected App with the required OAuth scopes
- Connect Salesforce in GrantPipe Settings → Integrations → Salesforce
- Run the object discovery scan and review the migration report
- Configure field mappings in the migration wizard
- Run a pilot migration to a GrantPipe sandbox
- Review and resolve mapping issues from the pilot
- Run the full migration, conduct the parallel period, and cut over
Common use cases
A nonprofit that implemented NPSP with a consulting firm in 2016 is spending $40,000 per year on Salesforce licenses plus another $15,000 annually on a managed services contract to keep it running. The migration to GrantPipe takes six weeks using the migration wizard, with a two-week parallel period for validation. No consultant is engaged.
An organization switching from Salesforce to GrantPipe has 12 years of donation history and 22,000 donor records. The pilot migration shows a 97% auto-match rate on deduplication. The remaining 3% — about 660 records — are reviewed manually before the full migration runs.
Limitations and gotchas
Custom Salesforce objects that have no GrantPipe equivalent require manual decisions: either map data to GrantPipe custom fields, archive as CSV, or accept the data will not migrate. The migration wizard surfaces all custom objects and their record counts before migration begins.
Salesforce custom reports, dashboards, and email templates do not migrate. GrantPipe’s reporting layer must be rebuilt separately. Most mid-sized nonprofits find this less time-consuming than expected because GrantPipe’s standard reports cover most common use cases.
Very old NPSP data (pre-2015) may use deprecated field schemas. The migration wizard tests compatibility against current NPSP field references and flags any deprecated fields before migration begins.
Pricing implications
Leaving Salesforce typically saves $150–$300 per user per month in licensing beyond the free 10-seat Power of Us tier. Organizations with 15–25 Salesforce users commonly recover $30,000–$60,000 annually in licensing and managed services costs after migration. GrantPipe’s pricing is flat per organization, not per user.
Start a free trial
Free resource
Get the Nonprofit Grant Compliance Checklist
A practical checklist for post-award grant compliance: restricted funds, reporting cadence, audit prep, and common failure points. Delivered by email.
Source: Salesforce Power of Us Program
Q&A
What if we have heavily customized Salesforce workflows and process builders?
Salesforce workflow automations do not migrate to GrantPipe. During the migration wizard, you document which Salesforce automations are in place and map each to a GrantPipe equivalent or determine it is no longer needed. Most mid-sized nonprofits find GrantPipe's native workflows replace 80–90% of what they built in Salesforce Flow.
Q&A
Do we have to migrate everything at once?
No. You can migrate donors and giving history first, then grant records in a second pass, then historical data. The migration wizard supports staged migration with configurable record type filtering.
Q&A
What happens to data that does not map to a GrantPipe field?
Unmapped data can be exported as a CSV archive from Salesforce and stored separately for record-keeping. GrantPipe's custom fields accommodate most common nonprofit data shapes. Data that genuinely does not fit GrantPipe's model is documented in the migration report.
Frequently asked