Switching your mobile device management (MDM) platform is one of those IT decisions that feels daunting on the surface, but with the right plan, it can be surprisingly smooth. Whether you’re leaving a legacy MDM that no longer fits your needs, frustrated by poor support, or simply looking for a solution purpose-built for dedicated and kiosk devices, migrating to Moki is a strategic move that pays off quickly.
This step-by-step guide walks you through the entire MDM migration process so you can make the switch with minimal disruption and maximum confidence.
Why Businesses Switch MDM Providers
Before diving into the how, it’s worth understanding the why. The most common reasons organizations change MDM solutions include:
- Poor customer support and slow response times
- Overly complex platforms designed for employee devices, not dedicated kiosks or POS systems
- Pricing models that don’t scale well with device fleet growth
- Lack of Android Enterprise or BrightSign support
- Insufficient remote management capabilities
Moki was built specifically for dedicated and purposed devices, think kiosks, point-of-sale terminals, digital signage, and warehouse scanners. If your current MDM treats these the same as an employee’s personal phone, you’re probably leaving efficiency on the table.
Step 1: Audit Your Current Device Inventory
Before you touch a single setting in your new MDM, you need a complete picture of what you’re working with. Create a full inventory that includes:
- Total number of managed devices
- Device types (Android, iOS, BrightSign, etc.)
- OS versions and hardware models
- Installed apps and their versions
- Current policy and configuration profiles assigned to each device
- Location data and grouping structure
This audit becomes your migration map. Export everything from your current provider before you start, most MDMs allow CSV or JSON exports from the device console.
Step 2: Design Your New Structure in Moki
Moki organizes devices using a hierarchical account and group structure. Before enrolling a single device, spend time designing how your fleet should be organized. Consider how Moki’s Device Group features let you group devices by location, device type, function, or any combination that makes sense for your operations.
Common grouping approaches include:
- By location (e.g., Store #101, Store #102)
- By device function (e.g., POS Terminals, Customer Kiosks, Back Office)
- By OS platform (e.g., Android Enterprise, iOS, BrightSign)
Getting this right upfront saves hours of reorganization later.
Step 3: Set Up Your Moki Account and Policies
Work with Moki’s onboarding team to configure your account. This is where Moki’s industry-leading support really shines, you’re not doing this alone. Set up:
- Device configuration profiles (Wi-Fi, VPN, restrictions)
- App deployment policies
- Kiosk lockdown settings if applicable
- Alert thresholds and monitoring rules
- User roles and admin permissions
Moki’s platform makes it straightforward to apply policies at scale using automation-friendly rules, meaning you can configure hundreds of devices the same way without manual intervention.
Step 4: Run a Pilot Migration
Never migrate your entire fleet at once. Select a small pilot group, ideally 5–20 devices across different device types and locations, and migrate those first. This gives you a chance to:
- Validate that policies apply correctly
- Test app deployments end-to-end
- Identify any configuration gaps
- Train your IT team on Moki’s interface
- Measure device enrollment time
Document everything that goes wrong (and right) during the pilot. This becomes your runbook for the full rollout.
Step 5: Enroll Devices Using Zero-Touch or Manual Enrollment
Moki supports Android Zero-Touch Enrollment for large-scale deployments, which allows devices to automatically configure themselves when they connect to the internet, no IT hands required. For iOS devices, Apple Business Manager (ABM) or Apple School Manager (ASM) integration enables similar automated provisioning.
For smaller batches or one-off devices, manual enrollment via QR code or enrollment URL is quick and straightforward.
Step 6: Decommission Your Old MDM
Once all devices are verified in Moki and operating correctly, it’s time to formally unenroll them from your legacy MDM. Don’t cancel your old contract until:
- 100% of devices are confirmed in Moki
- All policies are verified and active
- Your team has had at least 2–4 weeks of live operation in Moki
- You’ve exported any historical data you want to retain
Most MDM contracts are annual, so time your migration to avoid paying for two platforms longer than necessary.
Step 7: Optimize and Train
Migration complete doesn’t mean migration finished. Spend the first 30 days after cutover:
- Reviewing alert and reporting configurations
- Training all IT and operations staff on Moki’s dashboard
- Setting up custom alerts for device health
- Exploring features like remote control, action sequences, and content management
Moki’s support team is available to help you get the most out of the platform. Unlike larger MDM providers where you’re a ticket number, Moki treats every customer as a partner.
Common Migration Mistakes to Avoid
- Migrating during peak business hours or a busy season
- Skipping the pilot phase and going straight to full rollout
- Not exporting historical device data before leaving your old MDM
- Underestimating the time needed to recreate policy profiles
- Forgetting to update device enrollment credentials with IT staff
Ready to Make the Switch?
Moki makes migration as painless as possible with dedicated onboarding support, clear documentation, and a platform purpose-built for the types of devices you actually manage. Schedule a demo to see how Moki fits your fleet, or start a free trial today.