Salesforce Nonprofit Cloud

Yes. Salesforce currently uses Agentforce Nonprofit for the offering previously called Nonprofit Cloud. The product naming does not mean every implementation needs an AI assistant. We confirm the products and licenses required for your use cases.

NPSP is a managed package with a different data model. Nonprofit Cloud uses Person Accounts for individual constituents and a dedicated fundraising model. We assess existing records, automations, reports and integrations before planning a move. Staying on NPSP may be appropriate when it already meets your needs.

Basic Setup has no external integrations. Connected Fundraising includes exactly two: one payment system and a second system selected during discovery. Full Customization is scoped around the required systems and processes. We confirm records, direction, frequency, supported events and acceptance checks before delivery.

Connected Fundraising includes one payment-system integration within its two-integration allowance. Multiple payment providers require a revised scope. Stripe, PayPal and direct-debit providers are examples to assess, not a claim of built-in connectors. We validate regional availability, APIs and recurring-payment, refund and settlement events. Unsupported features need an alternative workflow or separately agreed development.

Nonprofit Cloud records fundraising activity; the selected processor handles payment collection. We design the connection and reconciliation workflow around your finance system of record. Processor fees, payouts and ledger entries must be mapped and checked rather than assumed to match automatically.

Migration scope is agreed after reviewing source records, relationships, history and data quality. No fixed record volume, source count or history depth is implied by the package name. NPSP migration needs assessment of its different data model and existing customizations. We agree volumes, cleanup responsibility, history depth, field mapping and reconciliation before importing. Raw card data is not migrated into CRM; any token transfer depends on the processors.

We provide a scoped estimate after reviewing your data, payment providers, workflows, licensing and team readiness. Package names describe delivery scope rather than fixed prices or guaranteed dates. The proposal separates implementation, licenses, third-party costs and ongoing support.

Your users test the agreed workflows, migration checks reconcile the selected records and gift totals, and integrations pass supported event and recovery checks. Launch follows customer acceptance, documented ownership and an agreed cutover plan.

Nonprofit Cloud manages giving relationships and fundraising records. Marketing Cloud can use selected data to support personalized stewardship and broader fundraising journeys. We define the audience, consent rules, content and response tracking for each use case, and select the appropriate Marketing Cloud product and edition.

Salesforce documents Participant Management actions for staff to record benefits, update goals, create referrals, prepare notes, create tasks and summarize participant records. The Donor Support Agent handles requests to pause, resume, close or change the amount of existing recurring gift commitments through an Experience Cloud site. These are configured agents with their own access and setup requirements. An applicant-facing enrollment assistant is a separate use case to assess; it is not the documented purpose of the staff Participant Management Agent.

No. We assess Data 360 when your use case needs data harmonization, identity resolution or supported activation across multiple sources. A straightforward CRM setup or payment integration may be served by existing Salesforce capabilities and direct application integration. Product and consumption costs are evaluated against the agreed requirements.