Home›Services›ClickOps → Code

Turn the infrastructure you clicked together into code

Most cloud accounts have resources nobody wrote down: created in the console, changed by hand, understood by one person. We import them into OpenTofu without touching what runs, so every future change is reviewed, repeatable and visible in Git.

from $2,500 · fixed price Measured first, then fixed price and dates Zero changes to live resources
The problem

Part of your cloud was built by hand and nobody can rebuild it.

What we do

Import it into readable OpenTofu modules with import blocks.1

The result

A plan that shows no changes — and every future change reviewed in Git.

Is this you?

Before and after

Todaybuilt in the console
AfterOpenTofu in your GitLab
Clicks in the consolehow changes happen
Merge request with a planthe reviewer sees the change
One or two peoplewho knows what exists
Anyone with the repositorycode is the documentation
Days of guessingrebuilding an environment
A pipeline runsame result every time
Found by accidentmanual changes
Scheduled drift checkalerts on any difference

How the import works

What you get

Inventory

Every resource in the agreed accounts and regions, marked as already in code, to import, or to leave alone.

Readable code

OpenTofu modules organised by environment and purpose, not one generated file of thousands of lines.

Clean import

State stored in GitLab, a plan with no changes as proof that nothing live was touched.

Pipeline

Plan on every merge request, apply after approval, scheduled drift check.

Handover

A short guide to making changes the new way, and a session with your team.

How it goes

The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates. Our free scope script gives the first numbers.

  1. Step 1 · 1–3 days

    Inventory

    We list what exists, agree the scope and the final price.

  2. Step 2

    Import

    Import blocks and code, account by account, until the plan is clean.

  3. Step 3

    Pipeline and handover

    CI pipeline, drift check, guide and session.

What we need from you

  • Read-only cloud access for the inventory; write access only for state, not for resources.
  • A GitLab group for the code and state.
  • Someone who knows which resources matter and which are leftovers.

Not included

  • Redesigning the infrastructure — we codify what exists. Improvements come after, if you want them.
  • Deleting unused resources — we list them, you decide.
  • Resources from providers without an OpenTofu provider.
from $2,500

Fixed price after the inventory in step 1. Paid on completion.

What changes the price

  • Number of resources and resource types.
  • Accounts, subscriptions or projects and regions.
  • How much is already in code — mixing existing code with imports takes more care.

Questions teams ask

Can the import change or break a live resource?

Importing only writes to state. We then require a plan with no changes before handover, so nothing is modified.

Which clouds?

AWS, Azure, Google Cloud and other platforms with an OpenTofu provider.

We use Terraform, not OpenTofu. Does that matter?

The approach is the same. We use OpenTofu by default because it is open source; if you prefer Terraform, tell us.

Can people still use the console afterwards?

They can, but the drift check will flag every manual change. Most teams switch to merge requests within weeks.

Often done together

Tell us which cloud and how big

Accounts, regions and a rough number of resources — enough for a price.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Sources — public announcements, documentation and legal texts, for orientation only; not legal advice. Terraform, Vault and Sentinel are trademarks of HashiCorp, an IBM company.
  1. OpenTofu docs: Import
Book a 30-minute call