Switching with reviewed CSV files

Supported source and version

Supported source coverage is only the talanton-r1-csv-v1 bundle. A spreadsheet or export must be prepared into that exact format; an arbitrary CSV export is not automatically compatible. No named church-management product has a verified adapter, so this guide does not list one as supported. Keep an unchanged source copy, stable source keys (including leading zeros), the export cutoff and a manifest with file checksums.

ChurchTrac is a named future priority, not a verified adapter or version, and it is not supported coverage. QuickBooks is an accounting integration/export target, not a church-record migration source.

Use UTF-8 CSV, exact case-sensitive headers, YYYY-MM-DD dates and USD decimal amounts with two fractional digits. Do not substitute invented dates for unknown history. The operator verifies files and mappings before a dry run.

What transfers and what needs review

people.csv: person_key, display_name and age_class; supported optional contact/name fields. households.csv: household_key and display_name plus address fields. household_members.csv: membership_key, household_key and person_key with reviewed relationships and optional historical dates.

funds.csv: fund_key and name. gifts.csv: gift_key, gift_date, amount, currency, tender and donor_kind; named gifts require a resolvable person_key. gift_allocations.csv: allocation_key, gift_key, fund_key and amount. Positive allocations must add exactly to the parent gift.

The current evaluation uses synthetic adults. Minor or unknown-age records, birth dates, private notes, photos, custody files, pledges, noncash gifts and unsupported adjustments are outside this R1 import exercise. Never remove refunds or reversals just to make totals match: stop the affected financial scope and agree a reviewed representation.

The church reviewer resolves possible duplicates, unmatched donors, relationship ambiguity and excluded rows. The operator controls mappings, run approval and recovery. No silent merge or automatic public church provisioning is promised.

A sample reconciliation

Fictional people example: 12 source rows = 10 accepted + 1 explicitly excluded + 1 rejected + 0 unresolved. Record the reason and reviewer for every exception; a matching equation alone does not approve data loss.

Fictional giving example: two accepted gifts of 100.00 and 50.00 total 150.00 USD. Allocations of 120.00 to General and 30.00 to Care also total 150.00. Compare by fund, date and donor as well as the overall total. Unresolved or unsupported financial rows block approval.

Preview, resolve exceptions and approve the pinned source/mapping version. Execute with checkpoints, reconcile target counts and money, and review the printable completion reference. An interrupted run resumes from confirmed checkpoints; after handover, preserve live changes and use the reviewed correction/recovery process.

Inquiry to onboarding

Send the form below with your current system. You receive one inquiry reference. Sending it again with the same request returns that reference and does not open a second inquiry. A workforce operator converts that same inquiry into one onboarding or migration support case. The case carries the church, contact, source and message already on the inquiry, so nobody types them again. Church staff cannot read the platform inquiry queue.

That support case begins assisted provisioning and migration planning. The operator still prepares the church workspace and migration workbench case. Sending this form neither uploads records nor starts an import, and it does not issue a certificate or collect a payment.

Printable cutover record

Preparation worksheet — not an approval or an issued completion reference. Church: __________ Source/version: __________ Export cutoff: __________ Case/run reference: __________

Source and target row counts: __________ Totals by fund/date/donor: __________ Exclusions and exception decisions: __________ Reviewer: __________

Source of record before/after: __________ Freeze and catch-up verified: __________ Recovery reference: __________ Handover reviewer/date: __________

At actual handover, use the migration workbench Cutover completion reference, which records the executed run and reviewed outcome. Keep the prior system read-only according to the agreed transition plan.

Things to try

• Inventory and source of recordList required domains, source version, cutoff and who authorizes cutover. Keep customer files out of the public inquiry form.
• Review mappings and exceptionsName the church reviewer. Account for every source row and unsupported type; preserve the original export.
• Reconcile and prepare cutoverCompare counts and exact amounts, record exclusions and recovery instructions, then obtain the workbench completion reference at handover.