# monday.com Data Transfer Between Boards Automation

Canonical: https://www.taskrhino.ca/en-us/monday-com-automations/data-transfer-between-boards/

> Learn how to transfer data between monday.com boards with automation. Solve column mapping issues for cross-board data syncing with proper formatting.

Published: 2026-02-26  
Updated: 2026-10-29  
Author: Rakesh Patel  
Categories: BoardBridge

**Key takeaways**

-   Native cross-board automations can map every column type except Dependency, Link to Item and Time Tracking, and each column must exist on both boards.
-   Each mapped Status, Tag, People or Dropdown column counts as an extra automation action.
-   monday.com doesn’t document whether cross-board automations match status labels by text or by ID, so test boards whose labels differ.
-   To write several columns into an existing item, use the workflow builder’s Find matching item and Update item blocks.
-   In the monday.com API, each column type takes its own JSON format, and status and dropdown values can be written by label text.

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](https://www.taskrhino.ca/en-us/monday-com-automations/button-update-status-another-board/))

**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](https://www.taskrhino.ca/en-us/monday-com-automations/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](https://support.monday.com/hc/en-us/articles/360011393900-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.

Definition

**Label ID:** the internal number monday.com gives each status or dropdown label on a board; the same label text has different IDs on different boards.

**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](https://community.monday.com/t/how-to-copy-status-columns-with-labels-to-another-existing-board/65707))

### 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](https://www.taskrhino.ca/en-us/monday-com-automations/cross-board-limitations/); our [monday.com automations guide](https://www.taskrhino.ca/en-us/monday-com-automations/) covers the rest.

**Plan Your Cross-Board Data Flow**

Get help mapping columns between your CRM and project boards.

[Book a Free Call](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone)

## How to Transfer Data Between Boards Natively

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

1.  **Prepare the target board:** add every column you want filled, with a compatible column type (see the mapping table in the setup guide below).
2.  **Set the trigger:** on the CRM board, start a cross-board automation such as “When status changes to Won”.
3.  **Create the item:** choose “create an item in board” and pick the Event Overview board.
4.  **Map the columns:** map each source column to its target; Dependency, Link to Item and Time Tracking can’t be mapped.
5.  **Test:** move a test deal to Won and check every value on the new item, especially status and dropdown labels.

### 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](https://www.taskrhino.ca/en-us/contact-us/).

**Need help structuring your monday.com boards?**

Book a free 30-minute call with a certified monday.com partner.

[Book a Free Call](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone)

## Column Value Formats in the monday.com API

TaskRhino tip

Numeric status labels such as “2023” are read as index numbers, so write those by index instead of by label.

| Column Type | API Format | Example Value |
| --- | --- | --- |
| **Text** | Plain string | `"Smith Wedding"` |
| **Long Text** | `{text: "..."}` (keeps line breaks) | `{text: "Outdoor ceremony, live band preferred"}` |
| **Email** | `{email: "addr", text: "display text"}` | `{email: "bride@smith.com", text: "bride@smith.com"}` |
| **Phone** | `{phone: "number", countryShortName: "code"}` | `{phone: "+15551234567", countryShortName: "US"}` |
| **Number** | The number as a string | `"50000"` |
| **Date** | `{date: "YYYY-MM-DD"}`, optional `time` in UTC | `{date: "2026-06-15"}` |
| **Dropdown** | `{labels: ["text"]}` or `{ids: [1, 2]}` | `{labels: ["Show + Teebox"]}` |
| **Status** | `{label: "text"}` or `{index: 1}` | `{label: "High"}` |
| **Checkbox** | `{checked: "true"}` | `{checked: "true"}` |
| **Location** | `{lat: "...", lng: "...", address: "text"}` | `{lat: "36.1627", lng: "-86.7816", address: "Nashville, TN"}` |

## 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

| Feature | monday.com Native Cross-Board Automations | Your Own API Integration |
| --- | --- | --- |
| **Column types supported** | All except Dependency, Link to Item and Time Tracking (column must exist on both boards) | Any writable column, in its JSON format |
| **Status/dropdown mapping** | Not documented (test it) | By label text (documented) |
| **Email column formatting** | Email is a supported mapping type | `{email, text}` |
| **Phone column formatting** | Phone is a supported mapping type | `{phone, countryShortName}` |
| **Checkbox support** | Not listed as unsupported | `{checked: "true"}` |
| **Location column support** | Not listed as unsupported; users report it not copying | `{lat, lng, address}` |
| **Long text preservation** | Not documented | `{text}` keeps line breaks |
| **Number formatting** | ✓ Yes | Number sent as a string |
| **Date timezone handling** | Limited | Date only, or a time in UTC |
| **Batch column updates** | Workflow Update item sets several columns in one block | `change_multiple_column_values` sets several in one call |
| **Works after board duplication** | Not documented for cross-board references | Your code chooses the target board |

## 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:

| CRM Column | Event Overview Column | Column Type |
| --- | --- | --- |
| Client Name | Client Name | Text |
| Event Date | Event Date | Date |
| Venue City | Venue | Location |
| Client Email | Contact Email | Email |
| Client Phone | Contact Phone | Phone |
| Event Type | Event Type | Dropdown |
| Priority | Priority | Status |
| Budget | Budget | Number |
| Notes | Notes | Long Text |
| Contract Signed | Contract Status | Checkbox |

### 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](https://www.taskrhino.ca/en-us/monday-com-automations/dont-carry-over-duplicated-boards/)).

Need the data flow built for you? Our [monday.com customization](https://www.taskrhino.ca/en-us/monday-com-customization/) team can set up the automations, workflows or an API integration.

**Need Help With Your monday.com Setup?**

TaskRhino has implemented monday.com for 110+ teams. Get a free consultation.

[Schedule Free Consultation](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone)

## Frequently Asked Questions

**Can I map columns with different names between boards?**

### 

Yes. Mapping pairs a target column with the source column you pick, so “Client Name” can fill “Company Name”. What matters is that a column of a compatible type exists on both boards.

**What if the source board has a column the target board doesn’t have?**

### 

It can’t be mapped: “the column you want to map must exist on both boards.” Add the column to the target board first, then map it.

**Can I transform data during transfer (add a prefix, concatenate fields)?**

### 

monday.com doesn’t document prefixes or concatenation in cross-board column mapping, which copies values as they are. For transformed values, build them in your own API integration, or [ask us](https://www.taskrhino.ca/en-us/contact-us/).

**Does data transfer work when duplicating boards?**

### 

Duplicating a board with “Structure & items” copies its items, column values and the recipes that are turned on. Connect Boards and Mirror settings aren’t carried over, and monday.com doesn’t document what happens to cross-board targets, so check each one (see [cross-board recipes that break on duplication](https://www.taskrhino.ca/en-us/monday-com-automations/dont-carry-over-duplicated-boards/)).

**What’s the fastest way to transfer 50+ columns at once?**

### 

Batch updates. In the API, `change_multiple_column_values` sets several columns on an item in one call; in the workflow builder, one Update item block sets several columns.

**Can I transfer data from a lookup/formula column?**

### 

Formula and mirror columns are read-only: you can read their values with the API and write them as text to a text column on the target board, but nothing can be written to them.

**Do I need to wait for the first item to create before transferring data to it?**

### 

No. A cross-board automation creates the item and fills the mapped columns in the same action, and the API’s create\_item takes column values when it creates the item.

**What happens if an email column has an invalid address?**

### 

monday.com doesn’t document validation when an email value is copied, so check addresses on the source board. If an automation later sends to an invalid address, the run fails and Run history shows it.

**Can I preview what data will transfer before running the automation?**

### 

monday.com doesn’t offer a preview of a cross-board mapping. Test with one item, then check the new item and the automation’s Run history (see [monday.com’s missing dry-run mode](https://www.taskrhino.ca/en-us/monday-com-automations/dry-run/)).