Freshrelease (Freshworks) to Jira Migration (~80,000 Issues) – Looking for Best Practices & Recommen

Question

Hi Atlassian Community,

We are currently working on an urgent client requirement to migrate approximately 80,000 issues from Freshrelease (Freshworks Agile Project Management & Bug Tracking) to Jira Cloud.

Freshrelease reference: https://www.freshworks.com/apps/freshrelease_for_freshdesk/

The client would like to preserve as much information as possible, including:

* Projects and issue hierarchy
* Epics, Stories, Bugs, Tasks, etc.
* Comments
* Attachments (including images)
* Linked issues
* Issue history/activity logs
* Custom fields
* Workflows and statuses
* Users (Reporter, Assignee, Watchers)
* Sprints, boards, releases, and other Agile metadata

We have already contacted Atlassian Support and understand that there is no native migration tool available for Freshrelease, and that CSV import has limitations (history, attachments, linked issues, etc.).

We're looking for guidance from the community:

* Has anyone successfully migrated from Freshrelease to Jira Cloud?
* Which migration tool or approach did you use (Help Desk Migration, OpsHub, custom REST API scripts, or another solution)?
* Were you able to migrate issue history, attachments, linked issues, and comments successfully?
* Are there any best practices or lessons learned for handling a migration of around 80,000 issues?
* Would you recommend a particular Atlassian Marketplace app or Solution Partner for this scenario?

Any recommendations, experiences, or documentation would be greatly appreciated.

Thank you in advance for your support!

Akshad Katke · Answer

Hi Shubham,

Thank you for your response.

We recently spoke with the Freshworks team and found that Freshrelease has been discontinued.

We're now looking for any official documentation, implementation guides, or references related to migrating from Freshrelease to Jira. If you've handled a similar migration in the past or know of any recommended approach, documentation, or tools that could help preserve data such as history, attachments, linked issues, and comments, we'd really appreciate your guidance.

Thank you in advance!

Akshad Katke · Answer

Hi Zoltan,

Thank you for your suggestion.

We spoke with the Freshworks team and learned that Freshrelease has been discontinued.

Since this is a large migration (~80,000 issues), we're looking for any official documentation, migration guides, best practices, or references from similar Freshrelease-to-Jira migrations. If you've worked on a similar migration before or know of any resources that could help, we'd greatly appreciate your guidance.

Thank you!

zoltanersek _outpostlabs_dev_ · Answer

For that size, I would spend time on a small pilot before commiting to the full run. Don't forget to validate user mappings, workflow, permissions.