01
Export review
You send an export from your current platform. We map every column, flag what will not carry over, and show you the exceptions before anything is written.
Switching platforms
The migration is on us.
Most teams stay somewhere they’ve outgrown because switching looks painful. We do the import, rebuild your forms, and stay on the call.
Talk through your migrationHow it goes.
02
Staged import
Donors, gift history, and recurring plans land in a staging area first. You review the reconciliation report and approve it before it becomes live data.
03
Form rebuild
We rebuild your donation pages and embeds to match your current branding, then hand you a side-by-side preview.
04
Recurring handoff
Recurring donors are the delicate part. We coordinate the transition and the donor messaging so plans do not silently lapse.
05
Cutover
We stay on a call with you through the switch and your first live gift. If something looks wrong, we roll back.
What nobody tells you
The parts of a migration that actually go wrong.
Better to hear it now than during cutover week.
Stored card credentials rarely transfer
Payment tokens are held by your old processor and usually cannot be moved. If your processor is changing, recurring donors will need to re-authorize. We plan the messaging for that up front rather than discovering it at cutover.
Some custom fields will not map cleanly
Every platform models donors slightly differently. We show you the unmapped fields during the review step so you decide what matters, instead of quietly dropping data.
History comes across as history
Imported gifts are marked as migrated, not as gifts DonorBeam processed. Your reporting stays honest about where each record originated.
What you need to send us.
Most migrations start with one export file.
- Donor export (CSV or XLSX)
- Gift history export
- Active recurring plan list
- A link to your current donation page