Cisco Meraki MV71 EoL: Migration Guide to MV72 Camera

The Cisco Meraki MV71 (PID MV71-HW) was part of Meraki's first generation of cloud-managed video: a weatherized outdoor dome that recorded to onboard solid-state storage and pushed motion metadata and management up to the Meraki dashboard. It did its job well for years, but its lifecycle has now closed. Cisco set End-of-Sale on June 19, 2019, and the Last Day of Support (LDoS) was June 19, 2026. If you still have MV71 cameras watching loading docks, perimeters, parking structures, or building entrances, they are now outside Cisco's support envelope and should be on a near-term refresh plan to the current outdoor model, the Meraki MV72 (MV72-HW).

Why the MV71 EoL matters right now

A camera that still streams to the dashboard can feel fine, which is exactly the trap. Past LDoS, three things stop: Cisco no longer ships firmware updates or PSIRT security fixes for the platform, Meraki technical support will not open or work TAC cases on it, and advance hardware replacement (the RMA that comes bundled with the MV license) is gone. A camera that dies on a dark corner of a campus after LDoS is simply a dead camera until you buy a new one out of pocket.

For regulated buyers the exposure is sharper than a single failed unit. Federal, DoD, SLED, and healthcare environments are routinely audited against the rule that production devices must run vendor-supported, patchable software. An MV71 cannot receive a firmware patch for a newly disclosed vulnerability, so it becomes an unremediable finding in a CMMC, FISMA/RMF, HIPAA, or PCI assessment. Physical-security cameras also sit on the network and capture sensitive video; an unpatchable endpoint recording a clinical corridor or a controlled-access door is precisely the kind of device assessors flag. Acting before the next audit cycle is cheaper than explaining a known-unsupported device in a POA&M.

What each milestone date means

• End-of-Sale (June 19, 2019): the last day the MV71-HW could be ordered new through Cisco. Everything after this is spares, used, or gray-market inventory, none of it eligible for new factory warranty.
• End of Software Maintenance (n/a): Meraki firmware is delivered as a unified cloud-managed train rather than per-SKU maintenance branches, so there was no separate published software-maintenance milestone; firmware eligibility simply ends at LDoS.
• Last Day of Support (June 19, 2026): the hard cutoff. After this date there are no firmware or security updates, no TAC, and no RMA for the MV71. The hardware can keep recording, but it is unsupported and unpatchable from this day forward.

The recommended replacement: Meraki MV72 (MV72-HW)

The MV72 is the direct successor in the outdoor varifocal dome class and is a generational jump, not a cosmetic refresh. The MV71 used a 1/3.2-inch 5MP CMOS sensor but actually recorded 720p (1280x720) H.264 video through a 3-10mm f/1.3-2.5 varifocal lens, with 128GB of high-endurance encrypted SSD storage. The MV72 moves to a 1/3-inch 4MP (2688x1520) sensor recording up to 1080p H.264 at 20fps through a 3-9mm f/1.2-2.3 varifocal lens, with dashboard-controlled 3x optical zoom and 256GB of onboard SSD (512GB on the MV72X, which records the full 4MP). In practice that means higher usable resolution, a faster lens for low light, and remote zoom/focus adjustment from the dashboard instead of a ladder and a screwdriver.

The bigger difference is on-device intelligence. The MV71 was a first-gen camera limited to basic motion detection. The MV72 carries an onboard processor and edge machine learning, enabling object detection and person tracking computed on the camera itself, plus audio recording via an integrated microphone and an 802.11ac Wi-Fi radio with Bluetooth for installation and survey workflows. That edge compute powers dashboard features like motion search, people analytics, and motion recap without back-hauling raw video to a server, which is the entire point of Meraki's architecture.

Environmentally the MV72 is also a step up: it carries IP67 weather-proofing (versus IP66 on the MV71) and IK10 vandal resistance, with a -40C cold-start rating that suits exterior northern-climate deployments. Both cameras draw from 802.3at PoE+ (the MV71 peaks near 21.95W, the MV72 near 23.4W), so existing PoE+ switch budgeting generally carries over with minimal rework.

A practical migration plan

1. Assessment and inventory

Export your camera list from the dashboard and pull every MV71 by serial, network, mount type, and the PoE switchport feeding it. Note retention requirements per camera (a camera under a records-retention or evidentiary mandate may need longer storage, pointing you to the 512GB MV72X). Capture each camera's field of view and current zoom/focus so the replacement can be aimed to match.

2. License transition

Order one MV Enterprise license per MV72, term-matched to your standard refresh window. Plan to claim and license new cameras in the dashboard before the physical swap so each unit comes online supported and ready, with no gap in recording coverage.

3. Config and feature parity

Recreate retention/quality profiles, motion-based recording schedules, alert zones, and access roles on the new cameras. The MV72's edge ML unlocks people analytics and motion search you could not run on the MV71, so treat this as a chance to tighten alerting rather than a like-for-like copy. Validate video export and chain-of-custody workflows if footage is used evidentially.

4. Physical: mount, power, and uplinks

The MV72 reuses standard outdoor dome mounting hardware, but confirm bracket and gang-box compatibility per location. Verify each switchport delivers 802.3at PoE+ and that the switch's total PoE budget absorbs the slightly higher per-camera draw. Reuse existing outdoor-rated cabling where it tests clean; re-terminate or replace runs that fail. Where you previously relied on the MV71's Wi-Fi, note the MV72 still offers an 802.11ac radio for sites where pulling new copper is impractical.

5. Phased cutover

Swap by zone, not all at once. Bring up MV72 units alongside the MV71 they replace, confirm framing, focus, night-vision range (IR is good to ~30m on both), and recording, then decommission the old unit. This keeps continuous coverage on perimeters and entrances throughout the project and gives you a rollback if a mount or angle needs rework.

6. Secure decommission

MV71 storage is encrypted, but follow your data-handling policy on retired devices: remove each camera from the dashboard to revoke cloud access and its license seat, then sanitize or physically destroy the SSD per your media-disposal standard before the hardware leaves the property. For DoD and healthcare sites, document the disposition for your audit trail.

Procurement notes for regulated buyers

Source the MV72 through an authorized Cisco partner so warranty and licensing register cleanly under your organization. uniqcli supplies TAA-compliant hardware suitable for federal and DoD acquisition, accepts the Government Purchase Card (GPC) for in-threshold orders, and can quote camera plus license as a single line per unit. Outdoor cameras and multi-year licenses can carry lead time, so place orders ahead of mounting and electrical scheduling. Browse current Meraki MV inventory in our catalog or the broader catalog, review the full milestone detail on the MV71-HW EoL page, and see other affected products in the Cisco EoL lookup.