Migration Guide

Migration Overview

Migrating to CloudNexus is designed to be seamless. Whether you're moving from AWS, Azure, Google Cloud, or a traditional data center, our Nexus Migrator tool automates the heavy lifting while giving you full control over the process.

This guide covers the end-to-end migration process, including infrastructure replication, database transfer, DNS cutover, and post-migration optimization.

💡

Pro Tip

Start with a non-production environment first to test the migration workflow before touching production workloads.

Prerequisites

Before beginning the migration, ensure you have the following:

Active CloudNexus account with verified billing
Read/Write access to your current infrastructure
Nexus CLI installed locally (nexus-cli)
Sufficient downtime window (if zero-downtime is not required)
Database credentials and connection strings

Bash

# Install Nexus CLI
curl -fsSL https://cli.cloudnexus.io/install.sh | sh

# Authenticate
nexus-cli auth login

# Verify installation
nexus-cli version
# Output: nexus-cli v2.4.1

Step 1: Assessment & Planning

Infrastructure Assessment

Run the Nexus Assessment tool to analyze your current infrastructure. This generates a detailed report with recommendations for optimal CloudNexus configurations.

Bash

# Scan existing infrastructure
nexus-cli assess \n  --source aws \n  --region us-east-1 \n  --output assessment-report.json

# Review recommendationsncat assessment-report.json

⚠️

Important

Ensure your source environment has no pending patches or uncommitted changes before scanning. This ensures the assessment reflects a stable state.

Step 2: Environment Setup

Configure CloudNexus Resources

Based on the assessment report, provision your CloudNexus infrastructure. We recommend using Infrastructure as Code (Terraform or Nexus Config) for reproducibility.

Terraform

resource "nexus_instance" "app_server" {
  name      = "production-app-01"
  type      = "nexus-nvme-8x16"
  region    = "us-east-1"
  image     = "ubuntu-22.04-lts"
  
  network {
    subnet       = "private-az1"
    auto_assign_ip = true
  }
  
  storage {
    size_gb = 200
    type    = "nvme-ssd"
  }
}

Step 3: Data Migration

Transfer Data & Databases

Use Nexus DataSync for high-speed, encrypted data transfer. For databases, we recommend the Managed Database Import feature which handles schema conversion and index rebuilding automatically.

ℹ️

Supported Database Engines

PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch, and ClickHouse. Custom engines can be migrated via raw backup restoration.

Bash

# Migrate PostgreSQL database
nexus-cli db migrate \n  --source "postgresql://src-host:5432/prod_db" \n  --target "nexus-db://us-east-1/prod-db-cluster" \n  --parallel 8 \n  --verify-checksums \n  --stream-replication

# Transfer object storage (S3 compatible)
nexus-cli sync \n  --src "s3://my-bucket" \n  --dst "nx://my-bucket" \n  --concurrency 32

Step 4: Application Cutover

DNS Cutover & Traffic Routing

Once data is synced, perform the final cutover. CloudNexus supports Blue-Green Deployment patterns, allowing you to shift traffic gradually while monitoring health metrics.

Update your DNS records to point to CloudNexus edge IPs. We recommend reducing TTL 24-48 hours before cutover.

Bash

# Configure traffic routing with 10% initial shift
nexus-cli route set \n  --domain example.com \n  --target nexus-cluster-prod \n  --weight 10 \n  --health-check /health

# Gradually increase to 100% over 15 minutes
nexus-cli route scale \n  --domain example.com \n  --weight 100 \n  --interval 15m

Step 5: Verification

Post-Migration Validation

After cutover, run the verification suite to ensure data integrity, application functionality, and performance baselines are met.

Bash

# Run automated verification
nexus-cli verify \n  --target production \n  --checks data-integrity,app-health,perf-baseline \n  --report post-migration-report.html

# Expected output:
# ✅ Data Integrity: 100% records matched
# ✅ App Health: All endpoints responding < 50ms
# ✅ Performance: 2.3x faster than source

Pre-Flight Checklist

Use this checklist to ensure you're ready for migration:

✓ Assessment report reviewed and approved by stakeholders

✓ CloudNexus infrastructure provisioned and tested in staging

✓ Database connections and credentials validated

✓ DNS TTL reduced to 300s or less

✓ Rollback plan documented and tested

✓ Monitoring alerts configured for target environment

✓ Team notified of maintenance window

Need Assistance with Migration?

Our Migration Engineers can handle the entire process for you, or provide real-time support during your cutover.

Contact Migration Team View Migration FAQ