You cannot delete CH 1.0 VPC after it upgraded to CH 2.0 (Private Space) from Runtime Manager UI

1. After migrating all your applications to CH 2.0 (Private Space), ensure that there are no CH 1.0 applications with the status Running, Stopped, or Deployed. If so, please delete them.

2. Also, ensure no active DLBs are attached to the CH 1.0 VPC, and delete if found.

3. The network connections (VPNs, Transit Gateway) will automatically gets deleted once VPC is deleted with PATCH command

 
4. Run the below PATCH commands if Private Space is deployed on US control plane 

Option 1 : With Validation (default):

curl -X PATCH 'https://anypoint.mulesoft.com/runtimefabric/api/organizations/{Anypoint-Org-ID}/migration/privatespaces/{privateSpaceID}/migrationComplete' -H 'Authorization: Your Bearer Token'

Option 2 : To bypass validation (force=true):

curl -X PATCH 'https://anypoint.mulesoft.com/runtimefabric/api/organizations/{Anypoint-Org-ID}/migration/privatespaces/{privateSpaceID}/migrationComplete?force=true' -H 'Authorization: Bearer YOUR_BEARER_TOKEN'

5. If Private Space is deployed on EU control plane, use the below PATCH command.

curl -X PATCH 'https://eu1.anypoint.mulesoft.com/runtimefabric/api/organizations/{Anypoint-Org-ID}/migration/privatespaces/{privateSpaceID}/migrationComplete' -H 'Authorization: Bearer Token'

6. Once the PATCH command runs successfully, you should no longer see the CH 1.0 VPC from Anypoint Runtime Manager.