Skip to main content
Feb 01, 2016

How to migrate from MDM to MAM

While a large percentage of our customers use Apperian MAM® alongside EMM suites that require an MDM profile, we are also seeing enterprises moving away from the device-centric control of mobile device management (MDM). End users often don't like MDM (especially on personal devices), and organizations are migrating to mobile application management for app-centric security that provides a better, less controlling user experience. Apperian is purpose-built at the app level which provides greater security and granular app control. This guide helps you plan your move from MDM to MAM. Our experience with customers making the migration shows that end-user communication is important before and during the migration. End users of MDM-controlled devices may be wary of a MAM platform being similar in its control of the device. But this isn't the case. With the Apperian platform, the end-user won't need to install an MDM profile and app developers won't need to use any SDKs. Clearly communicating to end users that the migration from MDM to MAM will provide a better, less invasive and less controlling experience will help with a successful migration.

Define Success

Before starting the migration, Apperian's customer success team works with the customer to define what a successful migration looks like. For example, success may be defined as a certain percentage of current MDM users are now using MAM to get their enterprise apps by a specific date. 

Configure Apperian MAM® Platform

Apperian Support and Customer Success will help you configure single-sign-on (SSO), brand your app catalog, upload your apps, apply policies and secure your apps.

Communicate the Plan

Clear communications to all MDM end users is key to successful MAM migration and adoption. Make sure you include a member of your organization's communication team on the migration project. Work with the communication team to understand the best channels and strategies in communicating with the MDM user community. For example, a company intranet may be the best way to get the message out as opposed to sending emails. The communication team can help with building MAM landing pages that users will see before installing the app catalog and the associated apps. Here are good examples:

Notify End Users

Use popular communications channels (intranet, email, posters) to notify end users of the upcoming migration from MDM to MAM and detail the actions they will need to take. This communication should be clear in that MAM isn't about locking down the end user's device but in securing only the apps that are installed onto the device. Keep this communication short and concise as the installing the app catalog is a simple process that should take only a couple minutes. Apperian's  Enterprise App Adoption Guide has some good examples of app store invitation email templates. Here’s a sample:

Install the MAM or App Catalog

The users will follow simple instructions on how to install the app (app catalog) onto their devices. Here's a sample flow:
  • End user receives an email with a link to the app catalog landing page (see above examples)
  • The landing page includes a direct link to download and install the app catalog onto the mobile device; the download link must be opened from the mobile device
  • The app catalog is installed on the device
  • The users taps on the installed app catalog and logs in using either their SSO password or one supplied to them by the MAM team (dependent on whether SSO integration is done as part of the MAM configuration)
  • Once logged in, the user taps and downloads the apps available to them based on their access level or group membership

Remove MDM Profile from End-User Devices

These are the general steps that end users will take to remove the MDM from their devices.


  1. Uninstall the profiles related to MDM under Settings > General > Profiles
  2. Uninstall the MDM app from the iOS device


  1. Go to settings >security>device admin>deactivate {MDM provider}
  2. Uninstall {MDM provider}
  3. Unencrypt the device
  4. Unencrypt the SD card
  5. Go back to device admin uncheck android device manager
  6. Restart device

Robert Lacis

More from the Blog
Mar 13, 2018

Latest Revelations Confirm Arxan’s Suspicions of Source of Apple Source Code Leak Issue

In early February news broke
Read more
Jan 11, 2017

Apperian Moving Up and To the Right as Part of Arxan Technologies

A letter from Mark Lorion, President & General Manager of Apperian. Dear Apperian Customers and Partners,
Read more
Dec 27, 2016

Predictions for 2017 - Where is Enterprise Mobility Headed?

The new year is around the corner and as we look back at 2016 it was an exciting year for the enterprise mobility market, ful ...
Read more