How to move from Jira Service Management to Artavolo
A step-by-step guide: what to export from Jira Service Management, how to bring it in, what comes over, what you rebuild, and how to check the result.
Last reviewed
In short
You export the requests of a Jira search as CSV, 10,000 at a time, and bring the files into Artavolo. Each request becomes a record; status, priority and request type become single selects, and comments one field with their dates. Queues become views, service levels are set up again in the Service desk window, and the portal on your contacts. 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 service spaces you bring, and write a search for each.
- Count the requests: above 10,000, split the search by created date.
- Write down your request types, statuses, queues and service level goals with their targets.
- List your customers and organizations: in Artavolo, each client sees the records linked to their company.
- Download the attachments you still need: the CSV holds Jira links to them.
- Make a free Artavolo account and a workspace: the free plan has no limit on people or records.
- Keep Jira Service Management running. Nothing in it changes, and the team switches once the new base is checked.
Moving from Jira Service Management in 5 steps
-
Export from Jira Service Management
You get: CSV from a search (all fields).
- Open Filters, search for the requests you want (for example project = SUPPORT), and run it.
- Choose Export, then Export CSV (all fields).
- Above 10,000 requests, 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 Service Management, 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 Service Management’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 Service Management.
- Open a few records and check their links, dates and selects.
- Compare the number of records with the number of requests your search returned in Jira.
- Sign in to the portal as a test client and check that only that company’s requests show.
- 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 Service Management to read-only, or stop using it, and keep it for a month rather than deleting it.
Jira Service Management’s words in Artavolo
What each part of Jira Service Management becomes after the move.
| In Jira Service Management | In Artavolo |
|---|---|
| Site | Workspace |
| Service space (project) | Base, or a table |
| Request (work item) | Record |
| Request type | Single select field |
| Queue | View with filters |
| Agent | Editor |
| Customer | Portal client (a contact) |
| Organization | Client company |
| Customer portal | Client portal |
| SLA goal | Service level |
| Customer satisfaction (CSAT) | Rating, asked when a request is resolved |
| Knowledge base article | A record of a help articles table, on a portal page |
| Automation rule | Automation |
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 Service Management | Result |
|---|---|
| Every request you exported, as records | Comes over |
| Status, priority and request type as single selects | Comes over |
| Comments as one field, with their dates; created, updated and due dates | Comes over |
| Your customers and organizations (as contacts and client companies) | You rebuild |
| Service level goals (in the Service desk window) | You rebuild |
| Queues (as views with filters) | You rebuild |
| The customer portal (as a client portal on your contacts) | You rebuild |
| Workflows (as status rules and automations) | You rebuild |
| Attachments, which come as Jira links | You rebuild |
Rather we did the move?
We move a base or a whole workspace from Jira Service Management 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 Service Management and roughly how much data; we answer with a price within one business day.