Connect Boards vs Mirror Columns vs a Real Sync on monday.com: Which One You Actually Need

2. Connect Boards: the link, not the data

The Connect Boards column creates a relationship between items, and the two-way connection option shows that link on both boards (Connect Boards docs). It is the foundation for everything else on this list, including a custom sync. What it does not do is change any values: connecting two items does not make their statuses, dates, or owners match.

Limits to plan around: a board can connect to 1, 5, 20, or 60 other boards on Basic, Standard, Pro, and Enterprise (mondayDB 2.0); a board holds up to 10,000 linked items (100,000 on Enterprise); one cell holds up to 750 links (linkage limits). A two-way connection also fails on boards where you do not have edit rights.

At enterprise scale, more limits stack up: items per board are capped at 10,000, or 100,000 on Enterprise (board item limits); a board holds up to 60 Connect Boards columns; dashboards can include 1 to 50 connected boards depending on plan (developer limits); links are lost when items are moved by automation or a board is archived (moving items); and boards in two separate monday.com accounts cannot be connected. The full list is in monday.com Connect Boards and automation limits.

3. Mirror columns: a window, with blind spots

A Mirror column shows a column from the connected items, and editing a mirrored cell changes the source (Mirror column docs). That is often enough. The limits show up as soon as a board depends on mirrors:

• Mirrored data only shows for people with access to every board in the chain; one missing permission leaves the column blank (permissions and connected data).
• Mirrors are not real columns: formulas can only use mirrored Numbers, grouping works only with one linked item, and mirrors do not appear in My Work (formula docs, My Work).
• Item names and the Updates section cannot be mirrored, so conversations stay on one board.
• You see the source board's labels as they are. A client board cannot show "In review" for an internal "Waiting on QA".
• Mirrors only go two levels deep, and column summaries are not supported.
• Only some status-change recipes can be triggered by a mirrored column (cross-board automations), and users report that mirrored and connected data is often not available to map in automations and integrations (community thread).
• Users report that sorting and filtering by a mirror stop working well once it pulls from more than one board (community thread), and developers report slower API reads on boards with many mirrors.

4. Cross-board recipes: a copy at one moment

Recipes such as "when an item is created, create an item in another board and connect them" are excellent for one-way hand-offs (high- and low-level boards). They copy data when they fire; they do not keep it aligned afterwards. Subitems behave the same way: values copied from a parent when a subitem is created have no ongoing link (subitems docs).

Building a two-way sync out of recipes means mirrored pairs of recipes that update each other, and monday.com only warns before you save a recipe that can loop (why automations get deactivated). Every bounce also uses your monthly action quota; see monday.com automation limits.

5. Marketplace sync apps

Because one item on many boards is not on monday.com's roadmap (feature request), several marketplace apps fill the gap. They are a sensible first step when the same item, with the same values, should appear on a few boards. Check three things before you commit: whether it can map different labels between boards, whether it carries updates and files, and what it does and tells you when a sync fails.

6. A custom sync

A custom sync listens to webhooks on each board, uses Connect Boards to know which items are twins, and writes changes through the GraphQL API with whatever rules the business needs: label mappings, cascading renames and deletions, updates with mentions, group moves, roll-ups, and a scheduled reconciliation that catches anything a webhook missed. Because values are written into each board's own columns, they sort, filter, group, and trigger automations like any other column, and the sync is not bound by linkage limits or account boundaries. It costs more up front and is the option that fits when the boards are genuinely different or there are too many to link. I explain the design in two-way sync between monday.com boards.

7. How to choose

1. Do you only need to see a few values from another board? Connect Boards and a Mirror column.
2. Does work move one way, once? A cross-board recipe.
3. Should the same item, identical, appear on a few boards? Try a marketplace app.
4. Do the boards use different labels, need updates to flow both ways, cascade renames and deletions, or roll up many boards, and must failures be noticed? A custom sync.
5. Are you near Connect Boards limits, losing links when items move, or need boards in another account to stay in step? A custom sync.

Most accounts end up with a mix: mirrors for reading, recipes for hand-offs, and one custom sync for the boards that matter most. That is how the agency in my board sync case study runs: client and internal boards stay in sync both ways, and project boards are realigned with the task boards every 6 hours.

Frequently asked questions