Skip to main content
Legia

Cloud Migration & Architecture

Legia designs workload placement in the cloud sized to your needs, then runs the migration in stages. Cost control is set up from the start, so monthly bills do not grow without explanation.

Pricing

How much does Cloud Migration & Architecture cost?

Cost splits in two: the migration work, paid once, and the monthly cloud bill, paid directly to the provider. Legia estimates both from the start so no bill shows up later.

  • Number of workloads moved
  • Data volume and time needed to move it
  • Number of environments prepared
  • Need to run alongside the old system
  • Scope of cost monitoring after migration
Send Message

> Project plan

Cloud Migration & Architecture · 5 stages

How Legia does it

A general view of the order and length of each stage. A change in scope moves the estimate, and the details are agreed after the consultation.

  1. Readiness assessment 1–2 weeks
  2. Design & cost estimate 1–2 weeks
  3. Environment setup 2–3 weeks
  4. Staged migration 3–8 weeks
  5. Cost tuning & handover 1–2 weeks
Estimated total
2–4 months
Estimated total
Work stages
5 stages
With a written deliverable at each stage
Team response
1 day
Legia team response on business days

For a mid-size workload, the whole process generally takes 2 to 4 months. The exact duration depends on the number of workloads and how tightly the old systems are tied to one another, and the move order is set so the riskiest part is not done first.

Legia's full process

Technology

Technology we build with

The tools actually used on this work. The choice adapts to the systems you already run rather than being forced into one mold.

Cloud providers

Chosen from technical needs and a cost comparison, including local cloud and VPS providers.

  • AWS
  • Google Cloud
  • Microsoft Azure
  • Local providers

Automation and orchestration

Used when needed: configuration as code and large-scale container management.

  • Terraform
  • Kubernetes

Security layer

Traffic filtering in front of the server.

  • Cloudflare

Why Legia

What you receive

Cloud migrations often end as a bill that rises without explanation. These five things keep placement, cost, and the way back readable.

  1. 01 · Engineering

    Written architecture

    An architecture document covering where each component sits, why it was chosen, and its estimated monthly cost.

  2. 02 · Ownership

    Documented configuration

    All infrastructure configuration is documented and traceable. When needed, it is kept as code in your repository so it can be repeated.

  3. 03 · Engineering

    Not locked to one provider

    The design uses services that have equivalents at other providers, so moving does not mean rebuilding.

  4. 04 · Ownership

    A rollback plan for every stage

    A plan to return to the original state for each migration stage, not just for the project as a whole.

  5. 05 · Reports

    Monthly cost review

    A monthly cost review while the project runs, with savings recommendations that can be acted on right away. After handover it can continue through a management subscription.

FAQ

Frequently asked questions

Haven't found your answer? Tell us what you need, and the Legia team replies within 1 business day.

Ask the Legia team ↗
What is a cloud migration service?

A cloud migration service moves systems from old servers to the cloud in a planned way: assessing what is worth moving, designing placement and sizing, moving in stages, then setting up cost control. Legia handles AWS, Google Cloud, Microsoft Azure, and local providers, with the old system staying up until the new one proves stable.

How much does a cloud migration service cost?

The basis is the number of workloads moved, how tightly the systems are linked, and whether cost control and monitoring are included. Legia gives the details after the readiness assessment, and that stage can be taken separately.

Is the cloud bill included in Legia's service fee?

No. The cloud provider's bill is paid directly by you in your company's name, separate from Legia's service fee. That way usage and cost stay under your control. Paid software licenses are also billed directly by their provider.

Do all systems have to move to the cloud?

No. Some systems make more sense staying on your own infrastructure, especially when their usage pattern is stable and predictable. Legia gives the comparison in the readiness assessment report.

How does Legia keep the cloud bill from ballooning?

Legia labels every resource, sets budget limits and usage alerts, and sizes resources to the real load. Monthly reviews include savings recommendations that can be acted on right away.

Will operations stop during the migration?

No. Workloads are moved piece by piece and run alongside the old system until proven stable. The full switch is done in a time window you set, and each stage has a rollback plan.

What security is installed in the cloud environment?

Access rights per person and per role, two-step authentication for admin accounts, data encryption, backups, and access logs. The rules go into the architecture document, so they can be reviewed before the migration starts.

How long does a cloud migration take?

For a mid-size workload, the whole process generally takes 2 to 4 months, from readiness assessment to handover. The exact duration depends on the number of workloads and how tightly the old systems are tied together, so Legia gives a stage-by-stage schedule after the readiness assessment.

Which cloud providers does Legia handle?

Legia handles AWS, Google Cloud, and Microsoft Azure, as well as local cloud and VPS providers. The choice is driven by technical needs and cost comparison, not vendor preference.

What is the difference between cloud migration and server installation and management?

Cloud migration is a project to move and reorganize systems in the cloud, complete with placement design and cost control. Server Installation & Management sets up and looks after the servers themselves every month, in the office or in the cloud. The two often come in sequence: migration first, then ongoing management.

Who manages the cloud environment after the migration?

Your team can manage it with the documentation and training handed over. If you prefer to hand it off, the Server Installation & Management or IT Support & Infrastructure Management service handles it on subscription, including its monthly cost review.