Home›Services›Migrate off Terraform Cloud

Move off Terraform Cloud. Keep your state, lose the bill.

We move your workspaces from Terraform Cloud (now called HCP Terraform) to OpenTofu, with state, plan and apply running in the GitLab you already have. Your infrastructure does not change — only where it is managed from.

from $6,000 · fixed price Measured first, then fixed price and dates No downtime for your infrastructure
The problem

HCP Terraform bills per managed resource, and the old Free plan ended on 31 March 2026.

What we do

Move every workspace to OpenTofu with state and pipelines in your GitLab, one workspace at a time.

The result

No new SaaS bill, the same infrastructure, and a plan that shows “no changes” as proof.

Is this you?

This service is for teams that already run Terraform in HCP Terraform and want it in their own hands.

Why teams are moving now

What moves where

Everything Terraform Cloud does for you today has a place in GitLab. Nothing is left without an owner.

Terraform Cloud / HCPbilled per managed resource
Your GitLab + OpenTofualready paid for, inside your perimeter
Remote statestores and locks the state file
GitLab-managed OpenTofu stateencrypted at rest, locked, versioned
Plain-text state contentssecrets readable by anyone with state access
OpenTofu state encryption (optional)end-to-end, keys from KMS or OpenBao8
Runsplan and apply
GitLab CI pipelineplan on every merge request, apply after approval
VCS workflowruns start from commits
Merge requeststhe plan is shown to the reviewer
Variables & credentialscloud keys and inputs
Protected CI variables or OpenBaoshort-lived cloud credentials where possible
Sentinel policiesblock unsafe changes
OPA/Conftest, Checkovsame pipeline, same rules
Private module registryshares modules
GitLab module registryversioned modules next to the code
Drift detectionspots manual changes
Scheduled planalerts on any difference

What you get

At the end you have a working setup, and your team knows how to run it without us.

All workspaces moved

Every agreed workspace runs from GitLab. After each move, a plan shows no changes — proof that nothing in your cloud was touched.

A pipeline your team can read

One reusable CI template: format and validate, security checks, plan, approval, apply. Plain YAML, no hidden magic.

Policies kept

The Sentinel rules you rely on, rewritten as open policy checks that block the same unsafe changes.

Credentials cleaned up

Cloud keys moved out of Terraform Cloud and stored as protected variables or in OpenBao, with access limited by environment.

State history and backups

Versioned state in GitLab plus a separate backup, so you can restore state even if GitLab itself is down.

Runbook and handover

A short written guide: how to add a workspace, roll back a change, rotate a key, restore state. One live 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.

  1. Step 1 · 1–3 days

    Inventory and test run

    We list every workspace, variable, policy, module and run trigger. We run OpenTofu plans against a copy of each state and note anything that needs a code change. You get the cut-over plan and the final fixed price for the rest of the work.

  2. Step 2

    Build the new home

    GitLab state backend, CI template, policy checks, credentials and approvals set up and tested on a non-production workspace first.

  3. Step 3

    Move workspaces in batches

    Lowest-risk first, production last. For each workspace: freeze runs, copy state, run a plan, confirm “no changes”, switch the team over. Each step can be undone.

  4. Step 4

    Handover and switch-off

    Runbook, live session with your engineers, two weeks of questions. Once you are confident, you close the HCP Terraform organisation.

What we need from you

  • Read access to your HCP Terraform organisation and the IaC repositories.
  • A GitLab group where we can create projects and CI runners (or use existing runners).
  • One engineer on your side for about 2–4 hours a week, plus approvals for production moves.
  • An agreed change window for production workspaces.

Not included

  • Rewriting or refactoring your Terraform modules beyond what the migration needs.
  • Fixing existing drift — we report it and fix it only if you ask (priced separately).
  • Installing GitLab itself. If you need it, we quote it separately.
  • Moving to a different cloud or changing your infrastructure.
from $6,000

Fixed price, agreed after the measurement in step 1. Paid by milestone: inventory, build, migration, handover.

What changes the price

  • Number of workspaces and how many cloud accounts they touch.
  • Sentinel policies — how many you have and how complex they are.
  • Code changes found in week one, if your code uses features OpenTofu handles differently.
  • Your GitLab — GitLab.com or self-managed, existing runners or new ones.

Not sure about the size? Start with the IaC Health Check (from $1,800). You get the size, the risks and a fixed quote before you commit to anything.

Questions teams ask

Do we have to switch from Terraform to OpenTofu?

No. You can keep the Terraform CLI and still move state and runs into GitLab. Most teams choose OpenTofu because it stays under an open-source licence. We help you decide in week one.

Will our Terraform code need to be rewritten?

Usually not. OpenTofu started as a fork of Terraform, so most code works as is. In week one we run plans against every workspace and list anything that needs a change before the cut-over.

Is there any downtime?

Your infrastructure does not change. Only the place where state is stored and where plans run changes. We move one workspace at a time and check that the plan shows no changes after each move.

What happens to our Sentinel policies?

Sentinel only runs inside HashiCorp products. We rewrite the policies you actually use as open policy checks (OPA/Conftest or Checkov) that run in the same GitLab pipeline.

We run Terraform Enterprise, not HCP Terraform. Is it the same?

Yes, the route is the same: workspaces, state, variables and policies move to OpenTofu and GitLab. In addition, you can switch off the servers that run Terraform Enterprise.

We use GitLab.com, not self-managed GitLab. Does that work?

Yes. GitLab-managed OpenTofu state is available on GitLab.com, GitLab Self-Managed and GitLab Dedicated, on all tiers including Free.6

Often done together

Tell us how many workspaces you have

A 30-minute call is enough to give you a price range. No preparation needed.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Sources — public vendor announcements and documentation, for orientation only; not legal advice. Terraform, HCP Terraform and Sentinel are trademarks of HashiCorp, an IBM company.
  1. HashiCorp: HashiCorp adopts Business Source License (Aug 10, 2023)
  2. IBM Newsroom: IBM completes acquisition of HashiCorp (Feb 27, 2025)
  3. HashiCorp Developer: HCP pricing definitions
  4. HashiCorp: Continuing HCP Terraform's enhanced free tier experience (Dec 17, 2025)
  5. CNCF: OpenTofu project page
  6. GitLab Docs: GitLab-managed OpenTofu state
  7. HashiCorp Developer: Terraform Enterprise
  8. OpenTofu blog: OpenTofu 1.7.0 (Apr 30, 2024)
Book a 30-minute call