Runs from a file export — no agents, no access to your environment

Know what your migration costs
before you commit to a cloud.

IaCTranslate reads the inventory export you already have, scores the estate for readiness, ranks every cloud on real cost and fit, sequences the cutover, and emits infrastructure code that the cloud providers’ own tooling validates. Every decision carries a reason you can audit.

5
inventory sources
5
target clouds
6
IaC formats
0
agents installed

The problem

Migration planning is still a manual craft.

It is done by hand, VM by VM

Infrastructure engineers read a discovery export and hand-translate it into infrastructure code, one workload at a time. It is slow, it is expensive, and the reasoning behind each sizing decision lives in someone's head.

No estate is only VMware

Real estates are VMware plus Hyper-V plus physical plus a CMDB nobody trusts plus a cloud footprint someone started in 2021. Tools that assume one source cover a fraction of the problem.

The vendor tools are not neutral

A cloud provider's migration tooling is single-cloud, emits no portable infrastructure code, and will never tell you a competitor is the better fit. You get the answer the tool was built to sell.

So teams either pay consultants for months, or accept whichever cloud the tool was built to sell.

Why not the vendor’s own tool

A cloud provider will never send you to a competitor.

This is not a gap in their roadmap. It is a conflict with their business model, which is why it has stayed open for a decade.

CapabilityIaCTranslateAWSAzureGoogle
Reads VMware, Hyper-V, Kubernetes, CMDB and cloud fleetsYesAgentsAgentsAgents
Emits portable infrastructure code you own6 formatsNoNoNo
Targets more than one cloud5 cloudsAWS onlyAzure onlyGCP only
Will recommend a competitor when it winsYesNeverNeverNever
Runs without touching your environmentYesNoNoNo

How it works

One deterministic pipeline. The same input always gives the same output.

  1. 01

    parse

    Any inventory export — five sources, auto-detected

  2. 02

    normalize

    One canonical model, whatever the source

  3. 03

    assess

    Readiness score, risks, data-quality findings

  4. 04

    recommend

    Unbiased cloud ranking on cost, fit and OS

  5. 05

    plan

    Right-size, network, sequence into waves

  6. 06

    validate

    Catalog and schema checks before anything renders

  7. 07

    govern

    Policy engine blocks on your org's rules

  8. 08

    render

    Six IaC formats, from templates — never freehand

No, an LLM does not write your Terraform.

AI is optional, off by default, and confined to structured decisions — grouping workloads and proposing instance types. Templates emit the code. A validation layer re-checks every choice against the target’s real catalog, so an invalid suggestion is rejected rather than rendered. The plan records which engine actually ran, not which one you asked for.

Your inventory stays yours.

The tool never connects to your environment — it reads a file you already export. It runs fully offline with no cloud credentials. If you do turn AI on, hostnames, cluster names and network labels are replaced with consistent pseudonyms first, and addresses, tags and resource IDs are dropped entirely.

Proof, not slideware

Same estate, four clouds, 31% apart.

  • OCI$3,864/mo
    recommended
  • GCP$4,320/mo
  • Azure$4,919/mo
  • AWS$5,051/mo

From a 7-workload sample estate. Full monthly cost — compute, block storage, Windows licensing and load balancers — at on-demand list price, assuming no committed-use discount. DigitalOcean prices lower and is excluded: it publishes no Windows image, so it cannot host part of this estate, and a cloud that cannot run the workload is not a cheaper option. Your estate will produce different numbers; the point is that the spread is large and knowable before you commit.

778

automated tests

10

CI jobs, green

tofu ✓

real provider validation

60

architecture decision records

Generated infrastructure code passes real tofu validate against the actual AWS, azurerm and Google providers — enforced continuously in CI, not demonstrated once.

Why this is happening now

86%

are actively reducing their VMware footprint

CloudBolt, survey of 302 North American IT decision-makers, Feb 2026

4%

have actually finished migrating

CloudBolt, survey of 302 North American IT decision-makers, Feb 2026

73%

run hybrid cloud today

Flexera 2026 State of the Cloud Report, n=753

Almost everyone has started. Almost nobody has finished. That gap is measured in estates that still need planning, costing and translating.

Who it is for

Built for the people who run migrations for a living.

Cloud consultancies and MSPs

You bid migrations fixed-price and the assessment phase eats the margin. This does the estate analysis in minutes and leaves you the client-ready report.

Enterprise platform teams

You have to justify a target cloud to people who control the budget. This gives you a costed comparison with the assumptions visible.

Migration leads

You own a cutover date. This finds the dependencies, sequences the waves, and flags the workloads that will fail on the night.

Pricing

Priced per estate, not per seat.

The work scales with how large and how messy the estate is — not with how many people read the answer. A consultancy bills a project straight through to its client as a line item.

Evaluate

Free

up to 100 workloads

  • The full pipeline on one estate
  • All five clouds compared
  • Readiness score and cost breakdown

Project

$7,500

per estate, up to 500 workloads

  • $20,000 up to 2,500 workloads
  • Unlimited runs on that estate
  • Client-ready reports and diagrams
  • All six IaC formats, policy engine, wave planning

Practice

Talk to us

annual, unlimited projects

  • For teams running several migrations a year
  • SSO, RBAC, audit export
  • Reusable policy packs and branded reports

Enterprise

Talk to us

annual, self-hosted

  • Air-gapped deployment — inventory never leaves your network
  • Customer-managed encryption keys
  • Support SLA and priority cloud coverage

Migration tooling typically runs 6–10% of total migration cost. On a mid-market programme that is a budget line measured in six figures, which is the number these should be judged against — not against a per-server rate.

Tell us about the estate you have to move.

We are looking for a small number of teams with a real migration in front of them. Bring your inventory export and we will walk through what the tool says about it — the readiness score, the cloud comparison, and the workloads it thinks will break.

No sales process. A working session with the person who built it.