A whole season in 30 seconds.

What works

Required columns: date, time, field, home team, away team. Optional columns: Park, Crew (override default crew size for that game), Notes. The importer is forgiving about column headers — "home", "Home Team", and "hometeam" all map to the same thing.

Date and time can come as two columns (e.g., 5/12/2026 + 3:30 PM) or one combined ISO column (2026-05-12T15:30). 12-hour and 24-hour time both work.

Drag, drop, review, commit

The import screen is a drop zone — pull the CSV out of your downloads folder onto the page. Every row appears in a preview table with parsed date, matchup, field, crew size, and any issues flagged with the row number. You can scroll the whole schedule and confirm everything looks right before any game gets written.

Parks, mapped row by row

If your CSV has a Park column, the preview table gives you three options per park name: skip (don't attach a park), create a new park record, or link to a park already in your league. New parks are created before the games import so every game lands with its park reference set correctly.

Atomic writes

The actual import runs as Firestore batch writes — chunked in groups of a few hundred to respect platform limits, but committed without manual coordination. Either every row commits or the operation fails cleanly and nothing is half-imported.

Adding games one by one

Mid-season makeup game? You don't need a CSV — the games page has a "New game" form for one-off additions. CSV import is for the bulk season load; the form is for everything after.