IMPLEMENTATION SCOPE

Compare Nonprofit Cloud starter packages

Choose a starting point for your Salesforce Nonprofit Cloud implementation. Compare what each service includes, how the scope expands and what we agree before delivery.

Compare all three implementation packages

Swipe or scroll to compare all three packages.

Compare all three implementation packages
Choose your starting point

Basic Setup

For organizations starting with out-of-the-box configuration and one focused AI agent.

Connected Fundraising

For organizations that need simple customizations, an AI agent with five chosen tools and two integrations, including one payment system.

Full Customization

For organizations whose requirements extend beyond standard configuration and the two-integration package.

Timeframe5–10 days

starting delivery range for the agreed Connected Fundraising scope after discovery and provider validation.

From 4 weeks

phased delivery for Full Customization, with milestones agreed against the selected requirements.

Which package fits your organization?

Organizations that need simple customizations, an instructed AI agent with five chosen tools and two external integrations.

Organizations that need Nonprofit Cloud fully tailored to their business requirements.

Implementation approach

Add simple customizations: custom fields, workflow tailoring, simple flows and simple Apex logic.

Fully tailor Nonprofit Cloud to the organization’s agreed business requirements through configuration, custom development and integrations.

Stakeholder management

Tailor stakeholder records, households and relationships with custom fields, workflow adjustments, simple flows and simple Apex logic.

Fully tailor stakeholder records, households and relationships, automation and integrations to the organization’s agreed business requirements.

Fundraising management

Tailor fundraising processes, gifts, commitments and designations with custom fields, workflow adjustments, simple flows and simple Apex logic.

Fully tailor fundraising processes, gifts, commitments and designations, automation and integrations to the organization’s agreed business requirements.

Program management

Tailor programs, benefits, enrollments and service delivery with custom fields, workflow adjustments, simple flows and simple Apex logic.

Fully tailor programs, benefits, enrollments and service delivery, automation and integrations to the organization’s agreed business requirements.

Outcome management

Tailor outcomes, indicators, targets and results with custom fields, workflow adjustments, simple flows and simple Apex logic.

Fully tailor outcomes, indicators, targets and results, automation and integrations to the organization’s agreed business requirements.

Case management

Tailor intake, referrals, cases and care plans with custom fields, workflow adjustments, simple flows and simple Apex logic.

Fully tailor intake, referrals, cases and care plans, automation and integrations to the organization’s agreed business requirements.

Volunteer management & grantmaking

Apply the same capability assessment; any external connection counts within the two agreed integrations.

Extend the selected capabilities only where custom requirements justify it.

Agentforce AI agents

Set up one agent with tailored instructions and five tools of your choice.

Create the agents, tools and agent integrations required by the organization, with no package limit on their number; agree the delivery scope during discovery.

System integrations

Exactly two integrations: one payment system and one other system selected during discovery.

Integration requirements, systems and data flows defined during discovery.

Payment integration

Connect one payment system. Confirm supported payment events, record mapping and reconciliation requirements before agreeing delivery.

Payment integrations and any custom payment workflows defined in the agreed solution.

Data 360 implementation

Not included; can be discussed separately.

Can be fully included in the agreed customization scope.

Data migration

Confirm source data and matching rules across Salesforce and the two connected systems.

Define migration stages, transformations and validation around the agreed legacy systems.

Access & permissions

Configure staff access and access required by the two integrations.

Design access for custom processes and any external user experience included in scope.

Reporting

Extend reporting with data from the two connected systems where required.

Build tailored reporting for the agreed processes and available data.

Self-service portals

Portal requirements assessed separately from the two integrations.

Define portal users, journeys, data access and delivery scope if a portal is required.

Implementation management

Tailor implementation workflows with custom fields, simple flows and simple Apex logic.

Fully tailor implementation processes, automation and integrations to the organization’s agreed requirements.

Testing, training & handover

Validate configured processes and both integrations; agree monitoring and operational ownership.

Define acceptance tests, training and handover for each implementation phase.

Plan your next stepDiscuss implementationDiscuss implementation

A discovery plan before implementation

