Cloud infrastructure and services
Move to the cloud, then run it well
Cloud strategy from migration to day-to-day operations, across AWS, Azure and Google Cloud: managed operations, FinOps to keep spend in check, and cloud-native architecture that scales.
On-premises rack
- Customer websiteWave 1
- ERPWave 1
- Orders databaseWave 2
- File sharesWave 2
- Nightly batchWave 3
- Old intranetRetire
AWSeu-west-2, London
Wave 1 Move as it is
Wave 2 Managed services
Wave 3 Rebuilt cloud-native
- Monitoring
- Patching
- Backups
- Spend by team
Six workloads in the rack: five to move, one to retire. Pick a cloud and migrate.
Sample estate. Region shown is the provider’s London region.
Two halves of the same job
Move
Get there in planned waves, and build for the cloud you land in.
Cloud migrations
Moving applications and data to the cloud in planned waves, choosing for each one whether to move it as it is, adapt it or rebuild it.
Cloud-native architecture
Designing systems around managed services, containers and automation so they scale and recover on their own.
Run
Keep it healthy every day, and keep the bill in check.
Managed operations
Running your cloud estate day to day: monitoring, patching, backups and changes.
FinOps optimisation
Making cloud spend visible by team and service, and cutting waste such as idle and oversized resources.
Plan a migration
Choose a route for each application in a sample estate. The plan groups them into waves, quickest moves first.
- Customer websiteStateless, containerised
- ERPVendor-supported on VMs
- Orders databasePostgreSQL on a VM
- Nightly batchCron jobs on one server
- Old intranetReplaced by SharePoint
- File shares6 TB of documents
Wave 1 Quick moves
- Customer website
- ERP
- Orders database
- Nightly batch
- Old intranet
- File shares
Wave 2 Managed services
- Customer website
- ERP
- Orders database
- Nightly batch
- Old intranet
- File shares
Wave 3 Rebuilds
- Customer website
- ERP
- Orders database
- Nightly batch
- Old intranet
- File shares
Switch off No move needed
- Customer website
- ERP
- Orders database
- Nightly batch
- Old intranet
- File shares
Sample estate. Real plans also weigh dependencies, risk and licences.
Where we start
Before the first wave
Every engagement opens with a discovery assessment. For cloud work, these are the first questions.
The applications and data to move, and what depends on what
Your target clouds: AWS, Azure, Google Cloud or more than one
Current spend, and how it is tracked
Uptime, security and data residency requirements
Three phases, planned like a migration
01Discovery assessment
We look at your current infrastructure, find the gaps and map them to your business objectives.
02Solution design
Our architects design a solution for your technical and compliance requirements, sized to grow.
03Implementation
We deploy and integrate with zero-downtime methods, keeping disruption to your daily operations to a minimum.
Bar lengths show the order of work, not a fixed timetable.
Questions about cloud work
Which clouds do you work with?
AWS, Microsoft Azure and Google Cloud.
What does the cloud service cover?
Migrations, managed operations, FinOps optimisation and cloud-native architecture and scaling.
How do you avoid disruption during a migration?
Moves are planned in the design phase and carried out with zero-downtime methods, to keep disruption to daily operations to a minimum.
Tell us what you want to move
We scope quickly and you speak to senior engineers from the first call.
