Watch a migration from AWS to UpCloud
Run the command to see what our agent does, step by step: on the left what it prints, on the right what it touches. Each step is explained under the diagram. A real move takes hours; this replay takes about 7 minutes. Use “Next step” or 2×/4× to go faster.
$ moveinfra report --final
Artifacts you keep (sample)
- YMLinventory.yaml14 resources mapped AWS → UpCloud, with dependencies6 KB
- TFterraform/The new environment as code: network, firewall, LB, servers, DB, storage9 files
- SHAsha256-manifest.txtHashes of every image and volume, taken on both sides: all match2 KB
- CSVdb-checksums.csv46 tables, row counts and checksums, AWS = UpCloud4 KB
- JSONobject-storage-sync.json18,450 objects copied from S3, every hash compared1.1 MB
- HTMLsmoke-tests.html12 of 12 checks passed, with response times38 KB
- MDcutover-log.mdMinute-by-minute switch: 38 s write pause, 0 errors11 KB
- MDrollback-runbook.mdHow to switch back in one command, valid for 30 days5 KB
- PDFcost-report.pdfAWS $1,284 / month → UpCloud €612 / month (sample)220 KB
- PRPull request #482In your repo: deploy target changed to UpCloudmerged
What is real here: the steps and their order are how MoveInfra moves you. Read-only access first, an inventory you can read, servers rebuilt with the same OS, databases replicated live, a short write pause for the switch, and the old setup kept in sync for 30 days. Names, sizes and prices are sample data.
AWS service icons from the official AWS Architecture Icons. AWS and the AWS logo are trademarks of Amazon.com, Inc. or its affiliates. MoveInfra is not affiliated with AWS or UpCloud.