Import registrations from a CSV
Upload, preview, review the warnings, and commit - plus how returning families are matched.
Your church’s registration system produces an export; FlightPath turns it into members, households and class placements. The import always shows you what it is about to do before it does it.
Admin only, on the Online Registration page.
Import a file#
- Open Online Registration and upload the file.
- Say whether it is Clubbers or Leaders.
- Read the preview — a full dry run that writes nothing. Check the created and updated counts, the people it matched, and every warning.
- Commit the import to apply it.
Screenshot to come
The CSV import preview showing created and updated counts, matched people, and warnings
The preview writes nothing#
That is the point of it. You can preview the same file as many times as you like, fix the export, and preview again, without touching your data.
The uploaded file is deleted after the import runs, and abandoned previews are cleaned up automatically every hour — these files hold children’s names, birthdays and addresses, so they are not left sitting around.
How returning families are matched#
Across years, FlightPath matches a submission to an existing person in this order, most authoritative first:
- The registration system’s own person ID.
- The profile the registration system matched the submission to — this is a name, so where both sides know a birthday, the birthdays have to agree.
- Name plus birthday.
A miss on all three means a genuinely new person.
Siblings and households#
Siblings are grouped into one household by the parent email. If a family keeps splitting into two households across years, an inconsistent parent email on the registration is nearly always why.
Class placement#
- Where the registration label names a class, that class is used.
- Where it does not — Cubbies often registers as one undifferentiated “Cubbies” — age at the September 30 age cutoff places the child into an age-ranged class.
- An explicit class always wins over the age rule.
For age placement to work, your classes need age ranges. Set them before you import — see Clubs and classes.
Every submission is kept#
Re-importing the same file updates its record in place. A new club year’s response adds a second one. So a family’s registration history builds up year on year rather than overwriting itself, which is what makes the supplies workbook work for last year as well as this one.
Leader imports#
A leader import counts as the record that they served that club year, feeding volunteer service history.
What it writes to the log#
One audit-log line for the whole run, not hundreds. So look for a single entry rather than a wall of them — see The Activity Log.
“A returning family got duplicated”#
Check two things in the export:
- Does it include the registration system’s person ID? That is the most authoritative match.
- Is the parent email the same as last year’s? Siblings group by it.
If duplicates are already in, an admin can merge the households — but merging is destructive, so read Households first.