On-Prem Migration to IMRON Cloud

Updated January 30, 2026

Introduction

This article is intended for UnityIS Web On-Premises systems that wish to migrate to IMRON Cloud Services.

Pre-Requisites

Before beginning the migration, ensure the following requirements are met:

  1. Active Software Maintenance

    • The existing IS2000/UnityIS system must have an active software maintenance plan.
    • To verify, log in to UnityIS and navigate to Help > About.

  2. SQL System Admin Access

    • Ensure access to the existing SQL Server or MariaDB Server with a SQL account that has System Admin privileges.

  3. Windows Local Admin Rights

    • A Windows account with local admin rights on the existing UnityIS server is required.

  4. Cloud Server Setup Notice

    • Provide 1-day advanced notice to IMRON Support to prepare the Cloud server instance.

  5. Migration Timeline

    • Migration to IMRON Cloud will take approximately 1 day, depending on the system size.

  6. Cloud Instance Naming

    • Select a Cloud instance name, e.g., abc.imron.com (replace abc with the client’s name).

Pre-Migration Procedures

Note: The existing production UnityIS server can remain active and operational during this process.

  1. Database Backup
    • Create a backup of the existing database.
    • Any updates made to the on-premises system after this backup will not be included in the IMRON Cloud system.
  2. Restore the backup on to the new Cloud server
  3. Make sure you have the following ports opened in your Firewall, depending on the Access Controllers you are using:
    • Mercury Controllers: UnityIS Cloud requires port 3001.
    • Azure Controllers: UnityIS Cloud requires port 9723.
    • Axis A1001 Controllers: Configure Port Address Translation (PAT) from the private IP of the controller to the public IP of the network.

Migration Procedures

Note: This process requires a technician to log in to the Mercury and Azure controllers to reconfigure Host Communication settings:

  • Mercury Controllers: UnityIS Cloud requires port 3001.
  • Azure Controllers: UnityIS Cloud requires port 9723.
  • Axis A1001 Controllers: Configure Port Address Translation (PAT) from the private IP of the controller to the public IP of the network.


Performing a Parallel Migration: 

Notes:  A parallel migration process occurs when both the existing IMRON system and the new IMRON System are both online. This process results in the least amount of downtime and least impact on day-to-day routine. Make sure you have access to both the existing IMRON system and the new system at the same time.

Steps:

  1. In the original IMRON System, navigate to Hardware Manager

  2. Select the first controller you want to migrate to the Cloud.

  3. In the Controller property, UNPOLL (or tun off POLLING) on this controller. Make sure to Save your changes. Once the controller goes offline

  4. Next, login to the Controllers Web Configuration page. Navigate to the Host Comm section. Set the protocol from IP Server to IP Client. In the Host Communication IP section, enter the Cloud domain name, for example:  myunityiscloud.imron.com (replace 'myunityiscloud' with your actual name). Then click on Accept and Apply Settings to save your changes

  5. In the Cloud instance, go to Hardware Manager, locate the same controller and set it to POLL.

  6. After about 10 seconds, the controller should come online

  7. Repeat the process for the rest of the controllers.

Post-Migration Procedures

After migration, perform the following functional tests to ensure the UnityIS Cloud system is fully operational:

  1. Disable All Services on onPrem system

    • On the onprem server, make sure you go into Windows Services and locate all the IMRON Corporation Services and stop all services. 

    • Set the UnityIS Web Service to 'Disable'

    • Set the Mercury Driver service to 'Disable'

  2. Live Event Verification

    • Check that live events are displayed in the Event Manager.

  3. Controller Status

    • Confirm all controllers are online and the Date/Time is accurate.

  4. Command Testing

    • Send a momentary unlock command to a few doors to verify that commands are successfully sent to the controllers.

  5. Door Schedule Updates

    • Reconfigure any door unlock/relock schedules as needed.

  6. Trigger/Macro Review

    • Re-confirm the functionality of all Triggers and Macros.

  7. Training

    • IMRON Support will provide training as needed to ensure smooth operation.

By following these steps, your UnityIS system will transition seamlessly to IMRON Cloud Services. If you have any questions or need assistance, contact IMRON Support.

Was this article helpful?