Why it matters
One connected place for this work.
A CRM migration is not just a file upload. Sapling treats imports as a staged workflow: upload, analyze, review mappings, resolve issues, ask Orchid for help, and commit only when the team is ready.
Back to features
Feature area
AI Driven Imports
Sapling uses AI-assisted import review to help teams bring in contacts, gifts, notes, event attendees, Sapling Pay batches, and messy CRM exports with review before commit.
Import review preview
Click a batch, review the shape, then commit when it is clean.
Imports should be staged, explainable, and reversible enough that teams can trust what enters the CRM.
Routing and field mapping
Sapling maps file columns into CRM fields before the batch reaches review.
Your CSV columns
Auto-mapped from the file.
Gift
1.Donor name *
Gift
2.Gift amount *
Gift
3.Fund
Contact
4.Primary email
Event
5.Guest of
Next: clean before commit
Then each row moves through three review steps before anything merges.
Sapling separates the rows that need attention, the rows that need a human merge or match decision, and the rows that are clean enough to add. That keeps imports useful without turning messy files into permanent CRM clutter.
Resolve records before merge
Click each stage to see how rows are sorted before they become donor records, gifts, or held-back work.
Needs Attention
Errors
Unparseable values, unknown types, or duplicate rows inside the same file.
Avery StoneAppears twice with different gift amountsCombine rows
Line 214Unknown contact type: "Family Org"Choose type
Line 281Amount field contains textEdit value
Fix, route, link, approve, or skipRe-checked before Review
The workflow is intentionally staged
Sapling starts with upload or batch creation, analyzes the file, then sends it to review before records are written.
- Upload or manual entry
- Background parsing and analysis
- Mapping review
- Needs-attention queue
- Commit only after approval
Orchid helps explain the file
Orchid can help explain flagged columns, summarize duplicates, describe missing rows, and clarify suggested mappings.
- Column mapping explanations
- Duplicate summaries
- Missing-info guidance
- Contact type reasoning
- Row issue review
Messy nonprofit data is expected
The import system is designed for real nonprofit files: households, organizations, DAFs, gifts, notes, events, refunds, matching gifts, and old CRM IDs.
- Households and individuals
- DAF and passthrough records
- Anonymous donor handling
- Refund and matching-gift review
- External and Sapling public IDs
Source platforms are treated as context
Imports can come from processors, donation tools, accounting systems, events platforms, email tools, and donor CRMs.
- Stripe and Sapling Pay
- Donorbox, Givebutter, Classy, Qgiv, and other donation tools
- QuickBooks, Xero, Sage, and accounting exports
- Eventbrite, OneCause, Auctria, and event files
- Bloomerang, DonorPerfect, Raiser’s Edge, Neon, Virtuous, and other CRM exports
Review means the team stays in control
AI should not silently rewrite the database. Sapling surfaces duplicate candidates, field overrides, row decisions, and commit status.
- Duplicate candidates and match reasoning
- Keep existing, use new, or append field overrides
- Create, merge, skip, hold, or approve row decisions
- Readiness and issue summaries
- Import history and batch status
Imports connect to the rest of the CRM
An import can create or update contacts, gifts, notes, individuals, addresses, batches, and event attendees.
- Contacts and households
- Gifts and donation batches
- Notes and history
- Event attendees
- Reports and dashboards
Keep exploring