Bulk import for teams — all five importers now live

The team importer is live — the fifth and final piece of the bulk import suite. You can now import athletes, facilities, volunteers, coaches, and teams all from the Import menu in the top nav.

Who can use it: club admins. Where to find it: top nav → Import → Teams.

What it does

• Upload a CSV with one row per team. Only name and age_group are required — everything else is optional.
• A team is identified by (name + age_group). This means your club can have "Tigers U12" and "Tigers U14" as distinct teams and the importer won’t treat them as duplicates of each other.
• Optional foreign keys (season, primary coach, home field) are looked up by name/email. You don’t need to know database IDs — just enter the season name, coach email, and venue/field names, and the importer resolves them automatically.

Example

 name,age_group,division,skill_level,gender,season_name,primary_coach_email,home_venue_name,home_field_name
Tigers,U12,Competitive,Intermediate,Mixed,Spring 2026,pat.henderson@example.com,Greenlake Park,Field A
Tigers,U14,Competitive,Advanced,Mixed,Spring 2026,riley.nakamura@example.com,Greenlake Park,Field B
Lightning,U10,Recreational,Beginner,Mixed,,,, 

Three teams created. Tigers U12 and Tigers U14 are both created (composite identity). Lightning U10 is created with just the basics — no season, no coach, no home field assigned. All three are valid.

What’s required

Name and age_group only. Age group must be one of: U6 , U8 , U10 , U12 , U14 , U16 , U18 , Adult .

What’s optional

Division, skill level (Beginner/Intermediate/Advanced/Elite), gender (Male/Female/Mixed), status (forming/active/completed/disbanded), max_players, team_color, season name, program name, primary coach email, home venue name + home field name.

Foreign key lookups are strict

If you provide a primary_coach_email that doesn’t match an existing user account, that row will error with a clear message ("Primary coach user with email '…' not found — import coaches first, or create the user account"). Same for season, home venue, and home field. This prevents silent data corruption when a CSV has a typo.

Recommended order for a fresh club onboarding:

1. Facilities — import your venues and fields first
2. Coaches — create user accounts for your coaches
3. Teams — now references to fields and coaches will resolve cleanly
4. Athletes — fill in rosters (the existing athlete importer has an optional team picker)
5. Volunteers — assign team helpers

The bulk importer suite is complete

With teams shipping, all five entity types from the original scope are now live. Adding a new entity type in the future is about 150 lines of code plus a few frontend dict entries — the generic wizard, column mapping, preview, progress polling, and error reporting all come for free from the shared framework.

What’s still on the wishlist for the importer broadly(not team-specific):

• Invite emails for auto-created user accounts (volunteers and coaches)
• "Update existing rows" mode — currently all importers skip matches instead of updating
• Downloadable error CSV for failed rows (error list is visible in the UI only)
• Additional entity types as new use cases emerge