AGENT MIGRATION
Move your settings when
switching AI agents.
Move your preferences, project rules, and workflows with a checklist for coding, office work, or both. Choose your agents, map each setting, and record what you have verified.
How to preserve and verify your settingsYOUR HANDOFF
Cursor → Codex
Carry useful context, adapt the tools, and check one real result.
This creates a fill-in template. It does not read your accounts or export conversations.
1. Capture the work in Cursor
Write a dated summary of the goal, confirmed decisions, completed work, open questions, source files, and next step. Carry your repository and test commands; adapt editor rules and extensions to the destination.
2. Prepare Codex
Install a supported client, sign in, and enable the tools required for your task. Carry project instructions and a dated task summary. Reconnect desktop plugins and verify file access in the destination client.
3. Reconnect tools and check costs
Reconnect the required accounts using the destination's supported setup. Confirm permissions, file access, and any paid entitlement. Account plan / usage limits: Check your account allowance and the selected model. Do not treat subscription use as a measured per-task API price. Subscriptions and usage allowances do not automatically move with your documents.
4. Hand off the coding work
Keep the repository, current revision, uncommitted changes, project rules, setup commands, tests already run, and known failures. Translate agent-specific instructions, skills, and tools. Check automatic branch, commit, and deployment behavior against your rules. Start with one small change and verify its diff and tests.
Finish with a checked handover
Acceptance: the new agent can access the required material, follow your instructions, and complete the sample task. Verify a new session if preferences must persist. Inventory reminders and recurring jobs; after validating the replacement, retire overlapping jobs so actions are not duplicated. Keep original files until the handover is checked.
What needs a separate transfer?
Native chat history, internal memory, tool settings, credentials, and running automations are not assumed to be portable. Review the destination's supported import features and keep originals until the handoff is verified.
This is an editorial checklist, not an end-to-end tested migration. Product versions and account conditions can change.
Preview the handoff template
# Handoff: Cursor → Codex Work: Coding Prepared on: [fill in] This is a handoff template, not a native session import. It contains no exported account data. ## Fill in the working context - Goal and deliverable: - Confirmed decisions and their dates: - Completed work and evidence: - Current files and access locations: - Unfinished work and next step: - Acceptance criteria: - Communication and formatting preferences: - Allowed actions and actions needing review: - Outdated or uncertain information: - Scheduled jobs and their owners: Do not include passwords, access tokens, or unnecessary private data. ## Preserve your settings SETTINGS INVENTORY Source product, client, and version: [fill in; unknown if unavailable] Destination product, client, and version: [fill in] Account or workspace type: [fill in] Last reviewed by me: [YYYY-MM-DD] My three most important requirements: [fill in] Review these categories. Mark each reviewed, not applicable, or unknown: - Communication preferences: - Project and file-specific rules: - Memories and corrections: - Active work and reference files: - Skills, commands, and agent roles: - MCP servers and account connections: - Model settings, permissions, and approval controls: - Hooks, scheduled tasks, and notifications: SETTING RECORD — repeat for each item ID and name: Original wording or value: Source and last-confirmed date: Scope: [global / project / file / task] Trigger and exceptions: Required files, tools, or accounts: Destination setting or location: Existing destination value and any conflict: Transfer method: [reuse / convert / rebuild or reconnect / unsupported / unknown] Verification status: [not started / configured, unverified / passed / failed / blocked] Acceptance task and expected result: Observed result and evidence: [leave blank until checked] Remaining differences: Previous destination value and rollback steps: Mark unsupported only after checking the destination's capabilities. Record connection names and required permissions, never secret values. Keep verification pending until you have observed the result. ## 1. Capture the work in Cursor Write a dated summary of the goal, confirmed decisions, completed work, open questions, source files, and next step. Carry your repository and test commands; adapt editor rules and extensions to the destination. - [ ] Checked ## 2. Prepare Codex Install a supported client, sign in, and enable the tools required for your task. Carry project instructions and a dated task summary. Reconnect desktop plugins and verify file access in the destination client. - [ ] Checked ## 3. Reconnect tools and check costs Reconnect the required accounts using the destination's supported setup. Confirm permissions, file access, and any paid entitlement. Account plan / usage limits: Check your account allowance and the selected model. Do not treat subscription use as a measured per-task API price. Subscriptions and usage allowances do not automatically move with your documents. - [ ] Checked ## 4. Hand off the coding work Keep the repository, current revision, uncommitted changes, project rules, setup commands, tests already run, and known failures. Translate agent-specific instructions, skills, and tools. Check automatic branch, commit, and deployment behavior against your rules. Start with one small change and verify its diff and tests. - [ ] Checked ## Finish with a checked handover Acceptance: the new agent can access the required material, follow your instructions, and complete the sample task. Verify a new session if preferences must persist. Inventory reminders and recurring jobs; after validating the replacement, retire overlapping jobs so actions are not duplicated. Keep original files until the handover is checked. - [ ] Checked ## Source and version check - Cursor: https://cursor.com/docs/agent/overview Scope: Editor workflow; cloud agents are a separate execution mode. Documentation checked: 2026-10-05; installed version: [fill in] - Codex: https://openai.com/codex/for-work/ Scope: Desktop and CLI; office tools depend on the selected client and plugins. Documentation checked: 2026-10-05; installed version: [fill in] The procedure is editorial guidance. Cross-product migration has not been tested end to end. Original session history, internal memory, permissions, and running tasks are not assumed to transfer.