# Import from Linear

> Connect Linear to By Dawn through By Dawn's Linear app, pick a team, and check how its workflow states, projects and cycles map.

This page helps you bring a Linear team into By Dawn. At the end its issues are By Dawn tickets, its projects are By Dawn
epics, and, if you chose to keep syncing, the two stay in step until your end date.
[Import and sync](https://docs.bydawn.com/import-and-sync/) explains the steps every tracker shares, so this page covers only
what's particular to Linear.

## Before you start

- You need to be a project admin in By Dawn, and an **org admin** has to install By Dawn's app (see
  [Before you start](https://docs.bydawn.com/import-and-sync/#before-you-start)).
- By Dawn's Linear app acts as itself, not as the person who installs it. Its changes and comments show in Linear as
  coming from By Dawn.

## Connect

1. In By Dawn, open **Settings › Import & sync › New import**, pick **Linear** and choose **Connect**.

2. Linear asks you to install By Dawn in your Linear workspace with read and write access. Choose **Authorize**.

3. Linear sends you back to By Dawn, and the page shows the connected Linear workspace.

## Pick what to bring

Pick one **team**. Everything in the team comes over: its issues, its projects, and the cycles its issues are in.

## How Linear maps

- **Statuses.** By Dawn proposes a column from each workflow state's type: *Triage* and *Backlog* go to the backlog,
  *Unstarted* to a to-do column, *Started* to a building column, and *Completed* and *Canceled* to a completed
  column. Canceled issues also get the label `resolution:canceled`.
- **Priorities.** Urgent, High, Medium and Low map to the same By Dawn priorities, and *No priority* to no priority.
- **Projects** become By Dawn epics, and the issues in a project join its epic.
- **Sub-issues** become sub-tickets. A sub-issue of a sub-issue is flattened to a sub-ticket, with a related link
  back to its old parent.
- **Cycles** can become By Dawn cycles, `sprint:` labels, or nothing.

## Customers and their needs

When your organization uses [Customers](https://docs.bydawn.com/customers/), each import and sync also brings Linear's customers and their
needs:

- **Customers** come over with their domains, revenue, size, status, tier, owner and logo. A status or tier is matched to yours by
  name. A Linear customer with the same name or domain as one you have joins it rather than making a second.
- **Customer needs** on the issues this import brought become requests on those tickets, marked **Import**. The
  need's text becomes the quote, an important need stays important, and a need attached to a conversation links to it.

A later sync fills only fields that are still empty, so an edit in By Dawn is never overwritten, and it never renames a
customer. Deleting a customer or a need in Linear doesn't delete it in By Dawn.

## When you sync both ways

By Dawn writes back the title, description, status, priority, assignee and labels, plus new comments. A label that
doesn't exist in Linear yet is created on the team. Due dates come from Linear but aren't written back yet, and
projects are only read, never changed.

## Where to go next

- [Import and sync](https://docs.bydawn.com/import-and-sync/): conflicts, pausing and ending a sync.

Source: https://docs.bydawn.com/import-linear/