Independent comparison · checked September 10, 2026
Choose the right Codex migration tool.
Changing Macs, recovering missing conversations, and keeping two computers in sync are different jobs. The best option depends on what you need to move and whether both computers will remain active.
Disclosure: this page is published by Joshua Segeren, the developer of Codex Migrate. Competing projects are linked directly and described from their public documentation. Verify their current releases and safety guidance before using them. None of these independent tools is made by or endorsed by OpenAI.
Short answer
Changing from one Mac to another?
Use Codex Migrate when you want a guided Mac-to-Mac transfer of local Codex state and selected workspace folders, with resumable staging and a verified destination backup.
Recovering or merging selected history?
Consider ChenglongLi777/codex-migrate when selective session import, path repair, HTML export, or Windows and Linux support matters more than a signed Mac release.
Want a small Mac history runbook?
Consider codex-history-migrator when you are comfortable running shell and Python scripts and primarily need to archive, restore, reindex, and remap local Codex history.
Want to AirDrop Codex records?
Consider Codex Sync at codexsync.org when you want an Apple-silicon Mac installer that exports conversations, titles, project records, and indexes into a bundle you send yourself.
Keeping multiple computers active?
Consider Codex Sync when the job is ongoing continuity across Windows and macOS. It is designed around selected stable task histories and a private shared folder or Git vault—not a one-time whole-workspace move.
At-a-glance comparison
| Option | Best fit | Platforms | Delivery | Important limit |
|---|---|---|---|---|
| Codex Migrate | One-time transfer of local Codex state plus selected workspaces | Mac to Mac; paid app is Apple silicon | Free MIT CLI; signed and notarized $49 beta with best-effort support | Not continuous sync; does not merge two independently active workspaces |
| ChenglongLi777/codex-migrate | Selective sessions, repair, backup, rollback, and HTML export | macOS, Windows, Linux, and WSL | Free MIT GUI and CLI builds | Its documentation says current releases are not commercially signed or Apple-notarized |
| codex-history-migrator | Scripted Mac history backup, restore, path rewrite, and reindex | macOS | Shell and Python source | Focuses on Codex history rather than transferring complete project folders |
| Codex Sync (codexsync.org) | AirDrop-friendly transfer of conversations, titles, project records, and indexes | Apple-silicon Macs | Mac installer sold through Gumroad | Its documentation says it does not transfer repositories, arbitrary documents, or generated files |
| Codex Sync | Ongoing selected-task and personal-skill continuity | Windows and macOS | Free MIT CLI and Codex Skill | Requires a trusted shared folder or private Git vault; divergent histories become explicit conflicts |
| Manual copy or rsync | Experts with a narrowly defined, reviewed set of files | Depends on your commands | Built-in system tools | You own identity exclusions, path mapping, backups, interruption recovery, and verification |
Codex Sync vs Codex Migrate
Codex Sync at codexsync.org is the simpler option when you only want to package Codex conversations, titles, project records, and indexes into a .codexsync file and send it to another Apple-silicon Mac with AirDrop. Its documentation explicitly says it does not transfer source repositories, arbitrary documents, generated files, or other Codex outputs.
Codex Migrate is for a broader new-Mac move. It transfers portable Codex state plus the workspace folders you select, including complete Git repositories, local branches, worktrees, stashes, and unfinished files. It stages a resumable copy directly over SSH, preserves the new Mac's authentication and installation identity, verifies a destination backup before replacement, and performs post-transfer checks.
Both are independent, local-first Apple-silicon Mac tools. Choose Codex Sync for a small AirDrop record bundle. Choose Codex Migrate when the project files and Git state behind those conversations need to arrive too.
Why “just copy the folder” is incomplete
Local Codex work can span conversations, configuration, skills, memories, automations, project folders, Git metadata, worktrees, unpushed branches, stashes, and unfinished files. Some runtime state is machine-specific. A blanket copy can also carry authentication, installation identity, live databases, locks, sockets, logs, or caches that should not replace the destination computer’s state.
A manual copy may be perfectly reasonable for an expert who knows the exact storage layout and has a tested recovery plan. The value of a migration tool is not the byte-transfer primitive; it is choosing the right scope, preserving destination identity, stopping unsafe writes, resuming interruptions, and verifying the result.
Migration is not synchronization
A one-time migration assumes the old environment becomes the source and the new environment becomes the destination. Ongoing sync assumes several computers may keep changing. That introduces conflict detection, stable checkpoints, transport coordination, and a decision about which history is canonical.
If you plan to work on the same Codex task from multiple computers, choose a synchronization design built for that job. Codex Migrate deliberately does not pretend it can safely combine two divergent active workspaces.
For a source-based Mac-to-Windows handoff, better-codex-rehome is another related project to inspect. Its scope and platform path differ from the Mac-to-Mac products compared above.
What to verify before trusting any option
- Does it preserve the destination computer’s authentication and installation identity?
- Does it move project folders and complete Git state, or only Codex conversations?
- What happens if the network, process, or computer stops midway?
- Is existing destination data backed up and verified before replacement?
- Can you inspect the proposed scope before enabling changes?
- Is the downloadable build signed, and can you inspect its source?
Keep the old computer intact and maintain an independent backup. No community migration or synchronization tool can guarantee compatibility with every Codex release, filesystem layout, or machine configuration.
For a guided Mac-to-Mac move
Codex Migrate transfers portable OpenAI Codex state and explicitly selected workspaces directly between Macs over SSH. The source Mac is left intact. The free CLI and paid app use the same migration engine and safety checks; the $49 beta provides a signed, Apple-notarized package and personal, best-effort support.