Cloudkeel-ZeroDiff

Move your Terraform state without moving your infrastructure.

State migration is the kind of work where the plan matters more than the execution. We assess read-only, write the plan, and run it alongside your team — on your infrastructure, under your credentials.

Assessment is read-onlyWe never hold your credentials

When teams call us about state.

State that outgrew one file

A single state has become large enough that every plan is slow and every apply is frightening. Splitting it means moving resources between states without destroying and recreating them.

A backend you need to leave

Local state, or a backend that no longer fits — moving to S3, GCS, Azure Blob or Terraform Cloud, with locking and versioning set up properly on the way in.

Two estates becoming one

A merger, an acquisition, or a repo split that left resources spread across states that disagree about who owns what.

Resources Terraform never adopted

Live infrastructure that no state claims, which has to be imported before it can be managed rather than recreated underneath a running service.

The risk is always the same. A state operation that goes wrong does not fail loudly — it orphans a resource, or plans to destroy and recreate something that is serving traffic. That is why the plan is the deliverable, not the commands.

How an engagement runs.

  1. 01
    Read-only assessment firstWe read your state and your live estate before anything moves. Nothing is mutated during this step, and what we find determines whether the work is worth doing at all.
  2. 02
    A written migration planWhich resources move, in what order, and what each step does. Reviewed with you before a single state operation runs.
  3. 03
    Execution alongside your teamThe work runs against your state, under your credentials, with your people in the room. We never take custody of your cloud access.

Scope, timeline and price are set at the scoping call, against your actual state — there is no useful fixed answer before someone has looked at it.

Tell us what your state looks like.

Twenty minutes is usually enough to work out whether this is a week of work or an afternoon, and we would rather say the second one now.

This is consulting work, not software — it is a separate engagement fromCloudkeel-DD, which you caninstall yourself without talking to anyone. We are pre-launch: no customers yet, and no SOC 2.