Move your legal requests over from Jira, history and all.
Connect the tool your team uses now or upload an export. A preview shows what each ticket becomes before anything is saved.
Northwind brings its legal requests across from Jira. Before anything is saved, a preview shows what each ticket becomes. Sample company, Northwind Materials.
From the tool your team uses now
Jira
Connect Jira Cloud or Data Center, or upload an export.
Zendesk
Connect with an API token.
Freshservice
Connect with an API key.
Spreadsheet (CSV or Excel)
Upload a sheet with one request per row.
A Jira export can be CSV, XML or JSON, with a zip of its attachments beside it if you have one.
What each ticket becomes
Advottic suggests a match for every type, status, priority and field it finds. Here is what it suggests for some common Jira values. You can change any of them before you import.
| In Jira | In Advottic |
|---|---|
| Issue typeContract review | Request |
| Issue typeLitigation | Matter |
| StatusWaiting for customer | Waiting on the employee |
| StatusWaiting for vendor | Waiting on someone outside |
| StatusDone | Completed |
| StatusWon't Do | Cancelled |
| Status of a matterIn review | Under review |
| PriorityHighest | Urgent |
| FieldDue date | Due date |
| FieldGoverning law | Jurisdiction |
| FieldCounterparty | Counterparty |
Check it before it is saved, and after
The preview plans the first 25 tickets with your mapping and saves nothing. When the import is done, a report lists what came across and anything left out, with the reason, and the full list downloads as a CSV.
Each record keeps its original key, such as NWL-12, and a link back to the ticket when it has a web address. Advottic gives it its own request or matter number. Original dates and comments come with it. Change history comes across when you connect to Jira, because a CSV or XML export does not include it.
Upload the same export again and Advottic notices it. Choose Update the earlier import and records already brought in are updated, not added twice. Bring in separately adds them again.
If an import stops partway
A stopped import deletes nothing. What it brought in stays where it is, and the report names the step it stopped on.
The report lists what the import created or updated before it stopped, with a link to each record, so you can see what is already in Advottic.
To bring in the rest, upload the same file again and choose Update the earlier import. Records already brought in are updated where they changed, not added twice.
500 issues from Jira, measured
A Jira export of 500 issues, each with one comment, was imported in 4.9 seconds: 500 requests created, none skipped or failed.
One run on a MacBook Pro with a local production build, local Supabase in Docker and headless Chrome, with no attachments and one comment per issue. Time on a hosted account will differ.
The report when an import finishes: what was brought in, who was matched, and anything left out with its reason. Sample company, Northwind Materials.
People, files and who can import
- People are matched to your team, invited as members, added as employees, or kept as names. Invitations are prepared during the import and sent only when you confirm.
- Attachments up to 50 MB each come across, checked like any upload and stored privately with the record.
- Only a firm owner or admin can run an import.
Common questions
- Does the import keep comments and dates?
- Yes. Original dates and comments come across with each record, which also keeps its original key, such as NWL-12. Change history comes across when you connect to Jira, because a CSV or XML export does not include it.
- What does the preview show?
- The preview plans the first 25 tickets with your mapping and shows what each one becomes in Advottic, with its status, owner and requester. It saves nothing.
- What happens if an import stops partway?
- Nothing is deleted. The report names the step it stopped on and lists what was already brought in. Upload the same file again and choose Update the earlier import, and records already brought in are updated, not added twice.