Moving trackers is less scary when you can see exactly what will happen before anything changes. Starlex imports Jira CSV exports with automatic column mapping and a full check before it writes a single row.
1. Export from Jira
In Jira, open the issue search, filter to the project you want to move and export the results as CSV with all fields. Include custom fields if you use them.
2. Prepare the Starlex project
Create the project in Starlex and add the people who will work in it. If you rely on custom fields, create them first so the import can map to them.
3. Map the columns
Open Import CSV from the project's More menu and upload the file. Columns map automatically by name, including custom fields. Statuses, types and priorities match their names or common Jira names such as “In Progress”, “Highest” or “Won't Do”. People match by email, username or name.
4. Check, then import
The import checks every row first and reports each problem by row number, so you can fix the file or the mapping. When everything passes, all rows are created in one go: either the whole file lands or nothing does.
5. Tidy up
Reorder the backlog, plan the next sprint and invite the rest of the team. Keep the Jira export as an archive; you can re-run the import into a fresh project if you want to try a different mapping.
Big projects
One import handles up to 2,000 rows and 8 MiB. Larger projects split neatly into several files, for example by epic or by year.