> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate one Clay table to a Play

> Ask your agent to recreate one Clay table without changing the working process prematurely.

[Agent guide: CLI and SDK instructions →](/docs/migrate-from-clay)

## 1. Have your context ready

Have an authorized Clay table, its configuration and sample export, expected outputs, and the existing approval boundaries.

## 2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

```deepline-prompt theme={null}
/deepline-gtm Help me migrate one Clay table to a Deepline Play. First document the actual columns, formulas, prompts, conditions, provider fallbacks, and external writes from the table and export I provide. Ask about anything the export cannot establish. Show the mapping for review before building the Play. Validate it without execution, then propose a representative pilot on the same rows as Clay. Keep the current Clay workflow active until we compare results.
```

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

## 3. Review the result

The pilot matches the intended table behavior and its acceptance rules. Differences are explained before cutover; a similar-looking enrichment result is not proof of equivalence.

Ask your agent:

```deepline-prompt theme={null}
/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.
```

Approve a larger job, recurring work, or external changes only after reviewing that decision.

## Check your understanding

Does reproducing column names establish equivalent workflow behavior?

> **Show the answer**
>
> No. Compare the actual inputs, transformations, acceptance rules, and results
> under the same test cases.

## Related guides

* [Your first Deepline workflow](/docs/quickstart)
* [Webhooks and schedules](/docs/human/sdk-v2/webhooks-and-schedules)
* [Cost control](/docs/human/cost-control)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.