# How to move from Jira to Artavolo.com

> You export the work items of a Jira search as CSV, 10,000 at a time, and bring the files into Artavolo. Each work item becomes a record; status, priority and issue type become single selects, labels, components and versions multiple selects, and comments one field with their dates. Workflows, sprints and attachments are rebuilt or downloaded by hand. Nothing in Jira changes while you try it.

Source: https://artavolo.com/migrate/jira
Last reviewed: 16 November 2026

## In short

You export the work items of a Jira search as CSV, 10,000 at a time, and bring the files into Artavolo. Each work item becomes a record; status, priority and issue type become single selects, labels, components and versions multiple selects, and comments one field with their dates. Workflows, sprints and attachments are rebuilt or downloaded by hand. Nothing in Jira changes while you try it.

You import with: Import data, then Other apps.

## Before you start

- Decide which projects you bring, and write a search for each.
- Count the work items: above 10,000, split the search by created date.
- Download the attachments you still need: the CSV holds Jira links to them.
- Write down each workflow’s statuses and transitions.
- Make a free Artavolo account and a workspace: the free plan has no limit on people or records.
- Keep Jira running. Nothing in it changes, and the team switches once the new base is checked.

## Moving from Jira in 5 steps

### Step 1: Export from Jira

You get: CSV from a search (all fields).

1. Open Filters, search for the work items you want (for example project = WEB), and run it.
2. Choose Export, then Export CSV (all fields).
3. Above 10,000 work items, split the search (by created date, say) and export each part.

### Step 2: Bring the files into Artavolo

The files are read in your browser.

1. In Artavolo, choose **Import data** on Home, then **Other apps** ([this link opens it for you](https://artavolo.com/login?then=%2F%3Fimport%3Dapps#sign-up)).
2. Pick or drop the files, all at once: each becomes a table, linked where one names the other’s records. Say they come from Jira, so the report names it.
3. The tables and their fields are shown with their types, and what was found (links, lookups, groups). Untick a table to leave it out, then choose **Make the base**.

### Step 3: Read the import report

It lists the tables and records made, the formulas and lookups checked against Jira’s own results record by record, and what is different, so nothing is dropped without a word.

### Step 4: Check the new base

1. Compare the number of records in each table with Jira.
2. Open a few records and check their links, dates and selects.
3. Compare the number of records with the number of work items your search returned in Jira.
4. Go through the report’s list of what is different, and decide what to rebuild.

### Step 5: Rebuild and switch over

1. Rebuild what the export leaves out: the table below lists it, and so does the import report.
2. Invite the team, and set who sees which tables and records.
3. Set Jira to read-only, or stop using it, and keep it for a month rather than deleting it.

## Jira's words in Artavolo.com

| Jira | Artavolo.com |
| --- | --- |
| Site | Workspace |
| Project (space) | Base, or a table |
| Work item (issue) | Record |
| Issue type, status, priority | Single select fields |
| Labels, components, versions | Multiple select fields |
| Comment | One long text field, with the dates |
| Filter (JQL) | View with filters |
| Board or sprint | Kanban view, or a view grouped by sprint |
| Workflow | Status field with automations, or a review interface |

## What comes over

- Every work item you exported, as records
- Status, priority and issue type as single selects
- Labels, components and versions (Jira writes a column for each) as multiple selects
- Comments (also a column each in Jira’s CSV) as one field, with their dates; created, updated and due dates

## What you rebuild

- Workflows (as a status field with automations, or a review interface)
- Attachments, which come as Jira links
- Sprints and boards (views grouped by sprint or status)

## Help with the move

We move a base or a whole workspace from Jira for a fixed price, agreed before we start and quoted by e-mail: https://artavolo.com/contacts

## Questions and answers

### Jira’s CSV repeats columns. Is that a problem?

No. Jira writes a column per label, per comment and per file; the import makes each set one field: labels a multiple select, comments one long text with their dates.

### We have more than 10,000 work items.

Jira exports 10,000 at a time. Split the search (by created date, say), export each part and bring the files in together.

### Do attachments come over?

They come as Jira links, which need a Jira sign-in. Download the files you still need and attach them to the records here, or ask us to.

### How do we rebuild a workflow?

With a status field (single select) and automations on it, or a record review interface where people move a request from one status to the next.

### Does anything change in Jira?

No. You only export from Jira, and the files are read in your browser. Keep using it until the team has switched.

### Can you do the move for us?

Yes. We move a base or a whole workspace for a fixed price, agreed by e-mail before we start: we run the import, rebuild what the export leaves out and check the result against the report with you.

How Jira compares: https://artavolo.com/compare/jira.md
