Migration Plan: Upgrading from CM8 to CM10

The document provides an overview plan for all customers who are using My OPSWAT On-premise version 202x (also known as Central Management v8) to upgrade to My OPSWAT Central Management (Central Management v10).

Depending on your data and current infrastructure, the migration time can be a day or several weeks.

Prerequisites

  1. Minimum Central Management v8: 2025.4.1
  2. Minimum Central Management v10: 10.3.2511

If you are using the older version, you need to upgrade to the minimum version to support the migration plan. Follow the document Upgrade My OPSWAT to update Central Management v8, and CM10 documentation to upgrade CM10

Plan Overview

Central Management 8 is deployed using an OVA-based appliance, whereas Central Management 10 introduces support for MSI-based installation. Directly upgrading the OVA will not retain existing data. Therefore, a structured migration process is required to ensure data continuity and system integrity. Basically, you will need to install CM10 on a separate server and migrate data from the CM8 server to the CM10 server.

There are 6 steps to migrate from CM8 On-prem to CM 10 On-prem:

Step 1: Identify the use case and required features

Step 2: Determine the necessary data for migration

Step 3: Assess network requirements and prepare the environment

Step 4: Migrate the configuration settings and inventory data

Step 5: Migrate OPSWAT products

Step 6: Migrate historical data

The migration time can be an hour or several weeks, depending on the customer's use case and expectations.

Plan Detail

Step 1: Identify the use case and required features

Review the products currently in use and their usage.

  • Using _____ MetaDefender Endpoint
  • Using _____ MetaDefender Kiosk (Hardware / Software)
  • Using _____ MetaDefender Core
  • Using _____ MetaDefende ICAP
  • Using _____ MetaDefende MFT
  • Using _____ MetaDefende Drive
  • Using _____ MetaDefende Sandbox
  • Using _____ MetaDefende Media Firewall
  • Using other products ___

If you're using products that are not listed above, it means Central Management 10 does not support integration with those products.

Step 2: Determine the necessary data for migration

Review the required features.

  • Using Proxy
  • Using AD integration
  • Using SSO
  • Using HTTPS
  • Using SMTP
  • Using features in CM8 but not available in CM10:___
  • Auto-reconnect MetaDefender Endpoints
  • Able to re-deploy all MetaDefender Endpoints
  • Keep all groups & Configuration
  • Keep all Policy & Configuration
  • Auto reconnect MetaDefende Core/Kiosk
  • Keep Processing History in ____ days
  • Keep Event Log in ____ days

Step 3: Assess network requirements and prepare the environment

It's important to assess network requirements and prepare the switching plan. Here are 3 common deployments. If you are not using one of them, please contact OPSWAT support.

Do NOT switch at this step. Use the info on this step to prepare the environment only.

Deployment A: OPSWAT MetaDefender Products are connecting to CM8 FQDN.

If you are using an FQDN for CM8. You can plan to update your local DNS to switch to the new IP of the CM10 server. In this example:

Deployment B: OPSWAT MetaDefender Products connect to a reverse proxy. Redirect traffic from proxy to Central Management.

If you are using a reverse proxy. You can plan to update the rule to redirect from CM8 IP to CM10 IP:

Deployment C: OPSWAT MetaDefender Products connect directly to the Central Management IP Address

This deployment might have downtime since you need a plan to re-assign IP from the current CM8 deployment to CM10 server.

If it is not possible to retain the same network interface for all OPSWAT products when connecting to the new Central Management v10, you will need to re-enroll those products into the new My OPSWAT Central Management IP.

If your current deployment matches one of these deployments. It's time to prepare the environment. Let's install CM10 on a separate server.

Follow the CM10 documentation to install CM10. Dont forget to install the required software and prepare enough disk space based on the System Requirement document. These are common questions as below:

Ensure that the same Recovery Key and Registration Code are used for both Central Management v8 and v10. Using different credentials will result in the need to re-enroll all connected MetaDefender products.

Additionally, verify that both CM8 and CM10 are operating within the same network environment. Update firewall rules as needed to allow MetaDefender products to communicate with CM10 over ports 9000 and 443. Note that the required ports may vary depending on your specific deployment configuration.

Step 4: Migrate the configuration and inventory data

The configuration and inventory data include system configuration, user info, a list of enrolled products & configuration. You need to run the following steps to migrate data.

i. Follow steps in Import/Export - My OPSWAT Central Management v8 - Legacy to backup Product Configurations, User Management, My OPSWAT Configurations

ii. Download and run the CM8Converter on CM10 server to convert data

  • Download the CM8Importer
  • Extract and copy the cm8importer to "CM10 installation location" <default in "C:\Program Files\OPSWAT">
  • Copy the backupdate from step (i) to "CM10 installation location" <default in "C:\Program Files\OPSWAT">
  • Put the backup file and CM8Importer.exe to the same folder
  • Run the following command:
    • On Windows - Command Prompt
Powershell
Copy

iii. Verify the active data

Waiting for the importing process. It's similar to this one

Active data includes system configuration, list of enrolled products & configuration. You would need to verify some important data as below

a. Verify the User Access

Try to access CM10 with your credentials. You will need to reset the password and PIN on the first login. The master account is the most important account that you create when setting up the CM10. Ensure you can log in as the master account and one imported account from the CM8.

If you are using SSO configuration or Active Directory. You can verify the integration after switching to CM10. However, ensure that you can use the master account and one imported account from the CM8 before going to the next step.

b. Verify the system configuration

Compare the configuration between CM8 and CM10. The UI can be different. For any values that exist in CM8, they should be the same in CM10. For any new configurations in CM10. The default value will be set. You can search for more details from the OPSWAT Docs or contact OPSWAT Support if you need to clarify any configuration.

c. Verify the Inventory and Product Configurations

Compare the list of product groups between CM8 and CM10

Compare the list of MetaDefender Products between CM8 and CM10.

in CM8. All similar products belong to different Groups. Each group will have separate settings. The default value is set for any non-existent group settings from CM8

d. Verify the Set configuration and Policy Configuration

You can compare the individual product configuration by going to the product detail settings.

The Set setting will be migrated to Policy. You can compare the Set setting to the policy. For example, the Set Name will be converted to Policy Name.

Step 5: Migrate the history data

This step will copy all the processing history scan data from CM8 to CM10.

Migrating historical data involves copying records from CM8 to CM10. The duration of this process can vary significantly---from about an hour to several days or even weeks---depending on the size of your data. While this step may take time to complete, it does not block your deployment. You can either proceed with the next steps in parallel, wait until the migration finishes, or skip this step entirely by retaining the CM8 instance for historical queries.

i. Login CM8 Console ( version >= 2025.4.1 )

ii. Navigate to Settings > Global > Data Migration

iii. Enter the following info:

  • CM10 URL
  • Registration code
  • Start Date & End Date

iv. Click "Start Migration"

v. Then wait for the process

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard