Instead of Salesforce Nonprofit Cloud
Stop renting Salesforce Nonprofit Cloud. Own your programme delivery system.
We build your version around the services you deliver, map and reconcile your Salesforce records, and run it for you. Your benefit units, your reporting deadlines and your evidence.
Salesforce lists Core at US$70 per paid user/month, billed annually. Eligible nonprofits receive ten free Core licences, with discounts available.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the subscription buys
A broad nonprofit platform, priced by paid seat
Salesforce Nonprofit Cloud covers more than programme delivery. Compare the work your team needs with the edition and paid licences on your agreement. Core is US$70 per paid user/month, billed annually.
Paid staff licences
Beyond eligible donated licences, the public price is charged per user. Check your actual allocation and discounts before comparing costs.
An annual commitment
The listed monthly Core rate is billed annually. Use your contract renewal date when planning a change.
A wider suite
The pricing comparison includes fundraising, programme management and outcomes. Start with the delivery and reporting work you actually want to replace.
Storage by edition
The vendor lists different storage allocations by edition. Your evidence files and their retention needs belong in the comparison.
Related products
Salesforce lists Experience Cloud and Marketing Cloud among related products and add-ons. Confirm which products your organisation uses.
Services around the software
The vendor offers professional services and implementation partners. Compare the subscription alongside the work needed to maintain your process.
Your programme delivery desk
From a planned service to a supported report
Capacity
See the gap before committing more services
Keep each benefit target beside what has been delivered and what future sessions can provide.
- check Separate parcels, hours and visits
- check Compare target units with delivered units
- check Count capacity in future planned sessions
- check Find benefits with a gap after planned capacity is included
Delivery
Keep each recorded benefit tied to its evidence
Link the participant enrolment, the session and the evidence reference. The system checks that the programme and dates agree.
- check Record delivered units against a session
- check Reject quantities above session capacity
- check Keep a correction history when a delivery is voided
- check Find past sessions with no recorded deliveries
Reporting
Know which reports need work
Put reporting dates beside delivery records and the people responsible. Prepare a private evidence pack in your own brand.
- check Track reporting deadlines and owners
- check Show overdue reports alongside unreconciled sessions
- check Produce programme summaries and session registers
- check Keep delivery outputs separate from claims about social outcomes
Record care
Review evidence before it becomes a problem
Check retention dates and participant accuracy reviews against the recorded policy. Each check states its source and limits.
- check Flag short retention dates for applicable Australian charity delivery records
- check Review stale participant accuracy checks
- check List personal records due for a retention review
- check Keep legal holds and disposal decisions with the responsible person
Make it yours
Design your own Salesforce Nonprofit Cloud replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Salesforce Nonprofit Cloud. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Salesforce Nonprofit Cloud data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Programme Delivery for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Programme Delivery for Claude Code
Connected to your own database
Which benefits need more capacity?
ben13
- Programme
- Community pantry
- Benefit
- Pantry delivery route
- Unit
- deliveries
- Target units
- 40.00
- Delivered units
- 0
- Future capacity units
- 0
- Unplanned units
- 40.00
ben11
- Programme
- Community pantry
- Benefit
- Pantry parcels
- Unit
- parcels
- Target units
- 160.00
- Delivered units
- 5.00
- Future capacity units
- 25.00
- Unplanned units
- 130.00
ben12
- Programme
- Repair and reuse
- Benefit
- Repair sessions
- Unit
- hours
- Target units
- 80.00
- Delivered units
- 4.00
- Future capacity units
- 10.00
- Unplanned units
- 66.00
| Source id | Programme | Benefit | Unit | Target units | Delivered units | Future capacity units | Unplanned units |
|---|---|---|---|---|---|---|---|
| ben13 | Community pantry | Pantry delivery route | deliveries | 40.00 | 0 | 0 | 40.00 |
| ben11 | Community pantry | Pantry parcels | parcels | 160.00 | 5.00 | 25.00 | 130.00 |
| ben12 | Repair and reuse | Repair sessions | hours | 80.00 | 4.00 | 10.00 | 66.00 |
Ask it anything
Questions answered from your programme records
These examples run on fictional demonstration records. They combine delivery, capacity and reporting facts. Salesforce can also be configured with custom reports.
Switching
How to switch from Salesforce Nonprofit Cloud
A move usually involves exporting and mapping the programme records you need, checking a test import, then validating the new database alongside Salesforce before you switch.
- 1
Export supported records
Export Salesforce Details Only CSV reports for the supported programme records you want to move. Include source IDs and relationship IDs so records can be matched correctly. The free base covers benefits, sessions, enrolments, delivered units and reporting evidence, not every part of Salesforce Nonprofit Cloud. Keep exported files private, and agree which connected work remains outside this replacement.
- 2
Map fields and relationships
Use the supplied mapping example to match your Salesforce report labels to the records this database supports. Check dates and relationships before moving on, and decide how much history you need. Attachments stay in your controlled evidence store unless their migration is separately agreed, so note any evidence links your team must continue to use.
- 3
Test, then load records
Start with a test run to see how the mapped reports will be handled before importing real records. The importer accepts mapped report exports for supported records and processes them in dependency order. Once the test results make sense, load the records into the private database. Keep the exported files private, and do not mix fictional demo records with real records.
- 4
Review import results
Check the test and import results, including ignored columns and any conflicts the import reports. Reconcile report labels, dates and relationships against Salesforce before relying on the new records. If the results show a mapping problem, correct the mapping and repeat the import. Repeat imports leave unchanged rows alone, which helps when you need to rerun the process.
- 5
Run both, then switch
Keep Salesforce and the new database in use side by side for a short period. Compare the programme records, delivery evidence and reporting work you rely on, and confirm that staff know which system to use for each task. Switch off Salesforce Nonprofit Cloud only after the records and workflows you intend to replace have been checked, and any connected work staying outside has been accounted for.
Where the real effort goes
The real work is usually mapping your own report labels, fields, units and reporting rules, then deciding which history to bring across and checking that it reconciles. Attachments remain in your controlled evidence store unless their migration is separately agreed. When you have Enterprise DNA run the system, they handle this mapping and reconciliation as part of the custom build.
Not ready for a call?
Get your Salesforce Nonprofit Cloud switch plan by email
We will send you the step-by-step plan for moving your business off Salesforce Nonprofit Cloud, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Salesforce Nonprofit Cloud switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Choose who builds and runs your version
Open source
Do it yourself
Free, open source
- 1 Clone the repo and install its dependencies
- 2 Run npm test and npm run demo, then open it in Claude Code, Codex, OpenCode or Cursor
- 3 Export Salesforce Details Only CSV reports, map your headings and run import salesforce with --dry-run
- 4 Reconcile the results, import your records and ask /weekly-review
Built around your business
We customise it
One setup fee, then a retainer
- check Your programme names, benefit units and reporting rules
- check Your Salesforce records mapped and reconciled
- check A staff screen, participant portal or different technical foundation scoped to your needs
- check Your evidence storage and other connections agreed before the build
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed in a database your organisation owns
- check Agreed access, backups and connections operated for you
- check Your weekly reviews and reporting paperwork maintained
- check Run through Omni by Enterprise DNA with a named team responsible for the system
Questions
Instead of Salesforce Nonprofit Cloud, answered
Can this replace everything in Salesforce Nonprofit Cloud? expand_more
The free base handles non-cash programme delivery: benefits, sessions, enrolments, delivered units and reporting evidence. We scope fundraising, portals and other connected work around your organisation before agreeing the full replacement.
Will our Salesforce history come across? expand_more
The free version imports mapped report exports for the supported records. Your report labels, dates and relationships must be checked first. We map and reconcile that history in a custom build. Attachments remain in your controlled evidence store unless their migration is separately agreed.
What if our charity receives free Salesforce licences? expand_more
Include them in the comparison. Salesforce offers ten free Core licences to eligible nonprofits and discounts on additional licences. We compare your actual contract and operating needs, so the decision is based on what you pay and use.
Can staff collect attendance on a phone and keep records private? expand_more
We can build the staff screen, access controls and evidence connections your team needs into the custom version. The free base is for trusted operators using a private database. Agree the access, backup and retention arrangements before bringing personal records across.
What does Enterprise DNA charge and who runs it? expand_more
One setup fee, then a retainer for the agreed ongoing work. We review your programmes, records and connections with you, then quote the scope. The system is yours, with Enterprise DNA responsible for the operations covered by that agreement.
Bring your programme workflow and your software bill
Spend 30 minutes with Sam. Review the services you deliver, the evidence funders ask for and what your team pays to maintain the system. Leave with a clear scope for your version.
Programme Delivery for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Salesforce Nonprofit Cloud?
Get your version built