Scenario 01
Migrating from NPSP
to Nonprofit Cloud
Salesforce is retiring NPSP in favor of Nonprofit Cloud (NPC), which uses native standard objects instead of custom namespaced ones. Maestro reads your existing NPSP data, maps every field to the NPC data model, and writes clean records to the new standard objects — preserving relationships, history, and giving summaries.
Source
NPSP
Custom namespace objects
→
Maestro AI
Transform + Validate
Field mapping · Data quality
→
Destination
NPC Standard Objects
RecurringDonation · GiftTransaction
Field Mapping — Recurring Donations
npe03__Recurring_Donation__c (NPSP)
→
RecurringDonation (NPC)
npe03__Contact__c→DonorId
npe03__Amount__c→InstallmentAmount
npe03__Installment_Period__c→RecurringFrequency
npe03__Date_Established__c→StartDate
npe03__Open_Ended_Status__c→Status
npe03__Recurring_Donation_Campaign__c→FundraisingCampaignId
npe03__Next_Payment_Date__c→NextPaymentDate
Step 1 — Read from NPSP
SOQL Query
salesforce_soql_query
-- Pull active recurring donors from NPSP SELECT Id, npe03__Contact__c, npe03__Contact__r.FirstName, npe03__Contact__r.LastName, npe03__Contact__r.Email, npe03__Amount__c, npe03__Installment_Period__c, npe03__Date_Established__c, npe03__Open_Ended_Status__c, npe03__Next_Payment_Date__c, npe03__Recurring_Donation_Campaign__c FROM npe03__Recurring_Donation__c WHERE npe03__Open_Ended_Status__c = 'Open' ORDER BY npe03__Amount__c DESC
Step 2 — Write to NPC
Record Creation
salesforce_create_record
-- Create NPC RecurringDonation for each row salesforce_create_record("RecurringDonation", { "DonorId": row.npe03__Contact__c, "InstallmentAmount": row.npe03__Amount__c, "RecurringFrequency": mapFrequency( row.npe03__Installment_Period__c ), "StartDate": row.npe03__Date_Established__c, "Status": "Active", "NextPaymentDate": row.npe03__Next_Payment_Date__c, "FundraisingCampaignId": row.npe03__Recurring_Donation_Campaign__c }) -- mapFrequency: "Monthly" → "Monthly" -- "Yearly" → "Annually" -- "Weekly" → "Weekly"
Sample Output — Migrated Records
NPC RecurringDonation — Created
247 records migrated
| Donor | Amount | Frequency | Start Date | Next Payment | Status |
|---|---|---|---|---|---|
| Sarah Johnson | $500.00 | Monthly | 2021-03-01 | 2025-06-01 | Active |
| Robert Chen | $250.00 | Monthly | 2022-07-15 | 2025-06-15 | Active |
| Maria Gonzalez | $1,200.00 | Annually | 2020-01-01 | 2026-01-01 | Active |
| David Park | $100.00 | Monthly | 2023-09-01 | 2025-06-01 | Active |
| Lisa Thompson | $50.00 | Weekly | 2024-01-08 | 2025-05-26 | Active |
What's Delivered in Build 40
✓
Full NPSP object audit — inventory of all custom objects, fields, and record counts
✓
Field mapping documentation — every NPSP field mapped to its NPC equivalent
✓
Migration scripts — validated, rerunnable data migration for RecurringDonation, GiftTransaction, Contact, and Account
✓
Data quality report — flags missing contacts, duplicate accounts, broken relationships before migration
✓
Rollback documentation — if anything looks wrong post-migration, we can revert
This scenario fits comfortably within a Build 40 sprint.
Typical completion: 2–3 weeks.
Equivalent traditional SI cost: $6,000–$8,000
28
est. hours
Scenario 02
Loading an External Source
into Nonprofit Cloud
Coming from a spreadsheet, legacy database, Bloomerang, DonorPerfect, or another CRM? Maestro ingests your donor data, normalizes it to NPC's data model, deduplicates contacts, creates the right Account types, and loads clean records — all without you touching a data loader.
Source
External Data
CSV · DonorPerfect · Bloomerang
→
Maestro AI
Normalize + Dedupe
Data quality · Matching rules
→
Validate
Review + Approve
Exceptions flagged for review
→
Destination
NPC Standard Objects
Contact · Account · GiftTransaction
Source example: A nonprofit migrating from DonorPerfect exports a CSV with 1,200 donor records, 4,800 gift transactions, and 180 recurring pledges. Below shows how Maestro processes each layer.
Step 1 — Ingest & Normalize Contact Data
Input — Raw CSV Row
source_data
{
"DONOR_ID": "DP-004821",
"FIRST_NAME": "Patricia",
"LAST_NAME": "Williams",
"EMAIL": "pat.williams@email.com",
"PHONE": "(312) 555-0192",
"ADDRESS1": "4821 Oak Street",
"CITY": "Chicago",
"STATE": "IL",
"ZIP": "60614",
"TOTAL_GIVING": "$4,250.00",
"LAST_GIFT": "12/15/2024",
"SPOUSE_NAME": "James Williams"
}
Output — NPC Contact + Account
salesforce_create_record
-- 1. Create Household Account salesforce_create_record("Account", { "Name": "Williams Household", "Type": "Household", "BillingStreet": "4821 Oak Street", "BillingCity": "Chicago", "BillingState": "IL" }) -- 2. Create Contact linked to Account salesforce_create_record("Contact", { "FirstName": "Patricia", "LastName": "Williams", "Email": "pat.williams@email.com", "Phone": "3125550192", "AccountId": account.Id, "ExternalId__c": "DP-004821" })
Step 2 — Load Gift Transactions
Input — Gift History Rows
source_data
-- DonorPerfect gift export (sample)
DONOR_ID | GIFT_DATE | AMOUNT | CAMPAIGN | TYPE
DP-004821 | 2024-12-15 | $500.00 | Year End | Check
DP-004821 | 2024-06-01 | $250.00 | Spring Gala | Credit
DP-004821 | 2023-12-14 | $500.00 | Year End | Check
DP-004821 | 2023-05-20 | $200.00 | Annual Fund | Online
DP-004821 | 2023-01-10 | $750.00 | Major Gifts | Wire
DP-004821 | 2022-12-12 | $500.00 | Year End | Check
DP-004821 | 2022-11-01 | $550.00 | Annual Fund | Online
Output — NPC GiftTransaction
salesforce_create_record
salesforce_create_record("GiftTransaction", { "DonorId": contact.Id, "Amount": 500.00, "TransactionDate": "2024-12-15", "FundraisingCampaignId": campaigns["Year End"], "PaymentMethod": "Check", "Status": "Completed", "Source": "DonorPerfect", "ExternalGiftId__c": "DP-004821-20241215" }) -- Idempotent: ExternalGiftId prevents -- duplicates on re-run
Step 3 — Validation Report (pre-load)
Data Quality Report — 1,200 donor records
38 exceptions flagged
| Issue Type | Count | Action | Status |
|---|---|---|---|
| Duplicate email addresses | 12 | Merge using most recent record | Review |
| Missing email — will not get comms | 18 | Load as-is, flag for enrichment | Flagged |
| Malformed phone numbers | 6 | Normalize format, load | Auto-fixed |
| Gift with no matching donor | 2 | Hold — manual review required | Review |
| 1,162 clean records | — | Load directly | Ready |
What's Delivered in Build 40
✓
Source data analysis — full assessment of your export before any data moves
✓
Contact + Account creation — with proper Household Account setup per NPC data model
✓
Gift history load — all GiftTransaction records with campaign attribution preserved
✓
Recurring pledge setup — pledges converted to NPC RecurringDonation objects
✓
External ID mapping — every record tagged with source system ID for future reference
✓
Exception report — every record that needed human review, documented with resolution
Scales with record volume. A 1,200-donor import fits within Build 40. For larger datasets, Build 80 handles up to ~5,000 donors in a single sprint.
Equivalent traditional SI cost: $7,500–$10,000
35
est. hours
Scenario 03
NPC Standard Objects
Accessible via Slack
Your fundraising and program staff live in Slack. Maestro connects a Slack-first MCP layer so your team can look up donors, log gifts, check campaign totals, and create records — all without leaving the channel where the conversation is already happening.
User
Slack Message
#fundraising · #programs
→
Maestro AI
Intent + Query
Natural language → SOQL
↔
Salesforce NPC
Read / Write
Contact · GiftTransaction · Campaign
→
Response
Formatted Result
Tables · Summaries · Confirmations
Example 1 — Donor Lookup
#fundraising
High Tide Demo Org
Example 2 — Campaign Summary
#leadership
High Tide Demo Org
What's Delivered in Build 40
✓
Slack-First MCP server — configured and deployed to your Slack workspace
✓
Donor lookup commands — name, email, phone → full NPC profile + giving history
✓
Gift logging from Slack — log a cash gift, check, or pledge without opening Salesforce
✓
Campaign dashboards on demand — totals, donor counts, YOY comparison in any channel
✓
Recurring gift management — update amounts, pause, cancel from Slack
✓
Role-based access — staff see their scope; leadership sees org-wide
Slack-First MCP setup + 5 core command types fits in Build 40. Expansion to additional workflows can continue in Maestro Run.
Equivalent traditional SI cost: $8,000–$12,000
32
est. hours
Scenario 04
NPSP → NPC Migration
Orchestrated via Slack
The most powerful Maestro pattern: Slack acts as the command center. Your team triggers reads from the legacy NPSP org, reviews exceptions, approves transformations, and monitors writes to NPC — all from a Slack channel. No SQL clients, no data loaders, no Salesforce tabs.
Command
Slack
Migration control channel
→
Read
NPSP Org
Legacy object queries
→
Maestro AI
Transform + Validate
Flags exceptions to Slack
→
Write
NPC Org
On human approval
Live Migration Session — #npsp-migration channel
#npsp-migration
Migration control channel
What's Happening Under the Hood
Read — NPSP Org
salesforce_soql_query · org=npsp
-- Maestro queries NPSP on your behalf SELECT Id, npe03__Contact__c, npe03__Contact__r.Name, npe03__Amount__c, npe03__Installment_Period__c, npe03__Date_Established__c, npe03__Open_Ended_Status__c, npe03__Next_Payment_Date__c FROM npe03__Recurring_Donation__c WHERE npe03__Open_Ended_Status__c = 'Open' AND npe03__Contact__c != null AND npe03__Amount__c > 0
Write — NPC Org
salesforce_create_record · org=npc
-- After human approval in Slack, -- Maestro writes to the NPC org FOR EACH approvedRecord: salesforce_create_record("RecurringDonation", { "DonorId": contactMap[record.npe03__Contact__c], "InstallmentAmount": record.npe03__Amount__c, "RecurringFrequency": mapFrequency(record.npe03__Installment_Period__c), "StartDate": record.npe03__Date_Established__c, "Status": "Active", "MigrationSource__c": "NPSP", "LegacyId__c": record.Id })
What's Delivered in Build 40
✓
Dual-org MCP configuration — Maestro connected to both NPSP and NPC orgs simultaneously
✓
Slack migration channel — #npsp-migration with full audit trail of every decision
✓
Human-in-the-loop approvals — no data moves without explicit Slack approval
✓
Exception surfacing — edge cases explained in plain English, not error codes
✓
Migration log artifacts — CSV export of every record migrated, held, and skipped
✓
Rollback-ready — LegacyId__c field on every NPC record links back to NPSP source
The most sophisticated scenario — but still fits in a single Build 40 sprint because AI handles the repetitive query/transform/write loops automatically.
Equivalent traditional SI cost: $12,000–$18,000
38
est. hours