What is the difference between Matter and Zigbee?

Zigbee is a full network stack — radio, mesh networking and an application layer — built on the IEEE 802.15.4 radio. Matter is an application-layer standard that runs on top of existing IP networks such as Wi-Fi and Thread. They are not two competing versions of the same thing; Matter standardises what devices say to each other, while Zigbee is one of the underlying ways devices can connect.

Should my brand migrate from Zigbee to Matter?

Migrate when a concrete trigger fires, not because Matter is in the news. The three triggers that usually justify the move are: you are launching a new product line with no legacy installed base to serve, a retail or ecosystem partner now requires Matter, or you want to sell one SKU into multiple ecosystems without building a separate integration for each.

Can a product support both Matter and Zigbee?

Yes, though it is a real engineering decision rather than a free option. Some radios are multi-protocol and can run both stacks, and a bridge can expose an existing Zigbee network as Matter accessories. Whether to build a dual-radio or a bridge depends on your power budget, your BOM and whether you are serving an existing installed base or starting a new line.

What does an ODM factory actually do in a Matter migration?

The factory does the work a brand cannot outsource to a protocol choice: schematic and PCB design, prototyping and board bring-up, firmware, certification cooperation and mass production. In a migration the factory keeps the enclosure and power architecture where they make sense, swaps the connectivity layer for a standard CSA-certified Matter connectivity module, and carries the certification in its own name for the finished product.

Matter vs Zigbee for ODM Brands: How to Decide the Migration

Q: Does Matter replace Zigbee?

No. Matter and Zigbee coexist rather than replace each other. Zigbee keeps a large installed base and a mature, low-cost ecosystem for battery devices, while Matter is becoming the consensus application layer for new products. A common pattern is to run Zigbee as the field bus behind a bridge that exposes the devices as Matter accessories to the major ecosystems.

What Matter and Zigbee actually are

Zigbee is a full network stack — radio, mesh networking and an application layer — built on the IEEE 802.15.4 radio. It is mature, low-cost, battery-friendly and has a large installed base of devices and hubs. Matter is an application-layer standard that runs on top of existing IP networks such as Wi-Fi and Thread. It defines a common language for devices across ecosystems, so one Matter product works with the major smart home platforms without a separate integration for each.

The key insight for a brand is that they are not two competing versions of the same thing. Matter standardises what devices say to each other; Zigbee is one of the underlying ways devices can connect. That is why the question "Matter or Zigbee?" is often the wrong one — the honest answer for many product lines is "both, at different layers, at different times."

Where they coexist rather than compete

Matter and Zigbee coexist rather than replace each other. Zigbee remains the pragmatic choice for a battery sensor line with a decade of proven deployments and cheap silicon, and it keeps the largest installed base. Matter is becoming the consensus application layer for new products, driven by the simple fact that every major platform now speaks it.

A very common real-world pattern is to keep Zigbee as the field bus — the low-power mesh doing the actual sensing — and expose it through a bridge so the devices appear as Matter accessories in Apple, Google or Amazon ecosystems. That pattern is why many brands never make an all-or-nothing migration at all: they add Matter at the edge where it buys them interoperability, and leave Zigbee where it already works.

The three triggers that justify a migration

Migrate when a concrete trigger fires, not because Matter is in the news. In our experience three triggers do most of the justifying.

A new product line with no legacy to serve. If you are launching a fresh SKU with no existing hub or installed base, Matter removes the need to build a separate integration for each ecosystem — which is real savings, not ideology.
A retail or ecosystem partner now requires it. When a channel or a platform makes Matter a condition of listing, the decision is made for you, and the only question left is how to do it efficiently.
One SKU across many ecosystems. If your growth depends on selling the same device into several platforms at once, Matter's single certification buys you that reach — a genuine BOM-to-revenue argument rather than a trend argument.

If none of the three is present, the honest advice is usually to wait. Replacing a working Zigbee mesh to "be on Matter" spends budget on a standard that is not yet solving a problem for that specific line.

What a migration actually is, mechanically

A Matter migration is a hardware re-scope, not a firmware switch. The enclosure, the sensor element, the battery and the power architecture can largely carry over — the enclosure is the part your customers already recognise. What changes is the connectivity layer: the Zigbee radio is replaced by a standard CSA-certified Matter connectivity module, and the firmware is re-targeted to the Matter stack. The certification is then taken for the finished product in the factory's own name, not as a re-badge of somebody else's.

This is why the migration decision belongs in the same conversation as the BOM and the certification budget. The module choice sets the flash and RAM floor, the secure element and the per-unit cost — exactly the drivers we unpack in our article on Matter certification cost and timeline. A migration is a product decision with a price tag, not a protocol preference.

Dual-protocol: when "both" is the real answer

For some lines the correct answer is to support both. A multi-protocol radio can run both stacks, or a bridge can expose an existing Zigbee network as Matter accessories. It is a genuine option, but it is not free: it adds to the power budget, the BOM and the test surface. Decide it on the same logic as everything else — is there a concrete reason, this product, this market — rather than as a hedge against a future that may not arrive.

How the factory owns the decision

Shenan Yangguang runs the whole chain ourselves — schematic and PCB design, prototyping and board bring-up, firmware R&D, certification cooperation and mass production — so a migration is executed by the people who understand both protocols, not handed between vendors. We keep the enclosure and power architecture where they make sense, swap the connectivity layer for a standard CSA-certified Matter connectivity module, and carry the certification in our own name. The right answer for your line, Zigbee, Matter or both, is one we work out against your specific triggers — not against a trend.