MDM Migration. Switch Vendors Without Switching Devices.

MDM migration is the process of moving a managed device fleet from one mobile device management platform to another. The migration covers device re-enrollment (or native MDM-to-MDM transfer where supported), policy translation between the two MDM frameworks, app license transfer through Apple VPP and managed Google Play, certificate and VPN profile reissuance where required, and validation that every device reports correctly to the new MDM with the expected configurations. A well-executed migration preserves user productivity throughout the transition.

No, in most cases. Apple introduced native MDM-to-MDM migration in iOS 26 and macOS 26: devices accept a single migration profile and migrate from the old MDM to Bento, preserving apps, data, and user state. Older Apple devices, Android Enterprise devices, and Windows devices have vendor-specific re-enrollment paths that do not require a factory reset in most scenarios. The Bento migration assessment identifies any devices that require wiping and re-enrollment so they can be planned separately.

Migration timeline depends on fleet size, policy complexity, and platform mix. A 100-device single-platform fleet typically migrates in two to three weeks (assessment, translation, pilot, fleet cutover). A 1,000-device multi-platform fleet typically takes four to eight weeks. A 10,000-device global fleet with complex policy structures may take three to six months, including phased cutover by business unit. Bento’s migration assessment provides a specific timeline for your situation.

Yes. Apple VPP licenses transfer through Apple Business Manager: existing app assignments persist, and licenses do not need to be repurchased. Managed Google Play apps transfer through your Google Workspace tenant: app deployments continue working after migration. Custom enterprise apps (private APKs, IPAs, MSI packages) re-upload to Bento’s enterprise app store and re-deploy through Bento’s policy framework.

The migration is designed to minimize disruption. On Apple devices using iOS 26 / macOS 26 native migration, users see a single profile acceptance prompt and continue working. On Android Enterprise, users may need to re-enroll through QR code or zero-touch (typically a 5-minute process). On Windows, the Autopilot enrollment cycle automatically handles re-enrollment. Pilot group testing identifies any user-facing impact before fleet cutover, and cutover waves are scheduled outside business hours where possible.

Bento’s migration assessment specifically identifies feature parity gaps before migration commits. In most evaluations, Bento covers all required features (often with capabilities the previous vendor did not offer, such as Offline QR Commands or on-premise deployment). Where genuine gaps exist, the assessment surfaces them so the customer can decide whether to proceed, request a roadmap commitment, or wait. No surprise feature gaps were discovered after migration.

Bento is €1/device/month flat with all features included. Microsoft Intune typically costs €6 to €12 per user per month, bundled in M365 E3/E5 (or standalone). Jamf Business runs €4 to €7.50 per device per month; Jamf Pro runs higher with negotiated enterprise pricing. VMware Workspace ONE Advanced runs €7 to €9 per device per month. For a 1,000-device fleet, Bento typically costs €12,000/year compared to €60,000 to €120,000 on the alternatives. Migration ROI is usually clear within the first invoice cycle.

SOTI MobiControl migrations follow Bento’s standard five-step migration process: assessment, policy translation, pilot, fleet cutover, and validation. SOTI’s strengths in rugged Android, iOS supervised, and Windows endpoint management all carry over to Bento. SOTI MobiControl policy exports through the REST API translate into Bento’s policy framework. SOTI Surf web filtering rules map to Bento’s content filtering. SOTI Hub content distribution maps to Bento’s Mobile Content Management. SOTI Lockdown profiles map to Bento’s Kiosk Mode and Dedicated Device configurations. The migration team has executed SOTI cutovers across retail, logistics, healthcare, and field-service environments, with playbooks specific to rugged Zebra, Honeywell, and Samsung deployments managed through SOTI.

Migration support is included in the Bento subscription. The migration team handles assessment, policy translation, pilot validation, and cutover support. There is no separate professional services contract, no per-hour consulting charge, and no migration package upgrade. For very large or complex migrations (10,000+ devices, multi-region rollouts, M&A integrations), Bento’s migration team can schedule extended engagement at no additional cost.

Yes. Parallel running is the recommended approach for any migration involving more than 100 devices. A pilot group of 10 to 50 devices runs on Bento while the rest of the fleet remains on the current MDM. The pilot validates policies, apps, and compliance for one to two weeks before fleet cutover. After fleet cutover, the old MDM tenant typically remains in read-only fallback mode for 30 to 60 days before final decommission.

Compliance history from the previous MDM is exported as part of the migration assessment for archival purposes (audit retention, regulatory requirements). Going forward, Bento’s compliance reporting starts fresh on the cutover date, with full audit-trail capabilities. For organizations subject to multi-year retention requirements (HIPAA, CJIS, SOC 2 Type II), the legacy export and the Bento ongoing reports together provide a complete compliance record.