monday.com Data Transfer Between Boards Automation

When you create a new project from a CRM deal, you expect client data to flow automatically from the CRM board to your project boards. But monday.com’s native cross-board automations can’t map every column type, and getting several values onto an existing item takes extra setup.

The monday.com limitation: Native cross-board automations can map columns between boards, but:

• Dependency, Link to Item and Time Tracking columns can’t be mapped, and the column must exist on both boards
• Each mapped Status, Tag, People or Dropdown column counts as an extra automation action
• Users report Location columns not copying
• Writing several columns to an existing item on another board takes the workflow builder’s Find matching item and Update item blocks (to change only a status there from a button, see updating a status on another board with a button click)

What you actually need:

• Support for all major column types, each in its correct format
• Status/dropdown mapping by text (not hardcoded IDs that differ between boards)
• Proper formatting for dates, emails, phones, locations
• Batch column updates (all columns in one API call, not one-at-a-time)
• Dynamic value transformation (concatenate fields, format timestamps, map values)
• Pre-fill form fields with existing data (no re-entry required)

This is part of the broader monday.com column copying between boards workflow.

The monday.com Cross-Board Column Mapping Problem

What monday.com’s API Supports (Official Documentation)

From monday.com’s official support article on cross-board automations:

“In order to map across boards, the column you want to map must exist on both boards.”

This means:

• Both boards need a column with the same (or compatible) column type
• You can map text → text, date → date, number → number, status → status

(Source: monday.com Support – Cross-board automations)

The Label ID Problem (Community Evidence)

Thread: “How to copy status columns with labels to another existing board” (September 2023)

User Marco234, September 12, 2023:

“Just a simple solution to select one or more columns from a board and copy them to another existing board.”

The thread is about copying status columns between boards, not about automation mapping.

monday.com’s internal architecture: Each status or dropdown column on each board has unique label IDs assigned by monday.com. Even if two boards have status columns with identical label text (“Pending”, “Confirmed”, “Canceled”), the internal IDs are different.

What isn’t documented: monday.com doesn’t say whether cross-board automations match status values by label text or by ID. If labels differ between boards, test the mapping before relying on it.

(Source: monday.com Community Forum)

What Column Types monday.com’s Native Automations Support

monday.com’s official article lists only three column types that can’t be mapped by native cross-board automations (“When status changes, create item on another board and map columns”): Dependency, Link to Item and Time Tracking. The column must exist on both boards. Its list of types for match templates includes Item name, People, Date, Status, Numbers, Timeline, Link, Phone, Email, Text, Priority and Label. Mirror and Formula columns are computed, so nothing can be written to them.

Key gap: monday.com doesn’t document how status and dropdown labels are matched across boards, so mappings between boards with different labels need testing. This is one of many monday.com cross-board automation limitations; our monday.com automations guide covers the rest.

How to Transfer Data Between Boards Natively

Option 1: A Cross-Board Automation That Creates the Item

Option 2: The Workflow Builder for Existing Items

When the target item already exists, the workflow builder’s Find matching item block locates it by a column value, and one Update item block sets several columns at once.

Option 3: Your Own Integration with the API

If you write values with the monday.com API (change_multiple_column_values sets several columns in one call), each column type takes its own JSON format. Status and dropdown values can be written by label text, and monday.com matches the label on the target board.

Wondering whether BoardBridge fits your data flow? Ask us.

Column Value Formats in the monday.com API

Text-Based Status/Dropdown Mapping (Solves Label ID Mismatch)

The Problem

monday.com assigns unique label IDs to status and dropdown values on each board. Even if two boards have identically named labels, the IDs differ.

Example:

• CRM Board status column “Priority” has labels:
• “High” → internal ID label_abc123
• “Medium” → internal ID label_def456
• “Low” → internal ID label_ghi789
• Event Overview status column “Priority” has labels:
• “High” → internal ID label_xyz987
• “Medium” → internal ID label_uvw654
• “Low” → internal ID label_rst321

monday.com’s native cross-board automation: monday.com doesn’t document whether it matches by label text or by ID, so test it with your own boards.

Writing Labels by Text (API)

Instead of hardcoding label IDs, an API integration can send status and dropdown values as text labels and let monday.com resolve them to the correct IDs on the target board.

// Format sent to the monday.com API
{
  "column_id": "color_xyz987",
  "value": "{\"label\": \"High\"}"
}

What monday.com does:

• Receives the text label “High”
• Looks up which label on the target board (Event Overview) has the text “High”
• Writes the value with that board’s label (with create_labels_if_missing: true, it adds a missing label instead of returning an error)

Result: “High” on the CRM board maps to “High” on the Event Overview board, even though the internal IDs are different. It works on any board whose column has a label with the same text; numeric labels are the exception.

Native Automations vs the API: Side-by-Side Comparison

How to Set Up CRM → Project Board Data Transfer

Here’s a step-by-step guide to setting up automated data transfer:

Step 1: Map Your Columns

List which CRM columns should map to which Event Overview columns:

Step 2: Build the Automation

On the CRM board, create a cross-board automation:

• Trigger: when status changes to “Won”
• Action: create an item in the Event Overview board
• Mapping: one source column per target column, as in the table above

Step 3: Test with One CRM Deal

Mark a test CRM deal as “Won.” Verify:

• The Event Overview item has every mapped column filled
• Text, dates, emails, phones, dropdowns, statuses and checkboxes arrive as expected
• No data loss or formatting errors

Step 4: Check Run History

Open the automation’s Run history to see how it ran and where it got stuck.

Step 5: Duplicate Boards and Verify

If you duplicate the Event Overview board for each project, the automation still targets the board it was built for, so repoint it to each new board and test again (see cross-board recipes that break on duplication).

Need the data flow built for you? Our monday.com customization team can set up the automations, workflows or an API integration.

Frequently Asked Questions