Migration from Jira
Move to Veqsio from Jira Cloud, Server or Data Center, a Jira backup, CSV, Linear, Asana or ClickUp: what is imported, a trial run and finishing the switch.
Plan the move
- Try it on a copy. Install a test Veqsio, import one project, and let a few people look.
- Create your users first if you use SSO or SCIM — people are matched by e-mail.
- Import everything shortly before the cut-over; import again to catch up.
- Switch the team over and make the old tool read-only.
Jira Cloud, Server and Data Center (live)
Open Import from Jira (REST). Enter the Jira URL and choose how to authenticate:
- Jira Cloud — email + API token
- Server / Data Center — personal access token
- Server / Data Center — username + password
After connecting, choose the projects and what to bring: workflows, boards, sprints, issues with original keys, comments, worklogs, links, sub-tasks, labels, components, versions, change history, attachments and custom fields. Press Import everything now. Tick Overwrite issues that already exist if you want a re-run to replace local edits. The page shows counts as it goes (created, updated, skipped).
Keeping up until cut-over
Sync changes from Jira re-reads what changed since last time, so you can import early and keep Veqsio current while people still work in Jira. Re-running never duplicates anything.
From a Jira backup file
For Data Center you can upload the XML backup (up to 2 GB) under Import a Jira backup file. Veqsio analyses it first and shows what it contains; run a dry run, resolve any conflicts it reports, and start. The import can be paused and resumed.
From CSV
CSV import reads a Jira-compatible export. Map columns to fields and run the validation dry run to see problems row by row before anything is written.
From Linear, Asana, ClickUp or a JSON file
- Open the source and connect with a personal token (Linear, Asana, ClickUp) or choose a file (JSON). The token is used only from the Veqsio server for this job and is never stored, logged or returned.
- Run the preview (dry run): it reports how many projects, issues, comments, links, sub-issues and sprints would be created or updated, which people match existing users, which statuses, types, priorities and labels are new, and what cannot be imported.
- Press Import everything now (everything is selected by default; you may deselect projects and edit each project key).
- Watch the progress bar and error log. Cancel stops after the current issue; whatever was imported stays, and a later run continues without duplicates.
People
Assignees, creators and comment authors are matched to existing users by e-mail (case-insensitive), then by username and display name. With Create placeholder users (the default) unmatched people get an account without a password, which they can claim through SSO or a password reset. With it off, the assignee stays empty and the reporter and comment author fall back to the administrator who ran the import.
What maps to what
| In the old tool | In Veqsio |
|---|---|
| Project / team | Project (keeps its key where it can; a new unique key is suggested otherwise) |
| Issue, sub-task, epic | Issue of the same type, with parent links |
| Status | Status in a workflow (choose its status group) |
| Sprint, board, version, component, label | The same objects |
| Comment, worklog, attachment, link | The same, with original author and time where known |
| Custom field | Custom field of the matching type |
Anything that cannot be imported is listed in the report. Typical examples are app-specific data and fields with no equivalent type.
After the import
- Open Configuration health and fix what it reports.
- Check permission schemes and project roles for the imported projects (Users & groups).
- Add people to the roles, run a few saved JQL searches against the old tool and Veqsio to compare counts.
- Rebuild personal dashboards and saved filters you still need, and tell the team where boards now live.
Safe to re-run
Every imported project, issue, comment and sprint is remembered by its external id, so a second run updates instead of duplicating. If you type the key of an existing project, the data is merged into it and a warning says so.