monday.com CRM Data Pre-Populate New Project Boards

You just closed a deal in monday.com CRM. Client name: Acme Corporation. Event date: March 15, 2026. Venue: Downtown Convention Center. Contact: sarah@acmecorp.com.

Now you need all of that information on your new Project Overview board. So you open the deal, highlight the client name, copy it, switch to the new board, click into the Name column, paste. Repeat for date. Repeat for venue. Repeat for email. Repeat for…

5 minutes later, you’re done entering data you already entered once.

This is the CRM-to-project version of the data transfer between boards problem, a gap that creates busywork, introduces typos, and slows down every project kickoff. The information exists — it’s sitting right there in your CRM board — but monday.com has no ready-made automation to transfer it when you create new project boards; you’d have to build a multi-step workflow yourself.

CRM Data Should Pre-Populate New Project Boards

Here’s what teams need:

When a CRM deal moves to “Won” and a new project workspace is created, the deal data should automatically populate the new project boards:

• Client name from the Deal Name → Name column on Project Overview
• Contact email from the CRM Contact column → Email column on Overview
• Event date from CRM Date → Date column on Overview
• Venue/Location from CRM Location → Location on Overview
• Deal type (show type, project category, service tier) → Status or Dropdown column on Overview
• Deal value, budget, priority → Number columns

Without manual copy-pasting. Without opening two boards side-by-side. Without typos.

What monday.com offers:

The Workflow Builder’s “Create board from template” action creates a new board with your template’s structure (columns, groups, views) but none of the deal’s data. (monday.com Help Center) Later workflow steps can carry values over: Get item data reads the deal, Create item or Update item writes it, and Duplicate board can copy structure plus content. monday.com doesn’t explicitly document writing to a board created earlier in the same run, so test it before relying on it.

Even monday.com’s “Cross-board automations” (monday.com Help Center) — which can copy column values between boards — only work when the target board already exists. You can’t use them during board creation because the target board doesn’t exist yet.

The result: manual data entry after every board creation, or a workflow you build and test yourself.

What monday.com Users Are Saying

Thread: Create board from template in master board and link items — June 2023

“I have a master board, low level boards setup created. In the master board, I’m using the ‘create board from template’ automation to create the low level board when a status on an item changes in the master board.” — wesoos (Wessel Oosthuizen)

The user is trying to connect the CRM board to the newly created project board and transfer data. monday.com staff asked clarifying questions but provided no solution.

Thread: Is it possible to automatically create and connect Items to a Board created from a template — November 2023 – August 2024

“how can we connect board automatically if the board is created from a template?” — Maayango, December 28, 2023

“Did you ever get an answer to your question above that worked?” — tkthieme, August 11, 2024

monday.com staff (BiancaT) suggested a mirror status column workaround but acknowledged no native solution exists for creating boards from templates AND automatically connecting/populating items.

Thread: Automation when creating new board from template — April 2022

“I’ve created a board template with tasks already pre-populated. The dependencies between tasks as far as due dates is already setup.” — pbeaudry (Phil), April 26, 2022

“I am not sure the dependencies will get triggered in that scenario.” — basdebruin, April 2022

Even within a single board, dependencies and due dates don’t auto-adjust when boards are created from templates. Cross-board data transfer is even further out of reach.

Official monday.com documentation confirms (monday.com Help Center):

Cross-board “create item” automations can map columns between boards — but both boards must already exist. You can’t map columns from a CRM board to a board that doesn’t exist yet.

The documentation lists Dependency, Link to Item and Time Tracking as the column types that can’t be mapped; Dropdown is excluded only from match automations.

How to Pre-Populate Project Boards in monday.com

There are three native routes, from the most built-in to the most flexible.

Option 1: One Workflow That Creates the Board and Fills It

monday.com’s own example creates a new board from a template when a status changes, then creates a new item using the item ID from the first step. Get item data can add a previous step’s information to an item on a completely different board, and Update item writes several column values in one block (monday.com Help Center). Standard accounts can publish 3 active workflows, Pro 20 and Enterprise 250 (monday.com Help Center).

Option 2: A Cross-Board Automation into a Shared Overview Board

If every project reports to one Project Overview board that already exists, a cross-board automation such as “When status changes to Won, create an item in Project Overview” can map deal columns into it. The columns must exist on both boards, and the updates section doesn’t carry over when an automation creates a new item (monday.com Help Center). More on these limits in monday.com cross-board automation limitations and our wider monday.com automations guide.

Option 3: Write the Values with the API

A developer, or an integration platform like Make.com or Zapier, can read the deal and create the project item with its column values in one create_item call. Each column type takes its own format, shown in the table below.

Column Types and Their API Formats

If a status or dropdown label doesn’t exist on the target board, create_labels_if_missing: true creates it; that needs permission to change the board structure (monday.com developer docs).

Columns that need extra care:

• Dependency, Link to Item, Time Tracking — cross-board automations can’t map them; in workflows, Dependency can be filled with the Create item and Change column value blocks
• Mirror — workflows can use the mirror column’s text value in a step
• Files — workflows can copy files from one item to another

Example: Event Management

CRM Deal Board has these columns:

• Deal Name: “Smith Wedding”
• Client Email: jenny@smith.com
• Event Date: June 20, 2026
• Venue: Riverside Pavilion
• Event Type: “Wedding” (Status column)
• Guest Count: 150 (Number column)

When deal moves to “Won”:

1. A workflow creates the “Smith Wedding” project board from your template
2. On the Event Overview board, a new item is created:

• Item Name: “Smith Wedding”
• Client Email: jenny@smith.com
• Date: June 20, 2026
• Venue: Riverside Pavilion (Text column)
• Event Type: “Wedding” (Status label)
• Guest Count: 150

No copy-pasting. To create a whole project folder from the deal, see auto-creating a project folder from a CRM trigger.

The project manager opens the new Event Overview board and sees all the client details already filled in, pulled directly from the CRM deal.

Column Mapping Configuration

You set the column mapping once, in the workflow’s Create item block or in the cross-board automation. A mapping looks like this:

CRM Board → Project Overview Board:

• CRM “Deal Name” → Overview “Event Name” (text)
• CRM “Client Email” → Overview “Contact Email” (email)
• CRM “Event Date” → Overview “Date” (date)
• CRM “Venue” → Overview “Location” (text)
• CRM “Event Type” → Overview “Type” (status)
• CRM “Guest Count” → Overview “Headcount” (number)

You can map as many or as few columns as needed. Once configured, every new project uses the same mapping.

Limitations You Should Know

Writing to a board created in the same run needs testing. monday.com’s example shows a workflow creating a board and then an item, but test your own column mapping on a sample deal first.

Cross-board automations need a board that already exists. Use them for a shared Overview board, not for boards a workflow is about to create. Templates bring two more traps: some custom automations don’t carry over to duplicated boards, and workarounds built on templates are exposed to managed template editor changes that break workarounds.

Some columns don’t map. Cross-board automations can’t map Dependency, Link to Item or Time Tracking columns.

Status labels must exist or be creatable. If your CRM has a status label “VIP Client” that your project board lacks, add it to the template, or let the API create it with create_labels_if_missing, which needs permission to change the board structure.

Wondering whether BoardBridge fits your CRM-to-project handoff? Ask us, or have our monday.com customization team build the workflow with you.

Frequently Asked Questions