Cisco Meraki MV21 EoL: Migrate to the MV13 Indoor Camera

If you still have Cisco Meraki MV21 cameras (PID MV21-HW) watching lobbies, corridors, and stockrooms, the clock has effectively run out. The MV21 reaches its Last Day of Support on June 19, 2026. After that date Cisco delivers no firmware updates, no security fixes, and no TAC support or RMA hardware replacement for this model. The cameras keep streaming to the Meraki dashboard, which is precisely why first-generation MV hardware quietly survives in production years past the point it should have been retired. This guide explains what the end-of-life milestones actually mean for a camera you are still relying on, why the recommended Meraki MV13 is a genuine generational upgrade rather than a like-for-like swap, and how to plan a clean refresh.

What the Meraki MV21 actually was

The MV21 (MV21-HW) was a first-generation cloud-managed indoor dome camera, launched in Meraki's original MV line. Its defining idea was simplicity: every camera carried its own onboard solid-state storage and recorded locally, so there was no separate network video recorder (NVR), no DVR appliance, and no central storage array to size, license, or maintain. Management, retention policy, motion search, and live and historical viewing all happened in the Meraki dashboard. It was an HD-class fixed-focal dome powered over standard 802.3af PoE on a single Ethernet uplink, with on-camera video processing handling motion indexing so the dashboard could scrub footage quickly without pulling full streams to the cloud. For a 2016-era deployment that wanted serious video surveillance without a surveillance team, it was an elegant design. By today's expectations for resolution, on-device analytics, and storage headroom, it is a constrained platform.

Why acting now matters

The danger of an end-of-life camera is not that it stops recording. It is that it keeps recording while the support floor disappears underneath it. Three concrete exposures stack up the moment LDoS passes:

• No PSIRT security fixes. A cloud-managed camera is an internet-connected Linux device sitting on your network. When a new firmware or component vulnerability is disclosed, the MV21 will not receive a patched build. Any CVE that touches its frozen firmware is permanent, and an unpatched camera is a soft entry point onto the same VLAN as the rest of your video fleet.
• No TAC or RMA. A dead MV21 cannot be opened as a support case or swapped under warranty or contract. Your only recovery is a spare you stockpiled before LDoS or a gray-market unit of the same dead-end model, with no support behind it.
• Audit and compliance exposure. The frameworks that federal, DoD, SLED, and healthcare buyers operate under (FedRAMP, CMMC, HIPAA Security Rule, PCI DSS, and CISA directives) expect supported, patchable infrastructure on the network. An internet-facing camera that can no longer be patched is a finding waiting to happen, and 'the vendor stopped shipping fixes' is not a defensible remediation.

There is also a licensing trap unique to Meraki. Every MV camera requires an active Enterprise license to operate; the hardware is inseparable from its dashboard subscription. As MV21 licenses lapse against an end-of-support device, you are paying to manage hardware Cisco no longer stands behind. The cleaner economics are to roll that spend into current hardware that has a long support runway ahead of it.

What each milestone means in practice

• End of Sale (2019-06-19): the last day Cisco accepted new MV21 orders. Everything since has been consuming the support tail.
• End of Software Maintenance (not applicable): the MV21 has no separate software-maintenance milestone. Firmware is delivered automatically by the dashboard up to LDoS, then stops; there is no extended bug-fix window to lean on.
• Last Day of Support / LDoS (2026-06-19): the hard wall. No firmware, no security fixes, no TAC, no RMA. From this date the camera receives nothing.

The recommended replacement: Meraki MV13

Cisco names the Meraki MV13 (PID MV13-HW) as the current indoor successor, and the generational jump is the point. The MV13 keeps everything that made the MV line easy (no NVR, onboard storage, dashboard-native management, single-cable PoE install) while modernizing the parts that matter most for evidence quality and analytics:

