Cloud Architecture & Migration
Moving production estates to AWS and Azure without the drama.
Migration projects fail on the things nobody planned for — the undocumented dependency, the application nobody owns, the cutover window that was always too short. Two decades of doing this in regulated environments means those get surfaced during design, not during the weekend of the move.
Work covers assessment and dependency mapping, target architecture, landing zones, identity and network design, migration execution and post-migration optimisation. Hybrid is treated as a legitimate destination rather than a failure to finish — plenty of workloads should stay where they are, and saying so is part of the job.
What this covers
- Discovery and dependency mapping before anything moves
- AWS and Azure landing zones, networking and identity
- Lift-and-shift, re-platform or re-architect — chosen per workload, with reasons
- Migration runbooks, rehearsal and rollback planning
- Post-migration cost review and right-sizing
Delivered
Career migration volume runs to thousands of workloads: 2,000 servers moved to hybrid cloud for a global energy major during a vSphere platform upgrade, thousands of virtual machines and business applications migrated for a multinational energy group, and a 50+ server AWS migration for a global airline group.
Discuss a cloud architecture & migration project
Email darren.pilkington@it-architect.uk or get in touch. Initial conversations are free and you will get a straight view on scope and feasibility.