Contact Us 1-800-596-4880
  1. Homepage
  2. CloudHub 2.0

  3. Migrate from CloudHub to CloudHub 2.0

Migrate from CloudHub to CloudHub 2.0

Migrate CloudHub applications and infrastructure to CloudHub 2.0. Review the platform differences, choose a migration path, and complete each step in order.

Migration Journey Overview

Migrate from CloudHub to CloudHub 2.0 in these five steps.

  1. Plan the Migration. Audit apps, assess entitlements, estimate timelines, and choose a migration strategy.

  2. Prepare Infrastructure. Create a private space or upgrade an eligible VPC, then configure network connectivity.

  3. Migrate Applications. Update app code, deploy to CloudHub 2.0, and configure app properties.

  4. Validate and Switch Traffic. Switch traffic gradually, monitor for issues, and complete DNS cutover.

  5. Finalize and Decommission. Decommission CloudHub resources and release entitlements.

Choose Your Migration Path

Choose the path that fits your infrastructure.

  • Create a new private space if your VPC doesn’t meet upgrade eligibility requirements or if CloudHub 2.0 needs a different CIDR block.

  • Upgrade your VPC to a private space if it meets the eligibility requirements and you need to retain the existing CIDR block and infrastructure configuration.

For eligibility criteria and help choosing a migration path, see Determine Your Migration Path. For setup procedures for each path, see Prepare Infrastructure.

Assess Migration Impacts

Before planning your migration, review the differences that can require infrastructure or application changes.

  • Infrastructure and networking: private spaces, connectivity, firewall rules, static IP addresses, load balancing, domains, and TLS.

  • Traffic routing: DLB mapping rules, ingress endpoints and paths, certificates, access-control rules, and traffic switching behavior.

  • App deployment: Mule runtime compatibility, deployment configuration, app properties, worker-to-replica sizing, clustering, and alerts.

  • App behavior: persistent VM queues, logging, internal app communication, injected HTTP headers, and connection timeout behavior.

For the complete CloudHub and CloudHub 2.0 comparison, including DLB-to-ingress migration considerations, see Compare CloudHub and CloudHub 2.0.

See Also