> Source: [sk179444](https://support.checkpoint.com/results/sk/sk179444)

# sk179444 - Migration from a Standalone environment to a Distributed environment to versions R81.10 and higher versions

| Property | Value |
|----------|-------|
| Solution ID | sk179444 |
| Date Created | 2022-06-08 |
| Last Modified | 2026-11-18 |
| Technical Level | General |
| Products | Security Gateway, Security Management Server, Check Point Firewall |
| Versions | R82.10, R82, R81.20, R81.10 (EOS), R82.20 |
| OS | Gaia |

## Solution

To migrate to versions R80.10, R80.40, or R81, follow [sk154033](https://support.checkpoint.com/results/sk/sk154033).

**Table of Contents:**

* Overview
* Migration Procedure from a Standalone environment to a Distributed environment - separate Security Management Server and Security Gateway
* Migration Procedure from a Standalone environment to a Distributed environment - separate Multi-Domain Security Management Server and Security Gateway
* Changing References to the Security Gateway Object
* Limitations

### Overview {#Overview}

* **Migration from a Standalone environment to a Distributed environment (separate Security Management Server and Security Gateway):**

  Support for this migration is available for:
  * From versions R80.20, R80.30, R80.40, R81, R81.10, R81.20, and higher

  * To versions R81.10, R81.20, and higher

  You can migrate the management database between different versions (if you migrate to a higher version, then you also perform an upgrade).

  This migration process is based on the "New Upgrade" mechanism described in [sk163814](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk163814).
* **Migration from a Standalone environment to a Multi-Domain Server environment (separate Domain Management Server and Security Gateway):**

  * From versions R81.10, R81.20, and higher

  * To versions R81.10, R81.20 and higher

  You can migrate the management database between different versions (if you migrate to a higher version, then you also perform an upgrade).

  This migration process is based on the "Domain Migration" mechanism described in [sk156072](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk156072) (see the sections "Known Limitations" and "Migrating from a Security Management Server to a Domain Management Server").

### Migration Procedure from a Standalone environment to a Distributed environment - separate Security Management Server and Security Gateway {#MigrationProcedure1}

Show / Hide this section   

**Important** - Make sure to perform the procedure while you have physical access to the servers (not over VPN).

1. Back up the current management database on the Standalone server.

   1. Save a snapshot of your source Standalone server.

      This backs up the entire configuration.

      See the [Gaia Administration Guide](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=documents&product=184) for your version \> Chapter "Maintenance" \> Section "Snapshot Management".
   2. Save a backup of your source Standalone server.

      This file lets you extract the most important configuration easily.

      See [sk108902 - Best Practices - Backup on Gaia OS](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk108902) and the [Gaia Administration Guide](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=documents&product=184) for your version \> Chapter "Maintenance" \> Section "System Backup".
   3. Collect the CPinfo file from your source Standalone server (see [sk92739](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92739)).

      This file lets you see the most important configuration easily with the DiagnosticsView tool (see [sk125092](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk125092)).
2. Because the target server has a different IP address than the source server, you must prepare the source database before the export.

   In SmartConsole connect to the source Security Management Server:
   1. Create a new Host object with the new IP address of the target Security Management Server.

   2. In each configured Security Policy, add a new Access Control rule that allows connections from the new IP address to Security Gateways:

      |------------------------------------------------------------------------------|---------------------------------|--------------------------|
      | Source                                                                       | Destination                     | Services \& Applications |
      | Host object with the new IP address of the target Security Management Server | Each Security Gateway / Cluster | `CPD` `FW1` `FW1_CPRID`  |

      These are the predefined services:
      * `CPD` - TCP port 18191

      * `FW1` - TCP port 256

      * `FW1_CPRID` - TCP port 18208

   3. Install each updated Access Control Policy on each applicable Security Gateway and Cluster.

3. Export the current management database from the Standalone server.

   **Prerequisite** - You must always use the latest version of the Upgrade Tools from [sk135172](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk135172).
   1. Connect to the command line on the Standalone server.

   2. Log in to the Expert mode.

   3. Go to the *$FWDIR/scripts/* directory:

      `cd $FWDIR/scripts`
   4. Export the management database:

      For more information about this command, see the [CLI Reference Guide](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=documents&product=184) for your version \> Chapter "Security Management Server Commands" \> Section "migrate_server".

      `./migrate_server export -v <Target Version> [-l | -x] [-force-upgrade-flow] /<Full Path>/<Name of Exported File without File Extension>`

      **Note** - Use the parameter '`-force-upgrade-flow`' if the versions of the source Standalone server and the target Security Management Server are the same.

      Example:

      `./migrate_server export -v R81.10 -l /var/log/exported_db_standalone`
   5. Transfer the exported database TGZ file from the source Standalone server to your computer.

4. Configure the source Standalone server as a Security Gateway:

   1. [Download this script](https://supportcenter.checkpoint.com/file_download?id=123608) to your computer.

   2. Transfer the script from your computer to the Standalone server to some directory (for example, */var/log/*).

   3. On the Standalone server, go to the directory with the script:

      `cd /var/log/`
   4. Run the script:

      `sh Define_as_gw.sh`
   5. Configure a one-time Activation Key to establish SIC later with the new Security Management Server after the migration:

      `cp_conf sic init <One-Time Key>`

      Write down this Activation Key.
5. Install the target dedicated Security Management Server with the applicable version.

6. On the dedicated Security Management Server, install a valid license (in SmartConsole or Command Line).

   **Important** - Make sure the license supports the required number of managed Security Gateways.
7. Transfer the exported database TGZ file (you collected on the source Standalone server) from your computer to the dedicated Security Management Server to some directory (for example, */var/log/*).

8. On the dedicated Security Management Server, import the management database:

   **Prerequisite** - You must always use the latest version of the Upgrade Tools from [sk135172](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk135172).
   1. Create the required JSON configuration file (**/var/log/mdss.json**).

      **Important** - Even if only one of the servers migrates to a new IP address, all the other servers (including all Log Servers and SmartEvent Servers) must get this configuration file. You must use the same JSON configuration file on all servers (including Log Servers and SmartEvent Servers) in the same Security Management environment.
      1. Connect to the command line on the Security Management Server.

      2. Log in to the Expert mode.

      3. Create the */var/log/mdss.json* file that contains each server that migrates to a new IP address.

         Format for migrating a single Log Server / SmartEvent Server to a new IP address:

         `[{"name":"<Name of Log Server / SmartEvent Server Object in SmartConsole>","newIpAddress4":"<New IPv4 Address of R81.20 Log Server / SmartEvent Server>"}]`  
         Show / Hide an Example   
         There are 2 servers in the R80.30 Security Management environment - the Security Management Server and the Log Server.

         The Security Management Server remains with the original IP address.

         The Log Server migrates to a new IP address.
         1. The current IPv4 address of the source R80.30 Log Server is: `192.168.10.21`

         2. The name of the source R80.30 Log Server object in SmartConsole is: `MyLogServer`

         3. The new IPv4 address of the target R81.20 Log Server is: `172.30.40.51`

         4. The required syntax for the JSON configuration file you must use on the Security Management Server and on the Log Server:

            `[{"name":"MyLogServer","newIpAddress4":"172.30.40.51"}]`
   2. Connect to the command line on the Security Management Server.

   3. Log in to the Expert mode.

   4. Go to the *$FWDIR/scripts/* directory:

      `cd $FWDIR/scripts`
   5. Import the management database:

      For more information about this command, see the [CLI Reference Guide](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=documents&product=184) for your version \> Chapter "Security Management Server Commands" \> Section "migrate_server".

      `./migrate_server import -v <Target Version> [-l | -x] /<Full Path>/<Name of Exported File>.tgz`

      Example:

      `./migrate_server import -v R81.10 -l /var/log/exported_db_standalone.tgz`
9. Reset SIC in the Security Gateway object:

   1. Connect with SmartConsole to the new Security Management Server.

   2. From the left navigation panel, click **Gateways \& Servers**.

   3. Open the object of the Security Gateway with this name:

      **gateway_split_from_\<Original Name of Standalone Object\>**
   4. Change the name of this object as needed, and reset SIC with it.

      For more information, see [sk65764 - How to reset SIC](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk65764).
10. Install the applicable Access Control Policy on each applicable Security Gateway and Cluster.

11. Delete the special Access Control rule you added on the StandAlone server before the export:

    1. Connect with SmartConsole to the target Security Management Server.

    2. In each configured Security Policy, delete the Access Control rule that allows connections from the new IP address to Security Gateways.

    3. Delete the Host object with the new IP address of the target Security Management Server.

    4. Install each updated Access Control Policy on each applicable Security Gateway and Cluster.

12. If the source StandAlone server managed dedicated Log Servers or SmartEvent Servers:

    1. Update each Log Server and SmartEvent Server with the IP address of the new dedicated Security Management Server:

       * If the software versions of the target dedicated Security Management Server and of the source StandAlone server are **the same**:

         1. Connect to the command line on each dedicated Log Server and SmartEvent Server.

         2. Log in to the Expert mode.

         3. Stop Check Point services:

            `cpstop`
         4. Change the IP address:

            `cpprod_util CPPROD_SetValue SIC ICAip 1 <IP address of the new Security Management Server> 0`
         5. Start Check Point services:

            `cpstart`
       * If the software versions of the target dedicated Security Management Server is **higher** than the version of the source StandAlone server:

         * Upgrade the Log Servers and SmartEvent Servers to the same version as the target dedicated Security Management Server.

    2. Install the database on the target dedicated Security Management Server:

       1. In SmartConsole, click **Menu** \> click **Install database**.

       2. Select all objects.

       3. Click **Install**.

       4. Click **Close**.

13. On the target dedicated Security Management Server:

    `evstop; evstart`
14. At this time, the new Security Management Server object is a clean object with only the default Software Blades enabled.

    To enable additional Software Blades on the Security Management Server:
    1. In SmartConsole, from the left navigation panel, click **Gateways \& Servers**.

    2. Open the Security Management Server object.

    3. From the left tree, click **General Properties**.

    4. On the **Management** tab, select the applicable Software Blades.

    5. Click **OK**.

    6. In SmartConsole, in the top left corner, click **Menu** \> **Install database**.

    7. Select all objects.

    8. Click **Install**.

### Migration Procedure from a Standalone environment to a Distributed environment - separate Multi-Domain Security Management Server and Security Gateway {#MigrationProcedure2}

Show / Hide this section   

**Important** - Make sure to perform the procedure while you have physical access to the servers (not over VPN).

Minimum required Upgrade Tools packages ([sk135172](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk135172)):

* For R81.20 - Build 997000574 and higher
* For R81.10 - Build 996000447 and higher

Procedure:

1. Back up the current management database on the Standalone server.

   1. Save a snapshot of your source Standalone server.

      This backs up the entire configuration.

      See the [Gaia Administration Guide](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=documents&product=184) for your version \> Chapter "Maintenance" \> Section "Snapshot Management".
   2. Save a backup of your source Standalone server.

      This file lets you extract the most important configuration easily.

      See [sk108902 - Best Practices - Backup on Gaia OS](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk108902) and the [Gaia Administration Guide](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=documents&product=184) for your version \> Chapter "Maintenance" \> Section "System Backup".
   3. Collect the CPinfo file from your source Standalone server (see [sk92739](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92739)).

      This file lets you see the most important configuration easily with the DiagnosticsView tool (see [sk125092](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk125092)).
2. Because the target server has a different IP address than the source server, you must prepare the source database before the export.

   In SmartConsole connect to the source Domain Management Server:
   1. Create a new Host object with the new IP address of the target Domain Management Server.

   2. In each configured Security Policy, add a new Access Control rule that allows connections from the new IP address to Security Gateways:

      |----------------------------------------------------------------------------|---------------------------------|--------------------------|
      | Source                                                                     | Destination                     | Services \& Applications |
      | Host object with the new IP address of the target Domain Management Server | Each Security Gateway / Cluster | `CPD` `FW1` `FW1_CPRID`  |

      These are the predefined services:
      * `CPD` - TCP port 18191

      * `FW1` - TCP port 256

      * `FW1_CPRID` - TCP port 18208

   3. Install each updated Access Control Policy on each applicable Security Gateway and Cluster.

3. Export the current management database from the Standalone server.

   **Prerequisite** - You must always use the latest version of the Upgrade Tools from [sk135172](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk135172).
   1. Connect to the command line on the Standalone server.

   2. Log in to the Expert mode.

   3. Export the management database:

      For more information about this command, see the [Management API Reference](https://sc1.checkpoint.com/documents/latest/APIs/index.html#introduction) for your version \> from the top toolbar, select your API version \> search for "`export-management`".

      `mgmt_cli export-management version "<Target Version>" file-path "/<Full Path>/<Name of Exported File with File Extension>" is-smc-to-mds true --domain 'System Data' --format json`

      Example:

      `mgmt_cli export-management version "R81.10" file-path "/var/log/Standalone_DB_exported.tgz" is-smc-to-mds true --domain 'System Data' --format json`
   4. Transfer the exported database TGZ file from the source Standalone server to your computer.

4. Configure the source Standalone server as a Security Gateway:

   1. [Download this script](https://supportcenter.checkpoint.com/file_download?id=123608) to your computer.

   2. Transfer the script from your computer to the Standalone server to some directory (for example, */var/log/*).

   3. On the Standalone server, go to the directory with the script:

      `cd /var/log/`
   4. Run the script:

      `sh Define_as_gw.sh`
   5. Configure a one-time Activation Key to establish SIC later with the new Security Management Server after the migration:

      `cp_conf sic init <One-Time Key>`

      Write down this Activation Key.
5. Get the target dedicated Multi-Domain Security Management Server with the applicable version.

   You can do one of these:
   * Install a new server

   * Use an existing server

6. On the dedicated Multi-Domain Security Management Server, install a valid license (in SmartConsole or Command Line).

   **Important** - Make sure the license supports the required number of Domains.
7. Transfer the exported database TGZ file (you collected on the source Standalone server) from your computer to the dedicated Multi-Domain Security Management Server to some directory (for example, */var/log/*).

8. On the dedicated Multi-Domain Security Management Server, import the management database:

   **Prerequisite** - You must always use the latest version of the Upgrade Tools from [sk135172](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk135172).
   1. Connect to the command line on the Multi-Domain Security Management Server.

   2. Log in to the Expert mode.

   3. Import the management database:

      **Important** - Do **not** create the Domain manually. This API call creates a new Domain, creates a new Domain Management Server, and imports the source database.

      For more information about this command, see the [Management API Reference](https://sc1.checkpoint.com/documents/latest/APIs/index.html#introduction) for your version \> from the top toolbar, select your API version \> search for "`import-management`".

      `mgmt_cli import-management domain-name "<Name of New Domain>" domain-server-name "<Name of New Domain Management Server>" domain-ip-address "<IPv4 Address of New Domain>" file-path "/<Full Path>/<Name of Exported File with File Extension>" --domain 'System Data' --format json`

      Example:

      `mgmt_cli import-management domain-name "Domain1" domain-server-name "Domain1_Server" domain-ip-address "192.0.2.1" file-path "/var/log/Standalone_DB_exported.tgz" --domain 'System Data' --format json`
9. Reset SIC in the Security Gateway object:

   1. Connect with SmartConsole to the new Domain Management Server.

   2. From the left navigation panel, click **Gateways \& Servers**.

   3. Open the object of the Security Gateway with this name:

      **gateway_split_from_\<Name of New Domain Management Server Object\>**
   4. Change the name of this object as needed, and reset SIC with it.

      For more information, see [sk65764 - How to reset SIC](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk65764).
   5. Install the Access Control Policy on this Security Gateway.

10. Install the applicable Access Control Policy on each applicable Security Gateway and Cluster.

11. Delete the special Access Control rule you added on the StandAlone server before the export:

    1. Connect with SmartConsole to the target Domain Management Server.

    2. In each configured Security Policy, delete the Access Control rule that allows connections from the new IP address to Security Gateways.

    3. Delete the Host object with the new IP address of the target Domain Management Server.

    4. Install each updated Access Control Policy on each applicable Security Gateway and Cluster.

12. In the context of the Domain Management Server, restart the SmartEvent services:

    1. Go to the context of the new Domain Management Server:

       `mdsenv <IP Address or Name of Domain Management Server>`
    2. Restart the services:

       `evstop; evstart`
13. If the source StandAlone server managed dedicated Log Servers or SmartEvent Servers, do one of these:

    * Install a dedicated Log Server / SmartEvent Server and connect it to the Multi-Domain Security Management Server.

    * Install a dedicated Multi-Domain Log Server and configure the applicable Domain Log Server.

14. At this time, the new Domain Management Server object is a clean object with only the default Software Blades enabled.

    To enable additional Software Blades on the Domain Management Server:
    1. In SmartConsole, from the left navigation panel, click **Gateways \& Servers**.

    2. Open the Domain Management Server object.

    3. From the left tree, click **General Properties**.

    4. On the **Management** tab, select the applicable Software Blades.

    5. Click **OK**.

    6. In SmartConsole, in the top left corner, click **Menu** \> **Install database**.

    7. Select all objects.

    8. Click **Install**.

### Changing References to the Security Gateway Object {#ReferencesToSecurityGateway}

During the database migration, a new object is created for the new Security Management Server / Domain Management Server.

All references to the original Standalone object will point to the new Security Gateway object (except for the "**Send Logs and Alerts**" configuration in the managed Security Gateway objects).

If some of these references must point to the new Security Management Server / Domain Management Server object, you must change the configuration manually.

**Important** - This procedure applies to both migration scenarios - to a Security Management Server and to a Multi-Domain Security Management Server.
> **To change the references to the Security Gateway object in Security Policies:**  
> Show / Hide this section   
> > 1. Right-click the Security Gateway object and click **Where Used**.
> >
> > 2. In the **Where Used** window, click the **Policies** tab.
> >
> > 3. In the top right corner, click **Replace**.
> >
> > 4. Select the object of the new Security Management Server / Domain Management Server.
> >
> > 5. On the **Policies** tab, select the applicable rules.
> >
> > 6. Click **Replace**.
> >
> > 7. Close the **Where Used** window.
> >
> > 8. Install the Access Control Policy on all managed Security Gateways.
>
> **To change the references to the Security Gateway object in Legacy configuration:**  
> Show / Hide this section   
> > 1. Right-click the Security Gateway object and click **Where Used**.
> >
> > 2. In the **Where Used** window, lick the **Legacy objects** tab.
> >
> > 3. Write down where the Security Gateway object is used.
> >
> > 4. Close the **Where Used** window.
> >
> > 5. In SmartConsole, from the left navigation panel, click **Manage \& Settings** \> **Blades**.
> >
> > 6. In the applicable section, click **Configure in SmartDashboard**.
> >
> > 7. In the applicable place in SmartDashboard:
> >
> >    1. Select the object of the new Security Management Server / Domain Management Server.
> >
> >    2. Remove the Security Gateway object on that page.
> >
> > 8. In SmartDashboard, from the top, click **Menu** \> **File** \> **Update**.
> >
> > 9. Close SmartDashboard.
> >
> > 10. In SmartConsole, install the Access Control Policy on all managed Security Gateways.
>
> **To change the references to the Security Gateway object in other objects:**  
> Show / Hide this section   
> > 1. Right-click the Security Gateway object and select **Where Used**.
> >
> > 2. In the **Where Used** window, click the **Objects** tab.
> >
> > 3. Double-click the applicable object.
> >
> > 4. Select new Security Management Server / Domain Management Server object on the applicable page.
> >
> > 5. Remove the Security Gateway object on that page.
> >
> > 6. Click OK.
> >
> > 7. Close the **Where Used** window.
> >
> > 8. Install the Access Control Policy on all managed Security Gateways.

### Limitations {#Limitations}

> These migration procedures do not support Full High Availability clusters (Full HA).

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
