Radley LabsLoading site…The interactive site is taking longer to load. Reload site
Radley Labs

Check supporter records before a move

How we help

Before and after

Two exports use slightly different names for a supporter ID. Importing first makes it harder to see which source row caused a duplicate or missing value.

The team can review a field map, trial file and exception list against the destination template before deciding how to handle the records.

A worked example

A membership export contains two rows with the same member reference and a blank renewal date. A fictitious equivalent shows where the target would need a decision.

What you receive

  • A field map from source to destination
  • A trial file with an exceptions report
  • A checklist your team can run again

Where your team stays involved

The data owner decides which record to keep, what may be transferred and how to handle consent or communication preferences.

One source, one target template, up to 100 de-identified sample rows. The rehearsal does not make a live import or decide how to merge people.

Starting the conversation

Name the source and destination and describe the fields in general terms. Use fictitious supporter examples.

Ways we can help

Rehearse the supporter import

Ask for a price

Trial up to 100 de-identified rows and receive the field map, trial file, exceptions report and checklist.

What you receive

A supporter field map, trial import file, exceptions report and repeatable checklist.

Plan the records handover

£195 one-off

If ownership or the destination is unclear, map one process and agree a manageable first step.

What you receive

A map of the records workflow and recommended next steps for a manageable move.