Never lose an issue, project, or cycle

Overview⁠

SimpleBackups keeps a scheduled, verifiable copy of your entire Linear workspace in cloud storage you own, so issues, projects, documents, comments, and cycles survive an accidental bulk delete, a bad automation, or a lost workspace. Every run reports exactly what it captured, and you can restore any past backup into a separate Linear workspace while the original is only ever read.

How it works⁠

Connect a Linear workspace with a read-only authorization, then choose a schedule and a storage destination: Amazon S3 and S3-compatible providers, Azure Blob Storage, Backblaze B2, Dropbox, and more, or storage provided by SimpleBackups. Each run captures: issues and sub-issues, issue relations, comments, projects, project updates, project milestones, project labels, project statuses, cycles, documents, initiatives, initiative updates, initiative-to-project links, teams, team memberships, workflow states, issue labels, users, external users, attachments, custom views, and templates. Everything is written as JSON Lines with one file per record type, so the archive stays readable without SimpleBackups, and encryption with your own key and downloading the files hosted in Linear are both optional.

Every run writes per-type counts into the archive and shows them on the backup’s dashboard, so you can confirm what was captured rather than assume. If core content cannot be retrieved, meaning issues, comments, projects, cycles, teams, users, labels, or workflow states, the run is marked failed instead of being stored as a usable restore point, and you choose whether it stops at the first failure or keeps going and collects everything it can before failing. Failures affecting optional content do not fail the run; they are listed alongside partial counts for review.

To recover, pick any previous backup and authorize a destination workspace with a separate write-scoped connection. SimpleBackups recreates teams, workflow states, labels, projects, milestones, cycles, issues and sub-issues, comments, documents, and initiatives, rebuilds the relationships between restored records, rewrites cross-references between restored issues, and carries over original author names and creation dates on issues and comments where Linear’s API allows. The source workspace is only ever read, per-type progress is reported live while the restore runs, and a restore that is interrupted resumes from its last checkpoint instead of starting over.

Configure⁠

In SimpleBackups, create a new backup, select Linear, and click Connect Linear workspace, then approve the read-only authorization. The integration connects as a Linear app, which reaches your workspace’s public teams by default; to include a private team, grant it to the app from the app’s details page in your Linear settings. Once connected, select the connection, choose a schedule and a storage destination, and optionally turn on encryption with your own key or include the images and files hosted in Linear. You can also choose whether a run stops as soon as core content fails or keeps going and captures everything it can before reporting the failure.

To restore, open the backup run you want and select Restore, then authorize a destination workspace. This is a separate write-enabled authorization, and because the restore creates teams in the destination, Linear may require that you have the Admin role there. Use a new, empty workspace: if the destination already contains teams, issues, projects, or initiatives, the restore stops and asks you to confirm explicitly before it will run. Restores read from S3-compatible storage, Azure Blob Storage, Backblaze B2, and Dropbox, and an encrypted archive also needs its matching private key, which is used for that restore and never stored. Full setup instructions are at https://simplebackups.com/docs/saas-app-backup/apps/linear