tencent cloud

This document describes how to migrate from your resources from the classic network to VPC.

Note：

Before switching the network, you need to create a VPC in the same region as the classic network instance to be migrated and create a subnet in the same AZ as the instance. For more information, see Creating VPCs.

Tencent Cloud provides the two migration solutions below:

• Migrating a ingle instance: Choose this if you only need to migrate instances one by one.
• Hybrid access: if your business involves CVM, CLB, and TencentDB instances, you can use this solution to ensure a smooth business migration.

Migrating a Single Instance

You can easily migrate a instance from the classic network to a VPC. See below for details.

Note：

If you want to keep the resource IP addresses unchanged after the network switch, try to create a VPC that covers the classic network IP.

• Create a private DNS service and resolve its domain name. After migrating the resources to a VPC, use Tencent Cloud Private DNS.
• Access using the public IP.

Hybrid Access Solution During the Migration

Hybrid access means the services being migrated can access both the classic network and a VPC. Tencent Cloud provides the following hybrid access solutions:

• TencentDB: the accessibility of classic network IP and VPC IP ensures the hybrid access at the TencentDB instance level.
  
• COS: access through domain name naturally provides the hybrid access capability.
• CVM:
  • Classiclink: allows the classic network-based CVMs to interconnect with VPC resources such as CVM, TencentDB, and CLB instances.
  • Peering connection: allows the instances in a VPC to communicate with resources in the classic network (except CVMs).
    

    Note：

    • To use peering connection, submit a ticket.
    • To configure Classiclink, see Classiclink.
    • For migration of CLB instances, see Example: Migrating a Public Network CLB and Example: Configuring Hybrid Access for a Private Network CLB.