Services DevOps & cloud
Cloud migration
A planned move from legacy hosting to the cloud, sequenced and rehearsed to avoid customer-facing downtime.
At a glance
- Includes
- Inventory, migration plan, cutover rehearsals, data moves and a written rollback plan
- Works with
- AWS, Microsoft Azure and Google Cloud, from on-premises or other hosting
- Delivered as
- A phased plan and the migrated workloads, in your own cloud accounts
- Starts with
- An inventory of your applications, dependencies and data
Fit
Is this right for you?
Usually the right call when one of these sounds familiar.
Hosting that is ageing
Hardware or contracts are reaching their end.
A move nobody wants to start
The risk of downtime keeps it on the list, not in progress.
Systems nobody fully understands
Dependencies between applications are not written down.
Costs you cannot compare
You do not know what the move would cost or save.
Not the right service? A new environment from scratch: Cloud infrastructure. Releasing changes after the move: CI/CD pipelines.
Scope
Scope and what you get
The move is planned in writing and carried out in stages you have agreed. Each piece of work has a matching thing you receive.
- What we do
Inventory and dependencies
A review of applications, data, integrations and the links between them.
What you receiveA map of what you run
A written inventory showing what exists, what depends on what and what can move first.
- What we do
Migration plan
Workloads ordered by risk, with the lowest-risk moves first and a method chosen for each.
What you receiveA phased plan
Stages, dates and responsibilities agreed with you before anything moves.
- What we do
Cutover rehearsals
Practice runs of the move in a test environment, timed and reviewed.
What you receiveCutovers without surprises
Rehearsed steps and a written timetable for each move.
- What we do
Data transfer and rollback
Data moved and checked at the destination, with a way back if a check fails.
What you receiveA way back
A rollback plan written before each cutover and kept until the move is accepted.
Use cases
Relevant use cases
Practical situations where this service is put to work. Open a card to see how it applies.
Leaving an ageing hosting provider
An orderly move of applications and data to a cloud platform before hardware or contracts run out.
- Everything inventoried before anything moves
- Moves ordered so the least critical go first
- The old environment kept until the new one is accepted
Moving one application at a time
A staged migration where each application moves, is checked and is signed off before the next begins.
- One workload per stage, with its own plan
- Dependencies moved or bridged together
- Review with your team after every stage
Moving a database with little interruption
Data copied, kept in step with the live system and switched over in a short, rehearsed window.
- Copy and synchronisation tested in advance
- Checks comparing source and destination data
- A written rollback plan for the switch
Sample use cases, drafted as placeholders. The Plethora team confirms the final list.
Process
How it works
Four stops, agreed with you as we go. Each shows what we do and what we need from you.
Assess
We doWe inventory your applications, data and dependencies, and note what makes each one hard or easy to move.
You doYou share access to your systems and the people who know them.
Plan
We doWe propose the order of moves, the method for each workload and the cutover windows.
You doYou approve the plan and tell us when the business can accept a change.
Migrate
We doWe rehearse each move, then carry it out stage by stage, checking the result each time.
You doYou test the migrated workloads and confirm each stage before we continue.
Run
We doWe hand over the new environment with documentation and retire the old one when you agree.
You doYou decide when the old environment is switched off.
Quality
Quality and handover
How the work is checked, accepted and passed to you.
Rehearsed before the real move
Each cutover is practised in a test environment first.
A rollback for every stage
Written before the move and kept until the stage is accepted.
Data checked after transfer
Source and destination are compared, so you know nothing was lost.
A defined handover
Documentation, access and the retirement plan for the old environment.
Tools
Tools and technology
Tools we use in delivery. We choose them to suit your team, and the list does not imply any partnership. Logos belong to their owners.
- AWS
- Microsoft Azure
- Google Cloud
- Terraform
- Docker
- Kubernetes
Engagement
Engagement and cost factors
Ways to work with us
A scoped project
A defined migration, planned, carried out and handed over.
A team alongside yours
Our engineers work with yours through the move, in your tools.
Ongoing support
We keep tuning and supporting the new environment after the move.
What shapes scope, timing and cost
- How many applications and databases are moving
- How long the current systems have been running, and how well they are documented
- How much interruption the business can accept
- Which cloud platform you are moving to
- Security, compliance and data-location requirements
Scope and cost are confirmed with you in writing before work starts.
FAQ
Frequently asked questions
We plan every move to avoid customer-facing downtime, and rehearse it first. Where a short interruption is unavoidable, we agree the window with you in advance.
No. Some workloads are better left where they are, or moved later. The plan says which and why.
Often, yes. The inventory is where we find out what exists and what it depends on, before we commit to a plan.
It stays available until you accept the new one. Retiring it is a separate step that you approve.
Move without the surprises. Start with a conversation.
Tell us what you run today and we will come back with next steps.
Talk to usRelated