top of page

How to connect boards in monday.com without duplicating data

  • Jun 29
  • 6 min read
connecting monday.com boards

Picture this: your sales team closes a deal. The project team opens its delivery board two weeks later and sees the wrong client contact because someone typed the name manually when the project started. Sales updated the client record. Delivery did not get the update.


This often looks like a communication problem. It can feel like someone missed a step. In many monday.com setups, the real problem is structural: the same data is being stored in too many places.


Connected boards solve this by letting one board reference data from another board. The information still has one home, but the teams who need it can see it in the context of their work.


Quick answer: What are monday.com connected boards?


Connected boards in monday.com let items on one board link to items on another board without copying data. A mirror column then shows selected information from the linked item on your current board. When data lives in one source board and gets referenced elsewhere, teams spend less time re-entering information and reports become easier to trust.


How do connected boards work in monday.com?


Connected boards work by creating a relationship between items on two different boards. Instead of copying information from one board into another, monday.com uses a Connect Boards column to point one item to a related item elsewhere.


For example, a project on a Delivery board can connect to a client record on a Contacts board. The client details still live on the Contacts board, but the Delivery board can reference that client record whenever the team needs the context.

Two column types make this possible:


  • Connect Boards column: creates the link between related items on different boards.

  • Mirror column: shows selected information from the connected item, such as client name, email, company, or account owner.


The Connect Boards column creates the relationship. The Mirror column makes the related information visible without creating a second copy of the data.


Why duplicated data in monday.com causes problems


Most teams build their first monday.com boards like standalone spreadsheets. Every board holds all of its own information. A project board has a client name. A sales board has a client name. A billing board has a client name.


That can work for a while. Then a client changes their company name, an email address gets updated, or a contact leaves the organization. Now someone has to remember every place that information appears.


The issue is not the team. The board structure gave the team too many copies to maintain. Once reports and automations depend on those copies, the system gets harder to trust.


Connected boards force a clearer decision: where does this information actually live?


The Magic Button Labs philosophy on boards


At Magic Button Labs, we use a two-board model to keep monday.com systems clean and scalable: workflow boards and master data boards.


Workflow boards track work in motion, like leads, opportunities, projects, tasks, or requests. Master data boards hold the stable records those workflows depend on, like clients, contacts, organizations, products, or locations.


The goal is simple: workflow boards should reference master data, not recreate it. A Delivery board can connect to a client record. A Sales board can connect to an organization record. That way, each workflow gets the context it needs without becoming another source of truth.


What a mirror column in monday.com does


A mirror column shows data from a connected item on another board. If your Delivery board is connected to a Contacts board, you can mirror the client email, organization, account owner, or other fields into the Delivery board.


The important part: a mirror column is not a second copy of the data. It is a window into the source board.


That also means mirror columns are not usually the right place to edit information. If the client email changes, update it on the Contacts board. Every mirror column that displays that email will reflect the current version.


Our rule is simple: mirror for visibility, not duplication.

If the Delivery team needs to see the client email, mirror it. If the Delivery team needs to own and edit a delivery-specific date, use a local column on the Delivery board.


What improves when monday.com boards are connected?

purpose of connected boards in monday.com

Team handoffs carry the right context forward

When a deal becomes a project, the delivery team should not have to rebuild the context sales already captured. Connected boards help carry the client relationship, project details, key dates, and other important information into the next stage of work. The handoff becomes cleaner because the system is passing context forward, not asking another team to recreate it.


Reporting becomes easier to trust

Reporting gets cleaner when important information lives in one master board instead of being copied across several boards. If client data, organization data, or project details are stored in one source of truth, dashboard numbers are less likely to disagree. Everyone is working from the same record, which makes reporting more consistent across teams.


Automations can act on relationships between records

Automations become easier to reason through when the right records are connected. Instead of relying on users to manually copy information from one board to another, automations can respond to the relationship between connected items. That makes it easier to support handoffs, updates, and next steps without adding extra manual work.


Teams spend less time re-entering information

Connected boards reduce the amount of duplicate data entry happening across the system. When information is referenced from the source board, teams do not need to type the same client name, company, contact, or project detail again and again. That saves time and lowers the risk of small inconsistencies turning into bigger reporting or workflow issues.


A quick test: do your boards need connecting?


Ask these three questions:

  • Does your team type the same client, company, contact, product, or location into more than one board?

  • When that information changes, does someone have to update it in multiple places?

  • Do reports show different numbers depending on which board you pull from?


If the answer is yes, the system may be storing information that should be referenced instead.


You do not need to connect everything. But repeated reference data is a strong sign that a master data board and connected board structure would help.


6 ways to prepare your data before connecting boards

Connected boards make good data more useful and messy data more visible. Before you connect anything, make sure the board everyone will reference is clean, consistent, and ready to become the source of truth.


#1: Clean your master data board

Start with the board that will hold the source records, such as clients, contacts, organizations, products, or locations. This helps because every connected workflow will pull from this board, so the source needs to be reliable before it powers the rest of the system.


#2: Remove duplicate records

Look for repeated clients, companies, contacts, or other records that appear more than once. This helps prevent teams from connecting work to the wrong version of the same record.


#3: Standardize naming

Choose one naming format for records and apply it consistently. This helps users search, filter, report, and connect records without guessing which version of a name is correct.


#4: Fill in the fields that matter

Make sure the important columns are complete, especially fields used for reporting, filtering, automations, and handoffs. This helps connected boards surface useful context instead of empty or incomplete information.


#5: Decide which board owns each type of data

Clarify where each kind of information should live. This helps prevent teams from editing the same data in multiple places and keeps the source of truth clear.


#6: Protect data quality at intake

Use required form fields, standardized dropdowns, and clear input rules when new records enter the system. This helps the team capture clean data the first time instead of fixing messy records later.


Frequently asked questions


What is the difference between a connected board and a mirror column in monday.com?

A connected board is created when one board links to another through a Connect Boards column. A mirror column displays information from the connected record. The connection creates the relationship. The mirror column shows useful details from that relationship.


Can I connect more than two boards in monday.com?

Yes. A single board can connect to multiple boards using separate Connect Boards columns. For example, a project board might connect to a Clients board, a Team Members board, and a Services board.


Do I need to rebuild my boards to use connected boards?

Not always. If your boards are already clean and the source of truth is clear, you may be able to add connections gradually. If the same data lives across many boards with different versions, start by creating or cleaning a master data board first.


What is a master data board in monday.com?

A master data board holds stable records that multiple workflows need to reference. Common examples include clients, contacts, organizations, locations, products, or services. The master data board is where the record lives. Workflow boards are where the work happens.


Turn monday.com into a system your team can trust 


Connected boards are one of the most important structural decisions in a monday.com build. They help teams stop copying information, reduce manual updates, and create a more reliable source of truth across boards.

The key is not connecting boards for the sake of connecting boards. The key is deciding where each type of data should live, then letting every workflow reference that source.


That kind of decision is what turns monday.com from a collection of boards into a system people can trust. It is also one of the core concepts we teach in the Builder Blueprint Series. If your team is running into duplicate data, unreliable reports, or messy handoffs, the next step is a conversation about the structure underneath the work.



 
 

© 2025 by Magic Button Labs, LLC. Powered and secured by Wix

bottom of page