On this page
Migrate workloads & plan an exit
Inventory dependencies, rehearse a data transfer and define export and deletion before cutover.
Use this planning guidance now for an inquiry and pilot proposal. Service commitments require a written agreement.
Before you start
Identify the current application owner and source of configuration/data. Migration assistance, destination capacity and export/deletion terms must be agreed for the pilot. Avoid making a live customer domain the first test.
Inventory more than Kubernetes YAML
- ✓Manifest or Helm/GitOps source, image digests, architecture and application configuration.
- ✓Data stores, volume types/access modes, export format and application/schema compatibility.
- ✓DNS, TLS, public/private routes, external allowlists, webhooks, queues and scheduled jobs.
- ✓Credential renewal, identity integration and the people needed to approve access at the destination.
Do not copy live resource status, internal addresses or source-cluster bindings blindly. Start from your owned declarative configuration. Namespaces, storage class and ingress settings must match the agreed destination rather than the source platform.
Rehearse with a safe data copy
- 01
Prepare the target
Confirm namespace access, capacity, registry credentials and internal connectivity before restoring data.
- 02
Transfer reviewed configuration
Validate and review the manifests, provision only the agreed resources and deliver new credentials through the agreed secure channel.
- 03
Restore and test the application
Use a controlled data copy, disable live side effects and test authentication, data consistency and a representative workload. Measure time and record gaps.
Make cutover reversible where possible
Agree the write-freeze or synchronization strategy, final export, DNS changes, verification and who makes the go/no-go decision. Record the previous destination and the conditions for returning traffic. If the new system accepts writes, routing back alone may lose or split data; the rollback plan must address those writes.
Domains, ingress & TLS →Plan the exit before you need it
| Before ending the pilot | Evidence to retain |
|---|---|
| Confirm termination and final costs | Agreed notice/term, final resource billing and a shutdown schedule. |
| Export data and configuration | Usable copy at your destination with application/image references and recovery test. |
| Revoke access and integrations | Named owners for credentials, webhooks, DNS and operator access. |
| Authorize deletion | Scope, date and agreed confirmation/retention exceptions, including backup copies. |
Use this guide within your agreed pilot scope. Kubernetes examples are not evidence of a generally available Cloud capability.