Linear · Restore

Linear

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:

TargetWhen to use it
Another workspaceRecovery and copies. The backed-up workspace stays untouched. This is the default.
This workspaceRecover missing records in the original workspace, matching records already there rather than replacing the workspace.

Restore into a new workspace

  1. Create the workspace in Linear: workspace name at the top left → Switch workspace → Create or join a workspace.
  2. Stay in the new workspace. Linear connects the workspace you have open.
  3. In BackupLatte, choose Restore… on the backup, keep Another workspace, pick what to restore and choose Connect a workspace and restore.
  4. Approve the access in Linear. Check that Linear names the new workspace.
  5. 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:

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 recordMatched in the target by
TeamIts key. Created when the target has no team with that key.
Workflow stateName and type, within the team. Created when missing.
LabelName, team and group.
Project statusName 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, emojisName.

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

Restore into the same workspace

Restoring into the backed-up workspace brings back only what is missing. Matching existing records are reused, issues and projects now in Linear's trash can be taken out of it, and supported missing records are created again. This is recovery, not a rewind that overwrites the current workspace with the snapshot.

Follow the progress

Open a restore under Restores to see, per set:

ColumnMeaning
TotalRecords of the set in the backup.
RestoredCreated in the target.
Already thereFound in the target, not created again.
SkippedDeleted in the backup, or nothing to attach them to.
FailedRefused by Linear.
Not in the targetThe 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. Records that refer to one that failed (comments on an issue, sub-issues of a parent, issues in a project) wait for it rather than being restored without it, so a retry restores them together and links them. Every restored record gets an id tied to the target workspace, so a retry or another restore of that backup can recognise those records. This does not deduplicate unrelated records created manually or by other integrations.

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].