Move from Jira
From Jira to Artavolo, step by step
Export from Jira, bring the files in, and see what came over before anyone switches. It is read in your browser, and nothing in Jira changes.
-
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 in
- In Artavolo, open Import on the home page and choose Other apps (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, and make the base.
-
Read the 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. Keep Jira until the team works here.
What comes over
Your data, typed and linked
- 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
Named in the report, every one
- 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)
Rather we did it? We move a base or a whole workspace for a fixed price, rebuild what the export leaves out, and check it with you. Ask for a quote.
Questions
Moving from Jira
Yes. Artavolo runs on your own server with the same plans and prices as in our cloud, and the Community edition is free. It does not call home.
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.
For tracking work in tables, boards and forms, yes. For sprints tied to code and deployments, Jira is ahead: we say so plainly.
Other moves