The durable work is already on your SCM. Devin clones your repositories and opens pull requests there. It cannot create new GitHub repositories. Leaving is mostly confirming the branches, uninstalling an app, and picking the next engine.
The full migrate page, with citations: How to move off Devin.
1. Keep the git remotes
Confirm every useful branch exists on GitHub, GitLab, Bitbucket, or Azure DevOps. Session filesystem changes do not write back to Devin's org snapshot.
Source: Devin GitHub integration and environment setup.
2. Pull transcripts if you need them
The v3 API lists session messages and attachments. Archive sessions you want to keep readable. There is no documented one-click export of every cloud session as of 15 September 2026.
The Devin CLI --export flag writes ATIF after each local turn. That is the CLI path, not the cloud web app.
3. Disconnect GitHub
Unlink the personal connection under Devin Settings, then uninstall the Devin GitHub App at github.com/settings/installations.
4. Privacy and deletion
Email privacy@cognition.ai. The privacy policy (updated 9 March 2026) includes access, portability, and deletion. Paid plans can opt out of training. Enterprise trains only with written consent.
Source: Cognition Privacy Policy.
5. Start the next Task somewhere else
If the next ticket should run Claude Code, Codex, or OpenCode, connect the same repository to Rush Cloud and start one Task. Do not import Devin Knowledge. Put durable instructions in the repo.
If you still want a vendor agent, the honest map is Devin alternatives and Devin review.
