> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sameitem.com/llms.txt
> Use this file to discover all available pages before exploring further.

# monday.com Mirror Column Limitations: Why It Isn't a Real Column

> Mirrored columns in monday.com are read-only references, so views, automations, forms, and integrations often can't use them. Here is exactly what breaks and what to do instead.

## The short answer

A mirror column is a **live window into another board's item, not a real column on your board**. monday.com treats it as a read-only reference, which is why a mirrored status column can't do the things a normal status column can. That's by design, and for light cross-board reference it's fine. The problems start when you try to run a workflow on mirrored values.

## What exactly doesn't work with mirrored columns

* **Views and grouping** — a mirrored status column is not recognized as a real status column, so Kanban lanes, grouping, and some filters won't treat it like one.
* **Automations** — most automation recipes can't trigger on or write to mirrored values.
* **Forms** — mirrored columns can't be used as form fields.
* **Formulas and integrations** — many can't read mirrored values reliably.
* **Dashboards** — several widgets ignore mirrored columns or handle them inconsistently.
* **Performance at scale** — long chains of Connect Boards + Mirror columns get slow and hard to maintain as boards and teams grow.

If you've hit one of these, you're not misconfiguring anything. The mirror system is a *display* mechanism.

## When mirror columns are the right tool

Use native mirrors when you only need to **see** a handful of fields from another board — for example, showing a deal value from the CRM board on a delivery item. They're built in, free, and simpler than any app. Don't replace them where they work.

## What to do when you need real columns on both boards

When the workflow itself needs to live on two boards — real statuses you can build views on, automations that fire, one updates thread — the item has to actually exist on both boards. That's what [Same Item Multiple Boards](https://monday.com/marketplace/10000363) does: the same item lives on every board you share it to, and every column on it is a real, native column.

* Build any view or automation on it — monday sees a normal column, because it is one.
* Statuses, dates, people, numbers, and text stay in sync across all boards ([supported column types](/columns/supported-columns)).
* [Updates and comments](/features/updates-sync) are one shared thread.
* Mirror and formula columns can still be used *alongside* it — see [how SIMB works with Connected Boards](/features/connected-boards) and [formula columns](/columns/formula-column).

Start with the [pillar guide: how to make an item live on multiple boards](/guides/item-on-multiple-boards) for the full comparison of all four approaches.

## FAQ

### Why did monday.com build mirrors as read-only?

A mirrored value belongs to the source board's item. Making it writable everywhere would effectively require one item to live on multiple boards — which is exactly the capability monday has kept off its roadmap and left to marketplace apps.

### My mirrored columns got slow as we grew. Is that normal?

Yes, it's a common report on large accounts: multi-hop mirror chains take time to resolve. Teams that grew out of mirrors typically move the shared work to synced items and keep mirrors for light reference only.

### Can I convert a mirror setup to synced items?

There's no one-click conversion, but the migration is straightforward: share the source items to the boards that currently mirror them ([in bulk](/features/batch-actions)), confirm column names match ([column mapping](/features/column-mapping)), then remove the mirror columns you no longer need.