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

# sk175823 - Migration from NSX-V to NSX-T (V2T)

| Property | Value |
|----------|-------|
| Solution ID | sk175823 |
| Date Created | 2021-10-25 |
| Last Modified | 2026-04-12 |
| Technical Level | General |
| Products | Cloud Firewall |
| Versions | R81 (EOS), R81.10 (EOS) |
| OS | Linux, Gaia |
| Platform | VMWare NSX, VMWare NSX-T |

## Solution

**Table of Contents:**

* Introduction
* V2T Migration
* Known Limitations
* Related Documentation

Introduction {#Introduction}
----------------------------

This SK article describes how to migrate an NSX-V environment to NSX-T with V2T.  

NSX-T offers a Migration Coordinator tool that migrates your vSphere environment with NSX-V installed on it to NSX-T. The Migration Coordinator imports all the configuration from NSX-V and copies it to NSX-T.  

From the Check Point side, you must replace the objects in the Security Management policy configured in NSX-V before the migration with their counterparts in NSX-T. The Cloud Management Extension utility (CME) does this replacement.  

![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk175823/img1202110211639162.png)  
source: [blogs.vmware.com](https://blogs.vmware.com/)

**Note** : NSX-V is End of Life. Before you upgrade to R81.20 Security Management, upgrade from NSX-V to NSX-T.

V2T Migration {#Migration}
--------------------------

### Step 1 - Before the Migration

Show / Hide this section  

Check Point Prerequisites  

* Make sure your vCenter environment is fully configured with NSX-V.  

* Make sure to configure NSX-V, NSX-T, and vCenter Data Center objects on the Security Management through SmartConsole:

  #### ![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk175823/img3202110251340201.png)

* Install the CME on the Security Management.

**Note:** It is not mandatory to deploy a Check Point CloudGuard service Gateway.  

VMware Prerequisites  

1. Install NSX-T (the Migration Coordinator is built into NSX-T).  

2. Install NSX-T Edges (do not configure).  

3. Provide a TEP pool.  

4. Create a Compute Manager that points to the vCenter connected to NSX-V.  

5. Make sure NSX-V is in a stable, healthy state and with no pending changes. Changes are not allowed during the migration.

**Note:** For more information, refer to the [VMware V2T migration guide](https://blogs.vmware.com/networkvirtualization/2020/01/migration-from-vmware-nsx-v-to-t.html/).

### Step 2 - Migration Configuration

Show / Hide this section  
![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk175823/img2202110211643013.png)
source: <blogs.vmware.com>  

1. Log in to the NSX-T WebUI and go to **System** \> **Migrate** .  

2. Click on **GET STARTED** .  

3. Select the NSX-V and vSphere from which to migrate and click on **start**.

**Notes** :  

* The migration imports all the applicable configuration.  

* If there are issues/warnings, resolve them first and then click on **start** to start the actual migration. You must resolve all issues before the migration runs.  

* The steps above take some minutes.

### Step 3 - Replace NSX-V Objects with NSX-T Objects in Security Management

Show / Hide this section  
When the migration configuration phase is done:  

1. Log in to the Security Management through SSH.  

2. Run the "`cme_menu`"command in the Expert mode.  

3. Go to ? **4) VMware** ? **1) NSXT** ? **1) Manage NSX-T Controller** ? **6) Migrate NSX-V Policy to NSX-T** ? **1) Migrate NSX-V Policy to NSX-T** ? select the NSX-V data-center-object you are migrating from ? select the NSX-T data-center-object you are migrating to ? select **yes** ? select **publish changes** .  

4. In the **Security Policies** section of SmartConsole, NSX-T objects are added to the rules alongside the NSX-V objects. These are the migrated "copies" of the objects in NSX-T.  

5. To delete the NSX-V objects, run the "`cme_menu`" in the Expert mode from the Security Management and go to:  
   **4) VMware** ? **1) NSXT** ? **1) Manage NSX-T Controller** ? **6) Migrate NSX-V Policy to NSX-T** ? **2) Remove NSX-V Objects From Policy** ? **Enter the NSX-V DC object name** .  

   This deletes the NSX-V objects from the policies.

### Step 4 - Complete the Migration

Show / Hide this section  
Go to the NSX-T WebUI and complete the Migrate Edges and Migrate Hosts phases.  

You have migrated your objects and configurations from NSX-V to NSX-T. You are ready to deploy a service in NSX-T.

Known Limitations {#Known Limitations}
--------------------------------------

* This feature is not supported on Multi-Domain Management Servers.  

* NSX-V object removal through the CME: Starting in R81.10, the new default value in the Security Policy Rulebase cell, after the removal of the last object, is **Any** (not **None** ). This results in a validation error: "T*his rule will never be matched.* "   

  To remove NSX-V objects with the CME (the object is the last object in the rule):  

  1. Go to **Manage \& Settings** -\> **Policy Settings** .  

  2. Change the Security access defaults of the Source and Destination from **None** to **Any** .  

  3. Change the setting **After removing the last object in a cell** to **Add the object according to the rulebase cell default**.

  > ![](https://sc1.checkpoint.com/sc//SolutionsStatics/sk175823/Untitled202208031832471.png)

Related Documentation {#Documentation}
--------------------------------------

* [Migration from VMware NSX for vSphere to NSX-T](https://blogs.vmware.com/networkvirtualization/2020/01/migration-from-vmware-nsx-v-to-t.html/)

---

# 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
