
A safe migration is a series of checks, not a promise that every field will move automatically. Contacts, households, past payments, outstanding pledges, attachments and recurring gifts can follow different paths. Agree the scope with both the data owner and the receiving team before setting a cutover date.
Inventory what you need to keep
List each dataset and its source: contacts, family relationships, campaign history, receipts, balances, consent records and documents. Note record counts, available export formats and any fields that only exist in free-text notes. Keep a protected original export so that a transformation can be checked against its source.
Payment credentials require a separate discussion with the payment provider. Exporting a contact list does not transfer a card token or a direct debit mandate. Do not send full card details or credentials in an ordinary spreadsheet. Ask whether existing recurring gifts can continue on the same account or require a provider-led transfer or new authorization.
Make a field map before importing
For each source field, record the destination, transformation and exception rule. Decide how to identify existing contacts and which records require human review. A shared household email is not a reliable universal identifier. Keep the original reference where useful to reconcile historical records.
For example, two adults may share one email address while having distinct donations and receipt identities. Merging them only because the email matches would lose that distinction. Put ambiguous pairs on a review list and confirm the intended relationship with the team.
Pilot a representative sample
- Include a household, a duplicate candidate, a donor without email and a Hebrew name.
- Add payments in the relevant currencies, a refund, an unpaid pledge and a recurring gift.
- Compare record counts and financial totals by currency; do not add unlike currencies together.
- Open the imported records and inspect dates, links, accents, Hebrew text and receipt references.
- Record exceptions and repeat the pilot after corrections before approving the full import.
Agree the cutover and acceptance checks
Choose who can edit each system during the transition. Define the final export, treatment of new payments and the period for reconciling differences. A successful import is not permission to delete the old records. Agree retention, access and backup needs with the responsible organization.
Ask Unisoft for a migration scope based on your actual export and data quality. Effort and timing depend on volume, formats, cleanup and payment-provider constraints. Do not cancel the old system until the agreed checks pass and the team can complete its essential daily tasks.