Moving off spreadsheets — a charity's guide to CRM migration

Almost every charity we meet runs on spreadsheets for longer than it should. It’s not a failure — a spreadsheet is free, familiar and good enough on day one. The problem is what happens by year five: donor records scattered across a dozen tabs, three people’s slightly different copies, Gift Aid history nobody trusts, and a growing fear that migrating it all will break something. So the charity stays put, and the data gets worse.

This guide is about getting off spreadsheets safely. Not the sales pitch for a CRM — the actual mechanics of moving years of messy data without losing a single donor or a penny of Gift Aid.

The real cost of staying on spreadsheets

The pain rarely shows up as one big failure. It shows up as a hundred small ones: a Gift Aid claim that misses eligible donations because the declaration was on a different sheet; a thank-you that goes to someone who died last year; an appeal that emails the same donor three times under three spellings of their name; a year-end that takes a fortnight because the numbers have to be stitched together by hand.

None of that is a spreadsheet’s fault. Spreadsheets were never meant to be a shared database of relationships. The moment more than one person needs the truth about a donor at the same time, you’ve outgrown them.

Step 1 — Find every copy of the data

You cannot migrate what you haven’t found. Before anyone talks about software, list every place donor, member and finance data currently lives: the main donations workbook, the old Access or desktop database, the Gift Aid declarations folder, the events sign-up sheets, the mail-merge list on someone’s laptop, the payment provider’s own records.

For each source, note roughly how many records it holds, who owns it, what format it’s in, and — crucially — whether it contains personal data you’re still allowed to keep. This audit is the single most valuable hour in the whole project. Our migration kit gives you the checklist to run it.

Step 2 — Clean before you move, not after

The temptation is to import everything and tidy up later. Don’t. A migration is the one moment you have permission to throw away the junk, and “later” never comes.

Work through three cleaning jobs: de-duplicate (the same donor entered under different names or addresses), standardise (postcodes, phone formats, title case) and decide what to drop (dead emails, records with no lawful basis to keep). Log every fix as you go — if a trustee later asks what happened to a record, you want an answer, not a shrug.

Step 3 — Map old fields to new before you sign anything

Every CRM has its own idea of how a donor should be structured. Your job is to decide, for each column in the old system, where it lands in the new one — and what gets transformed on the way (splitting “Full Name” into first and last, mapping a “GiftAid Y/N” column onto a proper declaration status).

Do this on paper first. A field-mapping table is also the clearest brief you can hand a CRM supplier: it turns “can you import our data?” into “here is exactly what our data is.”

Step 4 — Make Gift Aid survive the move

For UK charities this is where migrations quietly go wrong. Gift Aid depends on a valid declaration linked to each donor and an accurate donation history. If either is mangled in the move, you either lose claims or risk claiming on donations you shouldn’t.

Confirm two things with any CRM: that it stores declarations properly (date, method, what they cover) and that it can submit claims directly to HMRC through Charities Online. Our HMRC-listed Gift Aid software does both, and the UK charity Gift Aid complete guide covers the claim itself.

Step 5 — Import into a sandbox, validate, then go live

Never import straight into the system you’ll rely on. Load a representative sample into a test environment first, then spot-check twenty real records against the source by hand. If names, giving history and declarations all match, scale up to the full import. Keep the old spreadsheets as a read-only backup for twelve months — then delete them, so there’s only one source of truth.

What “done” looks like

A successful migration is quiet. One place holds the truth about every donor. Gift Aid claims build themselves from the data instead of a spreadsheet marathon. New staff can be trusted with the system on day one because there’s nothing hidden in someone’s personal file. And the year-end that used to take a fortnight takes an afternoon.

That’s the destination. The Legacy → CRM Migration Kit below is the map — the audit checklist, field-mapping template, cleaning log and project plan we use on real charity migrations. Download it, work through it, and when you’re ready to move, talk to our team — or see how iCHARMS is built for exactly this.