Import work items

Import moves an existing backlog into a Skopo project in one pass. You upload an export, review how its columns, statuses, and types map onto the project's active methodology, and then create up to 2,000 work items at a time.

Before you start

• You need a project role that can edit work items (Member or above). Observers cannot import.
• Archived projects cannot receive imports. Restore the project first.
• Assignees are matched by email address against people who are already on the project. Add teammates to the project before importing if you want their work to stay assigned.
• Supported sources:
  • CSV: any spreadsheet export with a header row.
  • Jira: a filter export via Export → Export CSV (all fields).
  • Linear: Settings → Import / export → Export CSV.
  • Trello: the board JSON from Menu → Print, export and share → Export as JSON.

Steps

Upload the export

1. Open your project's Settings page.
2. Scroll to Import work items and click Import….
3. Choose the source (CSV, Jira, Linear, or Trello).
4. Choose the exported file and click Review import.

Review the mapping

1. For CSV, Jira, and Linear files, check the Column mapping. Skopo suggests a column for each field based on the source:
   • Jira: Summary, Description, Issue Type, Status, Priority, Assignee, Story Points, Labels, Due date, Parent or Epic Link, and Issue key.
   • Linear: Title, Description, Status, Priority, Assignee, Estimate, Labels, Due Date, Parent issue, and ID.
   • CSV: common names such as Title, Status, Type, Labels, Due date, and Assignee. Change any field to a different column, or choose Not imported. Title is required. The preview refreshes after each change.
2. Check the Status mapping table. Each source status is matched to a workflow state of the project's methodology, so names like "To Do", "In Progress", "In Review", and "Done" land in the matching column. Values that do not match are marked (fallback) and go to the backlog.
3. Check the Type mapping table. Source types such as Epic, Story, Bug, or Task are matched to the methodology's work-item types. Anything unknown uses the methodology's first type.
4. Read any warnings, then scan the preview of the first 20 items. Assignees who are not on the project are shown as (unassigned), and parents that are not in the file are shown as (missing).

Run the import

1. Click Import N items and keep the dialog open while Skopo creates the work.
2. When the import finishes, the result shows how many items were created, nested under a parent, failed, skipped, or left unassigned. Failed rows list the reason.

How data is mapped

• Hierarchy: parents are created before their children. If the methodology does not allow a child type under its parent's type, the child is imported without a parent and the result says so.
• Source reference: each description starts with the source key, for example "Imported from Jira ABC-12".
• Labels: label names are kept. Trello label colors are kept as well, and other labels get a color from the label palette.
• Dates and priority: due dates (and start dates, when present) are converted to calendar dates. Priorities such as Highest, Blocker, Urgent, High, Medium, Low, and Lowest map to Skopo's Urgent, High, Medium, and Low.
• Trello: list names become statuses, and archived cards or lists are skipped.
• Limits: one import creates at most 2,000 items from a file of up to 10 MB. Split larger exports into several files.

Result

The imported items appear on the board, backlog, and roadmap with the project's workflow states and work-item types. Dated items show up on the roadmap right away. To keep working with them, see /docs/guides/use-the-board.