Turn your priorities into a delivery-ready scope. Discovery comes before the implementation ranges above; we confirm timing once requirements, access, data and integration dependencies are understood.

  1. Gather business requirements

    Meet fundraising, finance, program and operations stakeholders. Agree business goals, the processes in scope, decision owners and measurable success criteria. Output: a shared requirements brief.

  2. Understand pain points

    Map the current journey from donation or intake to reconciliation and reporting. Identify manual handoffs, duplicate data, failed payments and service bottlenecks. Output: a prioritized problem map and system inventory.

  3. Collect and prioritize user stories

    Capture what donors, finance teams, program staff and administrators need to do. Define acceptance criteria, roles and permissions, then separate launch essentials from later improvements. Output: a prioritized backlog with testable user stories.

  4. Assess and handle risks

    Review data quality, sensitive beneficiary information, migration, API access, payment events, licensing and team availability. Assign an owner and mitigation to each risk; validate uncertain integrations before committing. Output: a risk register, dependencies and fallback options.

  5. Agree the delivery plan

    Select the package, confirm scope boundaries and responsibilities, and agree milestones, acceptance checks, training and launch readiness. Output: an agreed statement of work and implementation plan.

NPSP to Agentforce Nonprofit Edition Migration

Move from Nonprofit Success Pack to Agentforce Nonprofit Edition with a migration shaped around your organization’s needs. We assess your current setup, preserve what works, improve existing functionality, and address the pain points that slow your team down.

Scope, cost, and timing are agreed after assessment. Starter-setup delivery ranges do not apply.

  1. Initial discovery and system audit

    Review business processes, NPSP configuration, objects, fields, data quality, permissions, reporting, stakeholders and risks. Agree what to retain, redesign or retire.

    Proposed output: A system assessment, migration objectives and agreed scope.

  2. Integration and application audit

    Assess installed packages, payment and finance systems, APIs, middleware, custom code, flows and triggers for NPSP dependencies. Confirm compatibility and decide what to adapt, rebuild, replace or retire.

    Proposed output: An integration inventory, compatibility decisions and sequenced rebuild backlog.

  3. Staff and donor journeys and backlog

    Map current and future journeys for fundraisers, finance and service teams, alongside donor journeys from first gift through recurring giving, acknowledgments and stewardship. Capture exceptions, access needs, user stories and acceptance criteria for workflows, integrations and reporting.

    Proposed output: Agreed journey maps and a prioritized delivery backlog with testable acceptance criteria.

  4. Field mapping, transformation and migration

    Map NPSP objects and fields to Agentforce Nonprofit Edition. Define constituent and household relationships, contact points, campaigns, gifts, recurring commitments, payments, refunds, soft credits and designations. Agree custom fields, picklists, legacy IDs, ownership, record splits, retention and exclusions. Back up and clean source data, prepare target security and metadata, and load agreed records, activities and files in dependency order.

    Proposed output: An approved mapping workbook, transformation rules, retention plan and repeatable migration loads with source-to-target traceability.

  5. Validation, cutover and handover

    Rehearse loads; reconcile financial totals, relationships and ownership; test integrations and staff and donor journeys against the backlog. Resolve acceptance issues and train staff. Agree final backup, freeze/delta handling, go/no-go owners and fallback before launch; monitor exceptions and transfer operational ownership.

    Proposed output: Reconciliation and acceptance evidence, a cutover runbook, training and admin handover with an agreed stabilization scope.

Discuss your migration

Scope, costs and delivery agreements

Routine Automation sells and provides implementation services only. We do not sell Salesforce licenses, AI tokens, credits, subscriptions or other Salesforce products. Discovery establishes the selected features, configuration depth, deliverables, responsibilities, acceptance criteria and delivery dates.

Product entitlements and implementation scope are different. Confirm the customer’s existing subscription before identifying any additional licenses, subscriptions or consumption costs. Not every extension requires a new purchase; portal access and AI agent entitlements depend on the chosen solution.

Basic Setup uses standard functionality without external integrations or custom development. Connected Fundraising includes exactly two integrations: one payment system and a second agreed system. Full Customization is scoped around the requirements that need tailored work.

For each integration, confirm supported objects, data direction, events, credentials and exception handling. Do not assume payment collection, refunds or settlement reconciliation are automatic because gift records exist in Salesforce.

Migration volume, history, cleansing, NPSP transformation, payment-token transfer and ongoing Salesforce support are assessed and agreed explicitly. The table does not establish fixed allowances or support commitments.

No pitch. Strategy only.

By submitting this form, you agree to Routine Automation processing your personal information in accordance with the Privacy Policy.