Migration tools

Use Codex import first. Validate the harness locally.

Start with native import for supported setup, projects, and recent chats. Review the result before relying on it; a working import may be all you need.

The remote Bring Your AI surfaces stay no-data. They help agents discover the product, quote the license, and find the local command path; they do not accept harness files or config contents.

Tool comparison

Codex importImports selected local instructions, settings, skills, memories, hooks, MCP, plugins, subagents, projects, and recent chats. Some connections and behavior still need review.
Manual AGENTS.md editsWorks for small repos where the only real state is one instruction file.
Bring Your AI CLIAn optional local migration with a write plan, explicit merge policy, and recovery snapshots for existing nonempty harness targets.
Remote MCP discoveryNo-data target discovery, install instructions, quote, and checkout handoff.

The separate official migrate-to-codex skill offers source scanning, plans, dry-runs, and static target checks. Its normal migration command writes files. Its merge mode can replace same-named generated artifacts; review the plan and keep a recovery copy.

Decision rules

  1. If native import meets your needs, review its changes and try a representative task in Codex. You do not need a second migration just to validate it.
  2. If the setup includes hooks, MCP servers, skills, managed policy, or generated memories, run a local validation pass.
  3. If MCP config includes env, Keychain, 1Password, or vault helpers, preserve references instead of copying values.
  4. If session logs are useful history, keep them as notes instead of active instructions.
  5. Before migration, keep a recovery copy of the harness being changed. Use separate project backups or version control before production-code edits; harness rollback does not restore application binaries, chats, or all project files.

Optional Bring Your AI migration

Use this path only if you choose Bring Your AI to migrate your setup. Free preview checks default-directory presence and migration direction. Planning and migration require an activated license. These commands use the default Claude Code and Codex directories; select the correct source and target for your setup.

curl -fsSL https://bringyour.ai/install.sh | sh
bringyour preview --from claude-code --to codex
bringyour migrate --from claude-code --to codex \
  --src "$HOME/.claude" --dst "$HOME/.codex" \
  --policy merge --dry-run

Review the write/skip plan. If you choose to proceed, the next command writes the target and snapshots an existing nonempty target first. An empty target has no prior snapshot.

bringyour migrate --from claude-code --to codex \
  --src "$HOME/.claude" --dst "$HOME/.codex" \
  --policy merge

After a Bring Your AI migration, check its generated manifest:

bringyour verify --root "$HOME/.codex"

This checks Bring Your AI's own portable-manifest.json and expected files. It does not audit an arbitrary native import or prove runtime behavior. Review deferred checks, then test the required instructions, tools, and restrictions in Codex before relying on the setup.

The agent-readable version of this comparison is available at /claude-code-to-codex-tools.json.

Buy lifetime access Read the audit
back to bringyour.ai