How to move from Jira to Artavolo
A step-by-step guide: what to export from Jira, how to bring it in, what comes over, what you rebuild, and how to check the result.
Last reviewed
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 export
- CSV from a search (all fields)
- You import with
- Import data, then Other apps
- It costs
- Nothing: the importer is free
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
-
Export from Jira
You get: CSV from a search (all fields).
- Open Filters, search for the work items you want (for example project = WEB), and run it.
- Choose Export, then Export CSV (all fields).
- Above 10,000 work items, split the search (by created date, say) and export each part.
-
Bring the files into Artavolo
The files are read in your browser.
- In Artavolo, choose Import data on Home, then Other apps (this link opens it for you).
- 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.
- 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.
-
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.
-
Check the new base
- Compare the number of records in each table with Jira.
- Open a few records and check their links, dates and selects.
- Compare the number of records with the number of work items your search returned in Jira.
- Go through the report’s list of what is different, and decide what to rebuild.
-
Rebuild and switch over
- Rebuild what the export leaves out: the table below lists it, and so does the import report.
- Invite the team, and set who sees which tables and records.
- Set Jira to read-only, or stop using it, and keep it for a month rather than deleting it.
Jira’s words in Artavolo
What each part of Jira becomes after the move.
| In Jira | In Artavolo |
|---|---|
| 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, and what you rebuild
The import report names every item in the second group, so nothing is dropped without a word.
| From Jira | Result |
|---|---|
| Every work item you exported, as records | Comes over |
| Status, priority and issue type as single selects | Comes over |
| Labels, components and versions (Jira writes a column for each) as multiple selects | Comes over |
| Comments (also a column each in Jira’s CSV) as one field, with their dates; created, updated and due dates | Comes over |
| Workflows (as a status field with automations, or a review interface) | You rebuild |
| Attachments, which come as Jira links | You rebuild |
| Sprints and boards (views grouped by sprint or status) | You rebuild |
Rather we did 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. We run the import, rebuild what the export leaves out, check the result against the report with you, and walk you through it on a recording.
Tell us what you use in Jira and roughly how much data; we answer with a price within one business day.