Mappings

A mapping connects one board to one worksheet table, in one direction, with a column map and a schedule. It's the unit everything else hangs off: runs, history, and alerts are all per-mapping.

Board → Excel

The board is the source of truth. Each sync makes the Excel table match the board:

New items become new rows; changed items update their row; items deleted on the board have their row removed.
The first column is always monday_id — the item's id, which is how rows stay matched. Don't edit it.
Only the synced table is touched. Anything else in the workbook — formulas, pivot tables, charts, other sheets — is yours and survives every sync.
Column values arrive as display text (what you see on the board), so Status shows "Done", dates show as dates, and people columns show names.

Edits you make inside the synced table will be overwritten by the next sync — the board wins. Build formulas and reports outside the table (or in another sheet) and reference the table's cells.

Excel → board

The spreadsheet is the source. Rows in your Excel table become items on the board:

Your data must be a real Excel table (select the range → Insert → Table), exactly one per worksheet.
Columns are matched by header name, so you can reorder or insert columns freely.
Every mapped cell is validated and converted to the monday column's type before writing. Rows that fail validation are skipped and listed in the run report — never guessed at, never half-written.
New status/dropdown labels that appear in your sheet are created on the board automatically.
Rows without a match on the board create new items; matched rows update; how matching works is the key strategy.

Validation preview

Before an Excel → board mapping's first run, the app shows a preview: how many rows would be created, updated, skipped as unchanged, and flagged with problems — with per-row reasons. Nothing is written until you approve.

Large imports

monday.com limits how fast items can be written (roughly 300 rows per minute). Big first imports run in background passes: the first pass starts immediately and the rest continues automatically — the run log shows progress like "wrote 300 of 4,200 changed rows this pass" until the import completes.

Conflict policy (Excel → board)

Policy	Behavior when a board item changed since the last sync
Source wins (default)	The spreadsheet's version overwrites the board edit.
Skip & flag	The row is skipped and flagged in the run report, protecting the board edit. Fix the sheet (or accept the board's version) and re-sync.

Changing a mapping

Remap columns in the view rebuilds the mapping with a new column selection and a fresh workbook — the old workbook is left untouched in OneDrive. Deleting a mapping stops its syncs and deletes its run history; it never deletes your workbook.