• 4K-class sensor and optics. The MV13 captures dramatically higher resolution than the HD-era MV21, so you can digitally zoom into a face, a license plate, or a badge in recorded footage instead of squinting at a blur. Higher pixel density also lets one camera cover an area that previously needed two.
• Far larger onboard storage. The MV13 ships with substantially more solid-state capacity than the MV21, extending local retention without adding any external recorder, which keeps the NVR-free model intact while satisfying longer retention requirements common in healthcare and public-sector environments.
• Modern on-camera processor and analytics. A current SoC runs richer edge analytics (people detection, object and motion search, attention and occupancy analytics) on-device, so the dashboard stays responsive and bandwidth to the cloud stays low because raw video is not constantly leaving the building.
• Hardware encryption and a current security baseline. The MV13 enforces encryption of stored and in-transit video on supported, actively patched firmware, which is exactly the property the MV21 loses at LDoS.
• Same install footprint. Single Ethernet uplink with PoE and dashboard onboarding mean the physical swap is largely one-for-one; in many ceilings it is a mount, a cable, and a dashboard claim.

A practical migration plan

1. Assessment and inventory

Export an exact count of MV21-HW units from the dashboard with per-camera location, mount type, the switch port and PoE budget feeding each one, the network/VLAN they live on, current retention settings, and license expiry. Note any motion-alert zones, scheduled recording profiles, and integrations (alerts, API pulls, third-party VMS bridges) so nothing is lost in translation. Flag cameras that share a refresh window with other end-of-life MV models so you size one combined project rather than several.

2. License transition

MV21 licenses do not transfer to MV13 hardware; you are buying new per-camera Enterprise licenses for the replacements. Co-term the new licenses to your organization's existing Meraki license expiry where possible so the whole estate renews on one date. Provision the licenses in the dashboard before install day so each MV13 comes online fully licensed the moment it is claimed.

3. Config and feature parity

Recreate retention policies, motion-detection zones, recording schedules, alert recipients, and access-control roles on the MV13s before cutover. Take advantage of the higher resolution to revisit camera placement: an MV13 may cover sightlines that previously required two MV21s, so confirm new fields of view against your coverage map rather than blindly cloning the old layout.

4. Physical, power, and uplink check

Verify each feeding switch port supports the MV13's PoE class and that the switch's total PoE budget absorbs the new draw, especially where one switch powers many cameras plus phones or APs. Confirm cabling supports the camera's uplink and reuse the existing drop where possible. For ceiling and wall mounts, check that the MV13's mounting hardware fits the existing back box or bracket; most indoor dome refreshes reuse the cabling but may need a new mount adapter.

5. Phased cutover

Stage the swap by zone, not all at once. Replace cameras in one area, confirm footage is recording and analytics are populating in the dashboard, validate retention against requirements, then move on. Because MV is NVR-free, there is no central recorder to migrate; the only continuity concern is the retention gap during the physical swap, so schedule changeovers during low-risk windows for security-sensitive spaces.

6. Secure decommission

Do not just unmount the old cameras. Remove each MV21 from the dashboard, and because it carried recorded video on onboard storage, treat decommissioning as data disposal: ensure devices are wiped or physically destroyed per your data-handling policy before they leave the building. For federal and healthcare environments, document the chain of custody. Then release or co-term the freed licenses.

Procurement notes

Buy MV13 hardware and licenses through an authorized Cisco partner so warranty, license registration, and support entitlement are clean from day one. For US federal and DoD buyers, confirm Trade Agreements Act (TAA) compliance and country-of-origin documentation, and remember that camera buys frequently land on the Government Purchase Card (GPC) for smaller quantities. Plan for lead times on volume orders rather than assuming on-shelf stock, and confirm license terms align to your contract period before the PO goes out. You can review current indoor MV options in our catalog, and the full lifecycle record for this unit lives on the MV21-HW EoL page alongside our broader Cisco end-of-life tracker.

Ready to scope an MV21 refresh? Tell us your camera count, sites, and target retention, and we will size MV13 hardware, PoE, and co-termed licensing into a single quote. Start at get a quote.