Skip to main content

​
Migrate to Different Cloud

migrate this application to DigitalOcean
Move your entire application to a different cloud provider. → Workload Migration

​
What Gets Migrated

  • ✅ Containerized services
  • ✅ Application code
  • ✅ Configuration
  • ✅ Networking setup
  • ⚠️ Database data (coming soon - currently manual)

​
Compare Before Migrating

how much would this cost on DigitalOcean instead of AWS?
Check cost savings before migrating. → Multi-Cloud Support

​
Partial Migration

migrate to DigitalOcean but keep the database on AWS
Move some components, keep others where they are.

​
What Monk Does

  1. Provisions new infrastructure - Creates matching resources on target cloud
  2. Deploys workloads - Starts your application on new cloud
  3. Updates DNS - Points domain to new infrastructure (if using Monk-managed DNS)
  4. Verifies - Checks everything works
  5. Cleanup - Removes old resources after confirmation

​
What You Provide

Credentials:
  • Target cloud provider credentials
Confirmation:
  • Approve resource provisioning
  • Confirm deletion of old resources

​
Migration Reasons

Cost savings: 
save 30-60% by switching providers
Better services: 
access provider-specific features
Geographic expansion: 
reach new regions
Compliance: 
meet data residency requirements

​
Timeline

Workload migration: 15-30 minutes for most apps Database data migration: Currently manual (automatic migration coming soon)

​
Next Steps