Contact Us 1-800-596-4880
  1. Homepage
  2. CloudHub 2.0
  3. Migrate from CloudHub to CloudHub 2.0

  4. Step 4. Validate and Switch Traffic

Validate and Switch Traffic

Validate a CloudHub 2.0 app after deployment by switching traffic in stages, monitoring health and rollback thresholds, updating DNS, and completing the cutover.

The process has two phases.

  1. Switch Traffic — Identify your traffic source, shift traffic in stages, and watch for rollback conditions.

  2. Validate and Complete the Cutover — Verify the migration, update DNS, fail over the DLB, and decommission the CloudHub application.

Contact Support for Migration Issues

If you encounter issues during or after traffic switching, gather the following information before contacting MuleSoft Support.

  • Org ID, environment name, and control plane/region (e.g., usa-e1, deu-c1.n).

  • CloudHub 1.0 application name and CloudHub 2.0 deployment ID.

  • Private space name and ID.

  • Timestamps with timezone of when the issue occurred.

  • x-request-id header values from failed requests (if applicable).

  • Replica status and reason (from the CloudHub 2.0 application’s Deployments tab).

  • DLB name and failover status.

  • Traffic switch percentage at the time the issue occurred.

Include this information in your support case to help engineering teams diagnose network, routing, and application state issues quickly.

See Also