#Leaving Fjord

Leaving is as portable as arriving. Your instance is standard Forgejo: your code is plain Git and everything else is reachable over the Forgejo /api/v1, so you can take a complete copy with you and nothing is trapped behind a proprietary format. Migrating in has its own guide; this page is the way out.

#Export your data

• Repositories. Clone or mirror every repo with git, exactly as you would any remote. A full clone is a complete copy of the history.
• Issues, pull requests, labels, milestones, and releases. Use Forgejo’s built-in repository data export, or pull them over the Forgejo API (fj api works well for scripting). See Export your own copy.
• Git LFS objects. Fetch LFS content from a fresh clone so large files come with the repository rather than staying server-side.
• Pages. A Fjord Pages site is built from your repository by a workflow, so the source and the build config leave with the repo; redeploy it anywhere.

Because these are standard Git and Forgejo interfaces, the same tooling you use day to day is all you need to walk away with a working copy.

#Close your account or delete an instance

• Delete an instance. Removing an instance tears down the server and its backups on the published schedule. Export first.
• Close your account. Sign-in is deactivated and your sessions are invalidated immediately. Your account data is then anonymized and purged after a 90-day retention window, rather than vanishing on the spot. You can also close your account from within Fjord Mobile.

For the authoritative export window and the deletion timeline, see Security and privacy and Accounts.

#What Fjord keeps, and for how long

• While your instance is active, backups run nightly with a 90-day rolling retention window on Team and Pro (see Backups).
• After you close your account, sign-in stops immediately and your data is anonymized and purged after the 90-day retention window.

#Related

• Backups and export
• Security and privacy
• Accounts
• Provisioning