Docs â€ē Guides â€ē Migration

Migrating to CloudNexus Infrastructure

A comprehensive, step-by-step guide to transitioning your applications, databases, and workloads to CloudNexus with minimal downtime.

📅 Updated: March 2025 | ⏱ī¸ Estimated Time: 45-90 mins

Overview

Migrating to CloudNexus allows you to leverage our global CDN, auto-scaling Kubernetes clusters, managed databases, and enterprise-grade security. This guide covers a standard migration path for typical web applications and microservices.

ℹī¸
Zero-Downtime Strategy

We recommend a blue-green deployment approach. Maintain your existing environment until CloudNexus is fully validated.

Prerequisites

Before beginning, ensure you have the following ready:

  • Active CloudNexus account with verified billing
  • CloudNexus CLI installed (cnx --version)
  • Valid API key with admin or deployer scope
  • Root/SSH access to current infrastructure
  • Database dump or replication credentials
  • DNS management access for your domain
Terminal
cnx auth login --key $CNX_API_KEY
cnx config set region us-east-1

Step 1: Environment Setup

Initialize your project structure and configure environment variables. CloudNexus uses a declarative cnx.yaml manifest for reproducible deployments.

Terminal
cnx init --template kubernetes-managed
cp .env.example .env
# Populate .env with your database credentials and API secrets
⚠ī¸
Secrets Management

Never commit .env or raw credentials to version control. Use cnx secrets import to inject them securely into the platform.

Step 2: Data & State Migration

Database Transfer

For PostgreSQL/MySQL, we recommend logical replication or snapshot import depending on dataset size.

Terminal
# Create managed database instance
cnx db create --engine postgresql-15 --tier standard-2 --name prod-db

# Import from remote host (zero-downtime replication)
cnx db import --from postgres://old-host:5432/app --to prod-db --replicate

Object Storage Sync

Sync S3/MinIO buckets using our optimized transfer tool. It handles multipart uploads and bandwidth throttling automatically.

Terminal
cnx storage sync --src s3://legacy-bucket --dst cnx://app-assets --concurrency 16

Step 3: Compute & Services

Deploy your application containers. CloudNexus handles container registry, build pipelines, and service mesh configuration automatically.

Terminal
cnx deploy --env production --auto-scale true --min-replicas 2
# Output: Deploying to cnx-prod-app... [✓] Health checks passed

Verify the service endpoint:

Terminal
curl -I https://api-staging.cnx.app/health
HTTP/2 200
x-cnx-region: us-east-1
x-response-time: 14ms

Step 4: DNS Cutover

Once validation is complete, update your DNS records to point to CloudNexus Anycast IPs. We recommend lowering TTL 24 hours before cutover.

  1. Update your provider's A or CNAME records to *.cnx.app
  2. Verify SSL/TLS provisioning (auto-issued via Let's Encrypt integration)
  3. Monitor propagation using dig or DNS checker tools
✅
CDN Activation

Cloudflare/CloudNexus edge nodes will automatically cache static assets and optimize TCP handshakes for global users.

Validation & Monitoring

Post-migration, run our automated health suite and enable observability dashboards.

Terminal
cnx validate --full --endpoint https://yourdomain.com
[✓] DNS Resolution
[✓] SSL Certificate
[✓] Route Handlers
[✓] DB Connectivity
Migration score: 100/100

Access real-time metrics at https://dashboard.cnx.app/metrics. Set up alerting for CPU > 80% or error rate > 1%.

Troubleshooting

🚨
Common Issues

Connection refused on port 5432: Ensure security groups allow inbound traffic from CloudNexus IP ranges.

SSL handshake failed: Certificate provisioning takes ~60s. Retry or check domain validation records.

  • Rollback: Run cnx deploy rollback --version previous to instantly revert traffic.
  • Logs: Stream live logs with cnx logs tail --follow --service prod-app
  • Support: Contact support@cloudnexus.dev or join our Discord community for migration assistance.
← Previous Getting Started with CLI Next → Auto-Scaling Configuration