---
schema_version: "1"
id: abd38889e03127f03d1ba8c1afa17d585dde66adfc727db6fdddb5723ef83a73
title: CloudHub to CloudHub 2.0 Migration Completion
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/cloudhub/ch-ch2-migration-completion.md
canonical_url: https://docs.mulesoft.com/cloudhub/ch-ch2-migration-completion
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 0f341d8b7e4a576d9cf95a8004439305548eb50411b3fc3177848347d09c305a
description: MuleSoft Documentation Site
latest: true
---
---
product: CloudHub
---

# CloudHub to CloudHub 2.0 Migration Completion

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

After completing the VPC upgrade and application migration phases, complete the CloudHub to CloudHub
2.0 migration process and release associated entitlements within the recommended time frame:

## Mark Upgrade as Complete

> [!WARNING] Marking the upgrade as complete is an irreversible action. This action deletes the
> original VPC, stopped DLBs, and all CloudHub 1.0 applications marked as upgraded. All traffic then
> flows through the CloudHub 2.0 private space.

Marking the upgrade as complete finishes the entire VPC upgrade process. Go to the **Upgrade** tab
and click **Mark Upgrade Complete**.

![\*Mark Upgrade Complete\* button within the Upgrade tab](/mulesoft/current/en-us/cloudhub/_images/mark-upgrade-complete.png)

After you mark the upgrade complete, CloudHub 2.0 replaces all CloudHub resources and CloudHub
assets become immutable. Perform any required changes on CloudHub 2.0.

## Entitlements for VPCs, Private Spaces, and Network Connections (VPNs/TGW)

After you complete the VPC upgrade and bring over any existing TGW and VPN network connections, your
old and new infrastructure count separately against your usage. Therefore, if your organization uses
all purchased quota, your usage can exceed the allowed quota until you move all your applications to
CloudHub 2.0 and decommission your old VPC.

Work with your account representative to plan for additional entitlements, and decommission your
CloudHub infrastructure (VPCs and associated DLBs) within six months after the upgrade to avoid
interruptions when trying to create or edit VPCs, private spaces, or network connections.

> [!NOTE] Deleting the upgraded VPC after all applications and their associated DLBs are removed
> doesn’t affect your CloudHub 2.0 Private Spaces or CloudHub 2.0 applications.

## See Also

- [CloudHub VPC to CloudHub 2.0 Private Space Upgrade](https://docs.mulesoft.com/cloudhub/vpc-upgrade)

- [CloudHub to CloudHub 2.0 Application Migration](https://docs.mulesoft.com/cloudhub/app-migration)