Migrate your monday Work Management data

Boards are the top-level workspace container. Each Board has a name, owner, workspace, and set of Groups. We map Board identity and metadata 1:1. Note that board-level settings like default view and notification preferences are API-readable but may require re-application in the destination.

Items are the primary work unit on a Board — the equivalent of Tasks in standard PM terminology. Every Item has a name, status, assignees, and timestamps. The API returns Items with their column values as key-value pairs. We map Item fields by column ID and preserve status, date, and assignee data in standard normalized format.

Groups are horizontal row containers within a Board, typically representing a status column or phase. Items live inside Groups. We preserve Group order and name, and we map Items into matching Groups in the destination based on Group name or position.

Columns are monday.com's field model — there are 20+ column types including Status, Date, Timeline, Numbers, Text, Link, File, Dependency, Formula, and Vote. We dynamically inspect the board's column schema before migration and build a field-mapping table. Not all column types map directly to standard PM fields; formula outputs, vote counts, and location coordinates require custom field handling.

Subitems are Items nested beneath a parent Item. They are second-class citizens in monday.com: no bulk export endpoint, no subitem-specific API filter, and no native subitem-to-subitem dependency. We handle Subitems by querying each parent Item and expanding its subitem array, then writing them as flat Items with a parent reference field in the destination.

Users are the human actors in monday.com — assigned to Items, owning Boards, and invited to Workspaces. We map Users by email and preserve display name. Owner assignment on Items translates to Assignee fields in standard PM systems.

Teams are monday.com's grouping mechanism for users, used for team-based permission scoping and Workload views. We map Teams to their member list and preserve team membership as a group-assignee mapping in the destination.

The Dependency column links Items across Boards or within a Board as predecessor-successor pairs. monday.com's dependency model supports only column-based input (no DAG visualization), and the API returns dependency pairs as an array. We flatten these into explicit predecessor-successor relationship records and write them to the destination's dependency model.

Updates are threaded comments on Items. Each Update carries a body (HTML or plain text), author, timestamp, and optional reply-to ID. The API allows querying updates per Item. We preserve Update text, author, and timestamp. HTML formatting is stripped to plain text unless the destination supports rich-text bodies.

The File column and inline attachments on Items store file metadata — name, URL, uploader, and timestamp. We preserve file references as URL strings. Actual binary file download is out of scope for most migration scenarios; we flag which Items have attachments so the customer can handle file migration manually or via a separate file-transfer step.

Tags are a Labels column type in monday.com — free-text labels applied to Items. Tags have a name and optional color. We map Tags to the destination's label/tag field by name and preserve the color as a hex value in a custom field if the destination supports it.

Time Tracking is a column type that logs time entries against an Item. monday.com records duration per entry with a description and assignee. The API returns time entries as nested data under the Item. We extract time entries as separate records linked to the parent Item and preserve hours, assignee, and description.

Automations (trigger-action rules built with monday.com's Automation Center) and Integrations (third-party connections like Slack, Zoom, Salesforce) are configuration objects that do not export via API in a transferable format. We do not migrate automations or integrations — these must be rebuilt manually in the destination environment.

Views — Gantt, Calendar, Kanban, Chart, Map, and custom saved views — are display configurations tied to a Board. monday.com does not expose saved view definitions via API. We do not migrate views; users should expect to recreate their preferred view configurations in the destination tool.