Migrating a Compliance Workflow to a Claude Agent

You already have a compliance workflow. Maybe it is a quarterly evidence-collection runbook a engineer works through by hand, or a brittle script that scrapes findings from three tools and pastes them into a spreadsheet. Someone has now asked you to "put an AI agent on it." The temptation is to rip out the old process and let a Claude agent run the whole thing on day one. That is how you end up with a missed control in an audit and a very uncomfortable conversation. Migration done well is staged, reversible, and boring.

This post lays out how to move an existing security or compliance workflow onto a Claude agent without betting the audit on it: map the workflow honestly, run the agent in shadow mode, keep a human in the loop, and cut over one slice at a time.

Map the existing workflow before you automate it

The first mistake is automating a process nobody fully understands. Before any agent work, write down the current workflow as discrete steps with explicit inputs, outputs, and decision points. Which steps are pure data gathering (pull findings from the scanner)? Which are judgment calls (decide whether a finding is an accepted risk)? Which are irreversible or high-stakes (close a control as satisfied)? This map is what tells you where an agent helps and where a human must stay.

You will usually find that the workflow is mostly mechanical with a few genuine judgment points. That is the ideal shape: hand the mechanical bulk to the agent and keep humans on the judgment and the irreversible steps. Trying to automate the judgment calls first is how migrations fail — start with the toil.

Run the agent in shadow mode first

The safest way to learn whether the agent is trustworthy is to run it in parallel with the existing process without letting it touch anything. In shadow mode, the agent does the work, produces its output, and you compare that output to what the human process produced — but the human process remains the source of truth. The agent's results go to a log, not to the auditor.

flowchart TD
  A["Existing workflow runs (source of truth)"] --> B["Claude agent runs in shadow on same inputs"]
  B --> C["Compare agent output vs human output"]
  C --> D{"Agreement high & safe?"}
  D -->|No| E["Fix prompts / tools, add eval case"]
  E --> B
  D -->|Yes| F["Promote: agent drafts, human approves"]
  F --> G["Narrow human review as confidence grows"]

Shadow mode gives you a real, quantified agreement rate on production inputs before the agent has any authority. Shadow mode is running a new agent alongside the existing process on the same live inputs while the old process stays authoritative, purely to measure agreement. Run it for enough cycles to cover the variety of real inputs — a compliance workflow that runs quarterly may need synthetic replays of past quarters to gather signal faster.

Promote to human-in-the-loop, not full autonomy

When the agent's shadow agreement is high and its safety record is clean, the next stage is not autonomy — it is assistance. Let the agent draft the output and have a human review and approve before anything is committed. The human is now reviewing a near-complete artifact instead of doing the work from scratch, which captures most of the time savings while keeping a person accountable for every consequential decision.

Crucially, make approval easy to deny and easy to correct, and capture every correction. When a reviewer overrides the agent — "this finding is actually an accepted risk, not an open one" — that correction is gold: it becomes a new eval case and, over time, sharpens the agent's prompts. The human-in-the-loop stage is where your eval set grows fastest, because every review is a labeled example.

Cut over one slice at a time

Only after the assisted stage proves out should you let the agent act autonomously, and even then only on the low-stakes, reversible slices first. Cut over by segment: let the agent fully own read-only evidence collection while humans still sign off on control conclusions. Expand the autonomous surface as each slice earns trust, and keep the irreversible steps — closing a control, attesting compliance — behind human approval indefinitely if the risk warrants it.

Keep the old workflow runnable throughout. A migration is not done when the agent goes live; it is done when you have run enough cycles autonomously to trust it, and you can still fall back to the manual process in a single command if something drifts. The Claude Agent SDK and Claude Code make it straightforward to keep the agent's actions gated and logged, so "autonomous" never means "unobserved."

Plan for rollback and drift

Even a successful migration needs a reverse gear. Define explicit rollback triggers before cutover: if agreement with spot-checks drops below a threshold, if a safety violation occurs, or if the agent's cost spikes, you revert that slice to manual and investigate. Pair this with ongoing monitoring — sample autonomous runs, keep humans labeling a slice, and watch your eval scores for decay. The same drift discipline that protects an eval suite protects a production migration, because the world the agent operates in keeps changing.

Frequently asked questions

How do I start migrating a compliance workflow to Claude safely?

Map the existing workflow into discrete steps first, separating mechanical data-gathering from judgment calls and irreversible actions. Automate the mechanical bulk, then run the agent in shadow mode before granting it any authority.

What is shadow mode and why does it matter?

Shadow mode runs the new agent alongside the existing process on the same live inputs while the old process stays authoritative. It gives you a real agreement rate on production data before the agent can affect anything, so promotion is a measured decision.

When is it safe to let the agent act autonomously?

After shadow mode shows high agreement and the human-in-the-loop stage proves a clean safety record. Even then, grant autonomy slice by slice, starting with read-only, reversible work and keeping irreversible steps like attesting compliance behind human approval.

What rollback plan should a migration have?

Define explicit triggers before cutover — agreement dropping below threshold, any safety violation, or a cost spike — that revert the affected slice to manual. Keep the old workflow runnable throughout so fallback is a single command.

Migrating your phone lines to agentic AI

CallSphere uses this same staged, reversible rollout to move voice and chat workflows onto AI agents — shadow first, human-approved next, autonomous only once trust is earned. See how at callsphere.ai.

Source & attribution: This is an independent, original explainer inspired by Anthropic's coverage on the Claude blog. Claude, Claude Code, Claude Cowork, Claude Opus, and the Model Context Protocol are products and trademarks of Anthropic. CallSphere is not affiliated with or endorsed by Anthropic.