Linear
BackupLatte is preparing to launch. Account creation and backups are not available yet. Join the waitlist for updates.
Restore a backup into Linear
A restore writes a snapshot back into a Linear workspace you have connected: 43 of the backed-up sets, from teams and workflow states to issues, documents, comments and customer requests. It never changes the snapshot, and the workspace the snapshot came from is only written to when you choose to restore into it.
Choose where to restore
Open the workspace in BackupLatte, find the backup in Backups and choose Restore…. Any backup that finished as Success or Partial can be restored. Under Restore into, pick one of:
| Target | When to use it |
|---|---|
| Another workspace | Recovery and copies. The backed-up workspace stays untouched. This is the default. |
| This workspace | Bringing back what was deleted from the backed-up workspace itself. Records still there are left as they are. |
Restore into a new workspace
- Create the workspace in Linear: workspace name at the top left → Switch workspace → Create or join a workspace.
- Stay in the new workspace. Linear connects the workspace you have open.
- In BackupLatte, choose Restore… on the backup, keep Another workspace, pick what to restore and choose Connect a workspace and restore.
- Approve the access in Linear. Check that Linear names the new workspace.
- Back in BackupLatte, the restore starts on its own.
If Linear connected the backed-up workspace instead of the new one, the restore does not start: switch to the new workspace in Linear and connect again. If the connected workspace already holds issues, projects or initiatives, BackupLatte asks you to confirm first.
Restore into another connected workspace
Pick it under Workspace. BackupLatte checks what it already holds:
- A clean target — no issues or projects yet. The restore can go ahead.
- Already has issues, projects or initiatives — restored records are added next to them and cannot be removed in one step. Tick Restore into … anyway to go ahead.
The list shows the first 100 connected workspaces. A workspace connected under another BackupLatte account cannot be a target.
Choose what to restore
Under What to restore every set the backup can restore is selected. Untick what you do not need. A set can be restored only if it is complete in the backup; a gap in another set does not stop the rest. Restoring into another workspace also needs the backup's Teams and Workflow states, which the restored records belong to.
Choose Queue restore. The restore appears under Restores with live progress.
How records are matched
Records are restored in dependency order — teams, workflow states and labels first, then projects, cycles and issues, then comments, and templates last — so everything a record points to exists before it. References to things that already exist in the target are matched rather than duplicated:
| Backed-up record | Matched in the target by |
|---|---|
| Team | Its key. Created when the target has no team with that key. |
| Workflow state | Name and type, within the team. Created when missing. |
| Label | Name, team and group. |
| Project status | Name and type, else the first status of the same type. |
| Person (assignee, lead, member) | Email address of an active user. |
| Project labels, customer statuses and tiers, emojis | Name. |
A reference that cannot be matched — for example an assignee who is not a member of the target workspace — is left empty instead of failing the record. BackupLatte does not invite people: invite them in Linear first if assignments matter.
What a restored workspace looks like
- Archived records come back archived. They are archived at the end, after their comments, attachments and relations are added.
- Deleted records — issues and projects in Linear's trash, deleted labels — are not restored.
- Files linked in descriptions, comments and documents are uploaded to the target again and the links point to the new copies. In the same workspace, the original links still work and are kept.
- Authors. Records are created by the Linear user who connected the target. A comment or update written by someone else starts with Originally posted by and their name. The creation dates of issues, comments, customers and releases are kept.
- Issue numbers are given by the target workspace, so an issue may get another identifier than in the original.
- Workspace settings (backed up with extended coverage) are copied only into a workspace that held no issues, projects or initiatives when the restore began, such as one created for it. A workspace already in use keeps its own settings, and the restore says so.
- Teams over the plan's limit. If the target's Linear plan allows no more teams, that team and its records are skipped.
- Features the target lacks. A set the target workspace does not offer on its Linear plan (for example customers or cycles on some plans) stops as Not in the target; the rest of the restore continues.
Restore into the same workspace
Restoring into the backed-up workspace brings back only what is missing. Records that still exist are left as they are, issues and projects in Linear's trash are taken out of it, and everything else missing is created again.
Follow the progress
Open a restore under Restores to see, per set:
| Column | Meaning |
|---|---|
| Total | Records of the set in the backup. |
| Restored | Created in the target. |
| Already there | Found in the target, not created again. |
| Skipped | Deleted in the backup, or nothing to attach them to. |
| Failed | Refused by Linear. |
| Not in the target | The target workspace does not offer this set. |
Under the table, Also created in the target counts the teams and workflow states the restore had to create, and the files it uploaded again.
Resume a failed restore
If a restore fails — Linear was unavailable, access was revoked — open it and choose Resume restore. It continues where it stopped. Every restored record gets an id tied to the target workspace, so records already restored are recognised and never copied twice — also when you run another restore of the same backup into the same workspace.
What is not restored
These sets are kept in the backup and its download, but cannot be written back to Linear: the workspace's users, change history of issues, projects, initiatives and releases, document versions, the audit log, invitations, integrations, webhooks, agent sessions and activities, shared agent skills, team posts, team pinned resources and resource sections, and SLA configurations. The full list is in What a backup contains.
Something missing or unclear? Write to [email protected].