Cloud Migration
summary
A midmarket firm survives a ransomware attack by lifting about 40 servers and a week‑old ERP backup into public cloud and restores operations in 4–5 business days, then moves backups to cloud with object locking and a hybrid posture. Large banks migrate over years using a Cloud Business Office, standard stacks (ECS/Fargate), zero‑trust patterns and portfolio classification to avoid shadow IT and runaway costs. Practical advice: pilot, plan governance, pick providers for specific features or existing vendor relationships.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:00Personal Experience
- 4:15Difficulty of Migration
- 4:58Recovery Time
- 5:36Team
- 6:19Stress
- 6:56Carth
- 8:59Strategic change
- 10:15How long ago
- 10:44How has the cloud helped
- 12:38Establishing ownership
- 14:56Davids experience
- 16:28Why choose public or private
- 20:32Data protection
- 23:05Cloud providers
- 24:58Questions
- 29:50Advice
- 31:19Common Mistakes
- 34:23Common Mistake
- 36:45Audience Question
related talks
25mMigrate Your Enterprise Applications to the Cloud
18mMigrating Legacy Financial Systems to Cloud: Challenges and Best Practices
29mJourney through the center of migrations
50mRansomware Readiness: Backup and Recovery in the Cloud
52mMigrations: The opportunity for you and your customers
27mBeyond Cloud Migrations: Engineering for innovation at Macquarie Bank
25mNavigating Cloud Migration: Strategies for Success
08mEnabling successful MRO operations with the AWS Cloud