On December 3, 2025, Cisco announced the end-of-sale for Meraki Systems Manager (SM), its enterprise MDM platform. If you're managing a device fleet on Meraki, you need to start planning your migration now. This guide explains the timeline, your options, and why Appaloosa is the migration path built specifically for organizations that want a simpler, more reliable MDM.
Key dates you need to know
- December 3, 2025 - End-of-Sale announced. No new multi-year licenses.
- June 3, 2026 - Last day to purchase 1-year or 3-year Meraki SM licenses.
- June 3, 2029 - End of support. Platform goes dark. Migration must be complete.
Why is Cisco discontinuing Meraki SM?
Cisco cited "limited growth and ongoing operational costs" as the reason for exiting the MDM market. The company will shift its resources toward other strategic growth areas, and is pointing customers toward Ivanti Neurons for MDM as a replacement through its SolutionsPlus program (available Q3 FY26, minimum 50 licenses).
That's a signal: Meraki SM was never Cisco's core product, and the decision to wind it down confirms what many IT teams already experienced: platform instability, directory sync issues, and a support model built around ticket queues rather than fast resolution.
Key point: End-of-Sale does not mean the platform stops working today. You have until June 3, 2029 before Meraki SM is fully shut down. But the migration window is real, and choosing a new MDM takes time. The best time to start is now.
What are your migration options?
Option 1: Ivanti Neurons for MDM (Cisco's recommended path)
Cisco has partnered with Ivanti to offer its Neurons for MDM platform as the "official" replacement. It's a comprehensive Unified Endpoint Management (UEM) platform, but it's designed for large, complex enterprise environments. The minimum purchase threshold is 50 licenses, and onboarding typically requires dedicated professional services. If you came to Meraki for simplicity, Ivanti may feel like a step in the wrong direction.
Option 2: Migrate to Appaloosa
Appaloosa is a modern, European MDM platform purpose-built for organizations that need powerful device management without enterprise-level complexity. It fully supports iOS, Android, macOS, and Windows fleets, and was designed from the ground up to be easy to deploy, easy to maintain, and easy to scale.
How to migrate from Meraki to Appaloosa: a practical checklist
- Audit your current Meraki deployment
List all enrolled devices, active policies, app configurations, and integrations (directory, VPN, Wi-Fi profiles). Export what you can from the Meraki dashboard before your licenses expire. - Map your policies to Appaloosa equivalents
Appaloosa supports the full Apple MDM and Android Enterprise frameworks. Most Meraki configurations (restriction profiles, app push, Wi-Fi payloads, VPN configs) have a direct equivalent. Our team provides a free onboarding call to help you map them. - Set up your Appaloosa environment
Create your Appaloosa account, connect your Apple Business Manager / Android Enterprise accounts, and configure your organizational structure. Most customers have a working environment within a day. - Pilot with a subset of devices
Migrate 10–20 devices from a single department first. Validate that app distribution, restrictions, remote access, and directory sync all work as expected before rolling out fleet-wide. - Complete your fleet migration and unenroll from Meraki
Once validated, migrate remaining devices in batches. When complete, unenroll all devices from Meraki SM before your license expires to avoid co-terminus billing complexity.
Meraki vs. Appaloosa: a head-to-head comparison
Here's an honest look at how the two platforms compare across the dimensions that matter most to IT teams.
| Cisco Meraki SM | Appaloosa | |
|---|---|---|
| Data hosting | USA | France (ISO 27001) |
| COPE mode | Not available | Available |
| Contact sync | No | Yes |
| Remote control | No | Yes (TeamViewer integrated) |
| Directory sync | Unreliable | Works reliably |
| Support | Ticket-based, long delays | <5 min response, dedicated team |
| Training & onboarding | Limited guidance | Included |
| License management | Co-terminus, prorated, complex | Simple, per-device, flexible |
Why Appaloosa is the right MDM for your team
European hosting, ISO 27001 certified
Your data stays in France, on infrastructure certified to ISO 27001. Full GDPR compliance is built-in, not bolted on.
Support that actually responds
Real humans, response in under 5 minutes. No ticket queues. No waiting for an automated reply. A team that knows your setup.
Simple, predictable licensing
Per-device pricing. No co-terminus headaches. No prorated billing nightmares. You know exactly what you pay and for what.
Onboarding included
Every Appaloosa subscription includes guided onboarding. We migrate with you, not just hand you a documentation portal.
Don't wait for the 2029 deadline
Three years may feel like a long runway, but enterprise MDM migrations take time, especially if you have hundreds or thousands of devices across multiple platforms. Organizations that start planning now will have the luxury of a phased, low-risk migration. Those who wait will be scrambling.
Cisco is exiting the MDM market. The sooner you move to a platform built for the long term, the better your device management operations will be, not just as a contingency, but as a genuine improvement.
Note on credit memos: If you have Meraki SM licenses extending beyond June 3, 2029, Cisco will automatically issue partial credit memos, no request needed. Credits apply to the remaining term and can be used toward other Cisco products. Factor this into your migration budget planning.
Frequently asked questions
Do I have to migrate immediately?
No. Meraki SM will continue to function and receive security patches until June 3, 2029. But new licenses cannot be purchased after June 3, 2026, and the platform will be fully shut down in 2029. We recommend beginning your evaluation now and completing migration well before the deadline.
Does Appaloosa support the same platforms as Meraki SM?
Yes. Appaloosa supports iOS, iPadOS, macOS, Android (including Android Enterprise and Samsung Knox), and Windows. Both supervised and unsupervised enrollment modes are supported, along with BYOD, COPE, and fully managed device profiles.
How long does an Appaloosa migration typically take?
For a fleet of up to 500 devices, most customers complete the full migration in 2 to 4 weeks. Larger fleets with complex policy configurations may take 4 to 8 weeks. Our team works alongside yours throughout the process.
What happens to our Meraki license credits?
Cisco will automatically initiate the credit memo process for any licenses extending beyond the June 3, 2029 end-of-support date. Credits are issued to the original purchasing entity and apply to Cisco products. Knowing your credit position helps you budget your migration investment accurately.