From the Dirt -- Database

1. Summary We run a youth sports program and our player/parent contact data currently lives in three separate systems, each in a different format. We need them merged into one clean master file — one record per player, keyed on the player’s registration email, with every parent email retained. This is a one-time cleanup, not ongoing maintenance. 2. The three sources 1. Registration platform export — raw sign-up data. Inconsistent and incomplete; roughly half of most fields are blank. The only reliably populated fields are player name and account email. 2. Email-marketing lists (Klaviyo) — provided as multiple smaller lists (each ~10 to a few hundred names), not one export, in a different field structure. These must be consolidated and de-duplicated together first, since a contact can appear on several lists. 3. Excel workbook (from TeamSnap) — lists in yet another structure, containing multiple email columns per record (e.g. two parent emails), all of which must be kept. These must also be consolidated and de-duplicated together first, since a contact can appear on several lists. There is no shared key across these sources today, and the formats don’t line up. Total scale is roughly 1,500 unique players across all sources. 3. Objective Produce one master database, one record per player, in the provided format, in which: • We create a Player ID as the unique account identifier. You can use player name and primary email together to identify the player and create the ID. • All distinct emails tied to a player are captured (so we can reach every parent). • Missing fields are backfilled from the other sources wherever the data exists. • Duplicates are merged, and anything that can’t be confidently resolved is flagged for our review — never guessed.