LeadershipMigrationFeatured
The Cloud Migration That Almost Broke Our Export Service
3 weeks to migrate file storage from AWS S3 to Azure. The codebase has a storage abstraction layer. It looks clean. It isn't.
Situation
You're the lead engineer with 3 weeks to migrate file storage from AWS S3 to Azure Blob Storage before the AWS contract renewal. The codebase has a storage abstraction layer — an enum-routed service that wraps provider-specific calls. It looks like a clean swap. Your PM is confident. You're not sure yet.
Stakes
- Hard deadline — AWS contract renewal in 3 weeks
- Customer-facing file exports will silently break if any storage path is missed
- No equivalent staging environment for the Azure side
3 weeks. S3 to Azure. The abstraction layer is there. How do you start?