Move your Jira issues into Fareeqy
Export with all fields, upload, and choose what becomes your task lists. How the work is grouped is your decision, not ours.
Importing is available on paid plans and during the free trial, 14 days with no credit card
Your operations, marketing, or client-service team inherited Jira because engineering already used it. Soon a simple follow-up passed through an Issue Type, a Workflow status, perhaps an Epic, and the vocabulary of a software backlog. Nothing is broken, but a non-engineering team is carrying more process than its work needs. The weight appears as skipped updates, private lists outside Jira, and colleagues asking one person to operate the system for everyone else.
Export the Issues with all fields so comments are included, then choose the structure your team understands. The importer can group by Status, Epic, Sprint, Issue Type, Assignee, or Priority. It reads Status Category to decide completion, keeps Labels, Story Points, and attachment links in the notes, and lists every title collision before the data is written.
The result? Jira's work history moves without forcing engineering vocabulary onto the team responsible for following through after the migration. An operations lead can select Status instead of Sprint, read Summary as a task, and keep Story Points as reference rather than a way to manage the team. Every repeated Comment column arrives, Resolution informs completion, and Epic remains an optional grouping rather than a layer each department must learn.
What becomes what
Fareeqy has three levels and no fourth: project, task list, task.
| Jira | Fareeqy |
|---|---|
| Project | Project |
| Your choice: status, epic, sprint or type | Task list |
| Issue | Task |
| Labels | A line in the task notes |
| Story Points | A named value in the task notes |
| Attachment URL | A file-named link inside the notes |
What may surprise you about Jira
Jira Epics do not arrive as a separate hierarchy level. Choose epic on the upload screen and the importer uses Epic names to form Fareeqy task lists, placing each Issue inside the matching list. Choose Status, Sprint, Issue Type, Assignee, or Priority instead and Epics are not recreated as records of their own.
How to export from Jira
A project's issues
Search your project's issues in Jira, then from the button at the top right:
Export → Export CSV (all fields)
Pick all fields, not current fields. Comments only come out with it, and this is the single commonest way a Jira export goes wrong.
Accepted formats: CSV, or ZIP. You can upload several files together in one go.
What comes across, and what does not
Comes across
- Issues with their titles and descriptions
- Due dates
- Assignees, and the preview asks you who each one is on your team
- Comments, if you exported with all fields
- State, read from Status Category rather than from whatever your workflow named the status
Does not come across
- Files you uploaded inside the tool itself. Their bytes are not in the export at all, and fetching them would need your credentials for that account. Links do come across, inside the task's notes.
- Story points, sprints and issue links. They have no counterpart in Fareeqy, and what can be kept of them is written into the task's notes.
- Recorded time. Fareeqy tracks time on every task on Advanced and above, but the importer does not carry the value across from Jira, so those durations are typed in after the move.
Before you start
A Jira CSV export from the UI stops at 1,000 rows. If your project is bigger, split it with a filter, by sprint for instance, and upload all the files together in one go.
How the import runs
Nothing is written until you approve it
Upload the file and we read it, then show you exactly what would be created: how many projects, task lists and tasks, every title we would have to rename, and every person on your board. Only the confirm button creates data.
Duplicate titles are settled in front of you
Your board has three cards called Follow up, and the board's own name may already belong to a project you made last year. We rename, and every rename is on screen before you confirm, not after.
Upload the same export again safely
Re-exported after another week of work? Upload it again. What you imported before keeps your edits, and only what is new is added. This is a migration tool, not a two-way sync, so an import never overwrites what you changed inside Fareeqy.
The file stays yours
Delete it from the import page whenever you want. Forget about it and we delete it automatically after 30 days.
Frequently asked questions
Why must I export with all fields?
My project has more than 1,000 issues. What now?
How do you know an issue is done?
Does the import keep every repeated Comment column in Jira CSV?
Yes. Jira does not place all comments in one cell; it repeats the Comment column for every discussion entry on an Issue. The importer reads every value under that repeated heading instead of keeping only one, then separates the timestamp, author, and body without cutting off semicolons inside the message. A mapped author and original time are retained; an unmatched author falls back to the person running the import. That is why exporting with all fields matters.
The reader handles Jira's unusual shape before turning a row into a task. It never assumes a column heading is unique because Labels, Sprints, Attachments, and issue links can repeat in the same fashion. A Comment cell is split into date, author identifier, and body using only three parts, preserving later semicolons written inside the message. If a current-fields file contains a plain comment without that structure, the entire cell remains as the body rather than being discarded.
On write, the original Comment time remains when the export supplied one, and authors resolve through the mappings you approve in the preview. Bringing in an old Jira discussion does not fire new mention or subscriber notifications at the team; these messages are history, not conversations that happened today. Jira events that are not Comments, such as workflow changes or reassignments, do not populate Fareeqy's activity log because that would claim an action happened inside a product where it never occurred.
Which Jira Sprint is used when an Issue appears in several?
Jira writes repeated Sprint columns in chronological order when an Issue has moved through several iterations. If you choose Sprint for task-list grouping, the importer takes the newest value rather than the old Sprint where the work began. Current work therefore does not land under an iteration closed months ago. An Issue with no Sprint value is kept in a clearly named no-sprint list instead of being discarded.
Selecting Sprint changes grouping, not the nature of an Issue. Jira's Project field still names the Fareeqy project, the selected Sprint value becomes a task-list title, and Summary becomes the task title. The importer does not create a Sprint entity with start and end dates or attempt to run Scrum planning inside Fareeqy. Return to the preview and switch grouping to Status, Epic, Issue Type, Assignee, or Priority before confirmation, and the same file is parsed again.
Completion remains separate from Sprint and a customized Status name. The importer reads Status Category because it is limited to values that distinguish open from finished work, while a Jira team can name Status anything. Resolution means an Issue was resolved, but the Resolution value itself separates finished work from cancellation. An Issue leaving an old Sprint is therefore not automatically marked complete, and canceled work cannot be counted as an achievement that never happened.
Details outside that structure stay beside the task where possible. Story Points are written as a named line, Labels remain in the notes, and usable Attachment URLs become links labeled with their filenames. Issue relationships and time tracking do not become separate records. If Summary repeats inside the resulting list, the title deduplicator prepares a safe name and displays that rename before confirmation, preventing an otherwise valid Sprint grouping from failing because two Issues share a title.
What Teams Say About Project Management with Fareeqy
One of the nicest, most pleasant experiences I've had managing teams. Fareeqy stands out for being simple, easy, and uncomplicated.
And the most important feature is scheduling your work and tasks around prayer times, not the other way around!Honestly, I love using Fareeqy,
First, the project organization part, and its reminders if there are overdue tasks.
Fareeqy is easy and straightforward. I don't need to read or watch any video to know how to use any feature; everything is straightforward, and that's what makes me like Fareeqy most.Move your work into Fareeqy today
Create your account, upload the export, and read the preview. Nothing is written to your account until you confirm.
Get Fareeqy Free