Skip to main content
Member Data Hygiene helps staff clean up directory records and safely move people from another church-management system.

Review directory quality

Open Members → Data hygiene to review duplicate records, incomplete profiles, directory consent that needs attention, address values that can be normalized, and the quality of the latest import. Duplicate merges keep the selected primary record and archive the other record. Address cleanup always shows a preview before applying changes.

Export people from your previous system

Member migration uses a CSV export, so you do not need to connect a provider account. Files can contain up to 10,000 data rows and can be no larger than 10 MB.

Validate before importing

  1. Open Members and choose Import members.
  2. Select the source system, then upload the CSV.
  3. Review the suggested column mapping. Map a full name, or a first/last name, and at least an email or phone. Map the provider person ID when available.
  4. Choose Validate and preview. No members are added during this step.
  5. Review accepted, duplicate, rejected, and empty rows. Download the review CSV if you need to correct any excluded rows.
  6. Commit only the accepted rows when the preview looks right.
The preview matches existing records in the same church by provider person ID, email, or normalized phone. It also detects repeated people inside the file. Duplicate, rejected, and empty rows remain outside the directory.
Imported members are not invited automatically. Review the new records, then use the member invitation action when each person is ready for access.

Undo and correct an import

Open Import history to download the review file or undo a completed migration. Undo removes only the members added by that migration. Correct the CSV and upload it again; a fresh preview checks it against the current directory before any new commit.

Privacy safeguards

Only staff with Members permission can use migration tools. Uploaded CSVs and review reports are encrypted while stored, and every migration remains inside the church that created it. Audit history keeps action names, provider and field names, and outcome counts without copying member names, contact details, or raw row values.