Skip to help
ScopedHelp CenterContact supportSign in

Move work from Linear

Understand Scoped’s operator-run Linear CSV import, its preparation steps, and the information a CSV cannot carry.

Connect operators; Cloud users should contact supportReviewed

Before you start

For Connect, involve the person who operates the deployment and its database. They need a Linear workspace-admin CSV export, access to Scoped’s maintained import tooling, and a verified backup of the target database.

Understand what transfers

The importer supports issue fields represented in the CSV, including identifiers, titles, descriptions, status, priority, people, projects, and related planning fields where present. The source file determines what can be transferred.

  • Comments and historical activity cannot be reconstructed from the workspace CSV.
  • Attachments are not carried by this CSV workflow.
  • People identified by display name may need reconciliation with real Scoped accounts.
  • There is no continuing synchronization with Linear after import.

Prepare with your operator

  1. Export the workspace CSV from Linear using a workspace-admin account.
  2. Agree on the destination workspace and make a recoverable backup with your Scoped operator.
  3. Have the operator preview the CSV and review the importer’s limitations before running the import.
  4. Plan how unmatched people will be reconciled. Do not guess account mappings.

In an appropriately configured Scoped source checkout, the operator’s non-mutating preview is:

pnpm db:import:linear /path/to/workspace.csv --dry-run

The dry run parses the file; it does not validate account mappings against the database. Actual import and reconciliation should follow the operator’s maintained procedure.

Review the imported work

  1. Compare representative issue identifiers, titles, status, and ownership with the source workspace.
  2. Check projects, teams, and any expected relationships.
  3. Review the reconciliation report with the operator and resolve unmatched people.
  4. Keep the source export until the team has accepted the results.

If something is missing

First check whether the CSV contained the missing field. Comments, attachments, and old activity are known boundaries, not evidence that you should repeatedly re-import. Share specific issue identifiers and the reconciliation findings with your operator or support.