How To's
Home » » <!--<span></span>--> <span>How To's</span>

Last updated: July 24, 2026

How to migrate Mobile Device Manager Plus(MDM) server from one machine to another without losing any data?

This guide explains how to migrate the Mobile Device Manager Plus server to a new machine without losing data. Before migrating, ensure the NAT address isn't the local machine's IP/FQDN, avoid a fresh install on the new machine, and whitelist required domains and ports. Admins stop the server, zip and copy the installation folder to the new machine, run migrate-server.bat, and start the server there, verifying success via devices' last-contacted time and remote database connectivity.

Description

There are certain cases where the MDM server is to be migrated from one machine to another, such as moving the server from test environment to production environment, temporarily moving the server to update the machine, moving it to a new machine to improve scalability etc.,

Before migrating the server, there are a set of important steps to be followed:

  • If the NAT address being used in the MDM Server is the IP address/FQDN of the local machine, then the server cannot be migrated.
  • Do not have a fresh installation of MDM in the machine to which the server is to be migrated.
  • Ensure these domains and ports are white listed/excluded in firewall and other third-party filters in the new machine.
  • Do not uninstall the MDM server from the old machine until the migration is successful. 

Steps

Existing machine:

  • Stop the MDM server. Ensure it has fully stopped by checking whether any MDM-related process is running in the task manager.
  • Zip the entire MDM server installation folder found in <Directory>/ManageEngine. Copy the ZIP file

New machine:

  • Paste the ZIP file copied from the existing machine and expand the ZIP file.
  • Open Command Prompt as Administrator and navigate to MDMServer/bin and execute migrate-server.bat.
  • Start the MDM server in the new machine and ensure all the managed devices can contact the MDM Server and vice-versa.
Successful migration can be confirmed by scanning the devices from the MDM Server and verifying whether last contacted time is the most recent. If you've configured remote DB, ensure the new server can contact the remote DB.

NOTE: The above steps are applicable, even if you've configured MDM with Secure Gateway.

 

 

Frequently asked questions

Can the MDM server be migrated if its NAT address is set to the local machine's own IP or FQDN?

No — if the NAT address configured in the MDM server is the IP address/FQDN of the local machine itself, the server cannot be migrated to another machine.

Should the old MDM server be uninstalled before completing the migration?

No, don't uninstall the MDM server from the old machine until the migration to the new machine has been confirmed successful.

How can I confirm the MDM server migration was successful?

Scan devices from the new MDM server and check that their last-contacted time is recent; if a remote database is configured, also confirm the new server can reach it.