Practice sandboxTry anything: add, edit, record and send. Do not enter real people, children, gifts or contact details until we move to the launched production system. Changes stay in this browser only, and nothing sends, charges or posts.Practice only. No real data.
Legacy ChurchStaff Sandbox
Parity and data quality

While the church still runs on Elexio, the new system keeps a read-only copy of Elexio's people and households, refreshed regularly. Parity and data quality compares the two, row by row. The move from Elexio waits until they agree.

When to use this

  • Before each migration milestone, to see whether the data is ready.
  • When you have a spare half hour to tidy records in Elexio.

Read the report

  1. Look at the badge at the top: Parity: PASS or Parity: FAIL.
  2. Read the tiles: how many people, households and household memberships match, out of how many are in Elexio.
  3. Check Checks for each test the report runs, and whether it passed.
  4. Work through the Cleanup queue: the count of what's worth fixing, listed under the two cards below.

Differences that block the flip

Differences are rows where our copy and Elexio disagree:

  • Missing in mirror: in Elexio, but not in our copy.
  • Gone from Elexio: still in our copy, but no longer in Elexio. It's removed after two full refreshes.
  • Field mismatch: the same record with a different value, such as a name or a status.

These must be zero before the church can switch over. They're usually fixed by the next refresh; if one persists, the migration team investigates.

Data quality in Elexio

Data quality in Elexio lists records that are fine to copy but would cause trouble later:

  • Likely duplicate: two people with the same email, phone or name and birthday.
  • No primary contact: a household with nobody set to receive its mail and statements.
  • No household: a person in no household.
  • No birthdate: a child with no birthday, so check-in can't choose their class.

Fix these in Elexio, not here. The next refresh brings the correction across. Anything that needs fixing many times over is better turned into a rule in the import, which the migration team can set up.

Good to know

  • The copy is read-only: nothing here writes back to Elexio.
  • In the sandbox, the report is built from synthetic data.

Top tips

  • Tackle No birthdate for children first: it's the one that affects a Sunday morning.
  • Work through Likely duplicates with Elexio open in another window; merging there is quicker than explaining it later.

Was this helpful?

Your answer helps us keep these guides clear and up to date.