Nonprofit Success Pack tracked every gift on the Opportunity object. Nonprofit Cloud separates a gift into several records, and the Nonprofit Cloud Developer Guide lists the fundraising objects that carry that work: Gift Commitment for a donor’s pledge, Gift Transaction for a completed payment, Gift Designation, Gift Soft Credit, Gift Refund, and Donor Gift Summary. A donation form that wrote one Opportunity under NPSP needs a different plan under Nonprofit Cloud.
What Stays and What Changes
Salesforce continues to support NPSP, so many organizations run it today and plan a move later. NPSP relied on Opportunities with rollups on Household and Contact records, plus Payment and Recurring Donation records. Nonprofit Cloud keeps the Opportunity for major gifts, grants, and planned gifts. It adds the Gift Commitment for pledged and recurring giving and the Gift Transaction for money received. Reporting on what a donor promised versus what the organization received becomes cleaner, and form integrations have more records to populate.
What a Donation Form Has to Write
Under NPSP, a form creates or updates a Contact, associates it with a Household Account, and creates an Opportunity and Payment. Under Nonprofit Cloud, a one-time gift maps to a Gift Transaction, and a recurring gift maps to a Gift Commitment with a schedule and later transactions. Salesforce provides Fundraising APIs that create gift transactions and recurring commitments with matched or new donors, so integrations should test those paths against standard record creation.
Questions for Any Form Vendor
Which Salesforce objects does the form write to in each model? Does the integration match donors to existing contacts? How does it handle recurring gifts, refunds, and designations? And does the vendor test against Nonprofit Cloud orgs, or against NPSP alone?
Where FormAssembly Fits
FormAssembly connects directly to Salesforce and sends data to standard and custom objects that the Salesforce API exposes. For NPSP, a donation form can create the Opportunity, associate the Household Account, and update constituent records. For Nonprofit Cloud, organizations should test the Gift Commitment and Gift Transaction objects in a sandbox before launch and confirm the mapping with FormAssembly support, because Salesforce provides dedicated Fundraising APIs for those records. Conditional logic adapts the form to one-time and recurring gifts under either model. Nonprofit teams planning a migration can keep one form platform in front of both data models while the back end changes.
Explore FormAssembly’s capabilities for yourself
Book a personalized demo or request a free trial today.
