Exporting to DraftKings & FanDuel

The toolbar above the lineup cards handles everything that leaves the app. There are two distinct workflows: a plain lineup export, and the mass-entry Upload → Fill flow.

The results toolbar: Export, Randomize, Upload CSV, Fill, Rand Fill
1

Export — plain lineup CSV

Export downloads your lineups as DK_lineups_<date>.csv (or FD_lineups_<date>.csv on FanDuel). For MLB Classic the DK header is P,P,C,1B,2B,3B,SS,OF,OF,OF with DraftKings player IDs in the cells — exactly what DK's bulk lineup upload expects. Randomize is the same export with the lineup order shuffled.

2

Upload → Fill — mass-entry files

If you've already reserved contest entries, download the entries file from DraftKings (or FanDuel) — the one with Entry ID, Contest Name, and Fee columns — then:

  1. Click Upload CSV and pick that file. The button turns green and shows the entry count.
  2. Click Fill. Your lineups are written into the entry rows — Entry ID, contest, and fee preserved — cycling through your lineup set if there are more entries than lineups. Downloads as DK_entries_filled_<date>.csv.
  3. Rand Fill does the same with the lineup order shuffled first.

Re-upload the filled file on the DFS site to set all entries at once.

3

The build bar's other Export

The Export button in the bottom build bar is different: it downloads the current player pool (projections, salaries, ownership) as <Slate>_player_pool.csv — a data export, not lineups.

FanDuel MLB rules differ from DraftKings: a $35,000 cap and at most 4 batters per team. The FD export/fill paths handle FD's id:Name cell format automatically.

Keep the platform toggle matched to where you're entering. Exported IDs are platform-specific — a DK file will not import into FanDuel.

Strategy guidance coming soon
Allocating lineups across contests and entry counts