
Jira Service ManagementFreshservice
Jira Service Management to Freshservice migration
ITSM specialists move your incident requests, service requests and problems into Freshservice, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated November 2026 · 14 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Jira Service Management to Freshservice at a glance
A Jira Service Management to Freshservice migration turns work items into tickets, public comments into replies and internal comments into private notes. Freshservice sets the limits on the way in: 40 MB of files per ticket, incidents through the Tickets API and requests through the service catalog. Jira stays live until the final delta sync.
- Objects mapped
- 14
- in this route's mapping
- Typical timeline
- About 10 business days end to end
- 3 phases
- Free sample
- 100 records
- checked by your team first
- Quote
- Fixed
- within 24 hours
- Who it is for
- IT teams moving their service desk from Jira Service Management to Freshservice to run incidents, the service catalog, assets and changes on one ITSM platform.
- What does not move
- Automation rules, workflows, SLA goals and queues are configuration. We list each one for your Freshservice admin to rebuild as Workflow Automator rules, business rules and views.
- What sets the scope
- Work item volume, how many files pass 40 MB, the Freshservice plan you are on, request types that need the catalog, and how many Confluence sources feed the knowledge base.
What moves
What moves from Jira Service Management to Freshservice
Work items become tickets or catalog requests, public comments become replies, internal comments become private notes, and customers become requesters.
- 14 included
| Jira Service Management | maps to | Freshservice | Status |
|---|---|---|---|
| Incident requests | Tickets (Incident)Created through the Tickets API, which takes only the incident type. | Included | |
| Service requests | Service Requests on catalog itemsThe catalog item is built first, and the request is placed on it for the requester. | Included | |
| Problems | ProblemsProblem management starts on the Freshservice Pro plan. | Included | |
| Changes | ChangesChange management starts on the Freshservice Pro plan. | Included | |
| Public comments | Replies and public notesCreated as the original author with the user_id parameter and marked public, so they read as the thread the customer saw. | Included | |
| Internal comments | Private notesNotes are private by default, so an internal comment stays out of the requester's view. | Included | |
| Attachments | Attachments on the ticket or noteUp to 40 MB in total per ticket. Larger files are linked from a private note. | Included | |
| Customers | RequestersLoaded first, by CSV or API, with the exact email Jira holds, so no duplicate contact appears. | Included | |
| Organizations | DepartmentsCreated before any ticket, and requesters are linked to them. | Included | |
| Licensed agents | AgentsMatched by email. Former agents who get no seat are named in the note text. | Included | |
| Teams and assignee groups | Agent groupsGroups are per workspace in Freshservice. | Included | |
| Service spaces | WorkspacesOnly on accounts that have workspaces. | Included | |
| Assets objects, object types and references | Assets, asset types and relationshipsRelationships are loaded after both ends exist. | Included | |
| Knowledge base pages | Solution categories, folders and articlesEach Confluence source is mapped to a category, and deep trees use sub-folders. | Included |
- Incident requestsTickets (Incident)
Created through the Tickets API, which takes only the incident type.
- Service requestsService Requests on catalog items
The catalog item is built first, and the request is placed on it for the requester.
- ProblemsProblems
Problem management starts on the Freshservice Pro plan.
- ChangesChanges
Change management starts on the Freshservice Pro plan.
- Public commentsReplies and public notes
Created as the original author with the user_id parameter and marked public, so they read as the thread the customer saw.
- Internal commentsPrivate notes
Notes are private by default, so an internal comment stays out of the requester's view.
- AttachmentsAttachments on the ticket or note
Up to 40 MB in total per ticket. Larger files are linked from a private note.
- CustomersRequesters
Loaded first, by CSV or API, with the exact email Jira holds, so no duplicate contact appears.
- OrganizationsDepartments
Created before any ticket, and requesters are linked to them.
- Licensed agentsAgents
Matched by email. Former agents who get no seat are named in the note text.
- Teams and assignee groupsAgent groups
Groups are per workspace in Freshservice.
- Service spacesWorkspaces
Only on accounts that have workspaces.
- Assets objects, object types and referencesAssets, asset types and relationships
Relationships are loaded after both ends exist.
- Knowledge base pagesSolution categories, folders and articles
Each Confluence source is mapped to a category, and deep trees use sub-folders.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
What does not move from Jira Service Management to Freshservice as-is
Automation rules, workflows, SLA goals, request type forms and Confluence page permissions are configuration, so your Freshservice admin rebuilds them from the list we hand over.
- ChangelogOn request
- In Freshservice: Private note summaryField-change history from Jira kept as one private note per ticket.
- On request
- SLA resultsOn request
- In Freshservice: Custom ticket fieldsPast Jira SLA outcomes kept as fields for reporting.
- On request
- Automation rulesNot migrated
- In Freshservice: Workflow Automator and business rulesConfiguration, rebuilt by your Freshservice admin from the list we hand over.
- Not migrated
- SLA goals and calendarsNot migrated
- In Freshservice: SLA policiesRebuilt as policies by your admin. SLA management starts on the Freshservice Growth plan.
- Not migrated
- Request type portal formsNot migrated
- In Freshservice: Service catalog itemsThe forms are rebuilt as catalog items. Answers on past requests move as data.
- Not migrated
- Confluence page permissionsNot migrated
- In Freshservice: Article visibilityFreshservice article visibility is set again by your admin after the load.
- Not migrated
- Assets Discovery and Assets automationNot migrated
- In Freshservice: Freshservice discovery and asset rulesConfiguration, set up again in Freshservice. Asset records themselves move.
- Not migrated
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
Jira Service Management to Freshservice migration timeline
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayWe agree which service spaces and request types move, how requests split between incidents and catalog items, and what happens to files above 40 MB.
Connect Jira and Freshservice
You0.5 dayYou approve a Jira agent account on the source site and share a Freshservice API key from an admin account. Your Freshservice admin pauses workflows and requester notifications.
Plan and category check
Both1 dayYour Freshservice plan is checked against the request types in scope, and ticket categories and catalog items are created for each one.
Migration
Day 3-7
Free sample
MigrateX1 day100 of your records, chosen for the largest attachments, the most internal comments and one request of each type, loaded into Freshservice end to end.
You review the sample
You1 dayYour team opens the tickets as an agent and as a requester, and checks private notes, original times in the date fields, and that no email went out.
Full load
MigrateX2-3 daysRequesters, departments and agents first, then tickets, then notes and attachments, then assets and articles, paced to your Freshservice plan.
Delta sync
MigrateX0.5 dayWork items changed in Jira since the full load are applied to the same Freshservice tickets, so no ticket is created twice.
Validation
Day 8-10
Reconciliation report
MigrateX1 dayWork items against tickets per space and year, comments against notes, attachments against files, plus every file that was linked instead of attached.
Sign-off and workflows back on
You1-2 daysYour leads check a random sample, the paused rules go back on, and Jira stays read-only until you agree.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
Known risks
Every known risk on this route, with how we handle it
- 3 solved
- 5 handled
- 01HandledMost critical
Jira files can be far larger than a Freshservice ticket holds
The problem
A single Jira file can be many times larger than the 40 MB Freshservice allows for all the files on one ticket together, so work items with logs, screen recordings or disk images do not fit.
How we handle it
We size every attachment during export and agree a rule with you: files that fit are attached to the matching note, and larger ones are kept in storage you own and linked from a private note at the place they sat.
Source: Freshservice API documentation, checked 15 Nov 2026
- 02HandledMost critical
Original created dates have to live in fields you can report on
The problem
Jira gives every work item and comment a created time. Freshservice does not document a way to set the original created date on import, so a migrated ticket can show the day it was loaded.
How we handle it
The original Jira created, resolved and closed times go into custom date fields on each Freshservice ticket, and your reports are pointed at them. How your account handles dates is confirmed during your free sample.
Source: Freshservice API documentation, checked 15 Nov 2026
- 03Solved
A mistyped email creates a second contact
The problem
Freshservice creates a new contact when a ticket arrives with an email it does not know. A customer who appears in Jira under one spelling and on tickets under another ends up as two requesters with split history.
How we handle it
Customers are loaded first, using the exact email Jira holds, and Jira organizations become departments before any ticket is written. The reconciliation report lists requesters created during the run so a stray one is caught.
Source: Freshservice API documentation, checked 15 Nov 2026
- 04Handled
Jira request types do not all have a Freshservice home
The problem
Freshservice splits incidents from service requests at the API level. Its service catalog and SLA management start on the Growth plan, and problem, change and release management on Pro. A Jira space with all of these cannot land complete on a Starter account.
How we handle it
We check your Freshservice plan against the request types in scope on the scoping call. Each Jira request type is mapped to a ticket category or a catalog item before the sample, and anything the plan cannot hold is listed for you to decide.
Source: Freshworks website, checked 15 Nov 2026
- 05Solved
A Jira export on the old search endpoints may stop working
The problem
Atlassian is removing the older Jira Cloud search endpoints, so an export written against them can stop working mid-project, and an export run under a customer-level account lists only public attachments.
How we handle it
The export uses the enhanced search with a page token and runs as a licensed agent, so internal comments and non-public attachments are read too. Work item counts per space and year are checked against Jira before anything is written to Freshservice.
Source: Atlassian developer documentation, checked 15 Nov 2026
- 06Handled
Freshservice workflows react to history as if it were new
The problem
Freshservice keeps running its workflows and business rules while data is loaded, and a plain public API load sends a large volume of notifications and emails. Migrated tickets can trigger assignments and messages to people who closed those requests years ago.
How we handle it
Your Freshservice admin pauses the Workflow Automator rules, business rules and requester notifications for the load window, and switches them back on after the delta sync. We check on the sample that no requester received a message.
Source: Freshservice support documentation, checked 15 Nov 2026
- 07Handled
Jira knowledge can be spread over several Confluence sources
The problem
A Jira knowledge base may be linked to more than one Confluence space, to a cross-site space, or to a third-party folder. A single export of one space leaves the rest behind.
How we handle it
We list every linked source on the scoping call and map each to a Freshservice solution category. Third-party folders are exported from the system that owns them.
Source: Atlassian Support, checked 15 Nov 2026
- 08Solved
Ticket creation on Freshservice is the slow end of this route
The problem
Jira can be read quickly, but each Freshservice ticket, note and attachment is a separate call against an allowance that depends on the plan, and Create Ticket alone is capped at 50 to 160 a minute.
How we handle it
We pace the load to your plan's allowance and read the Retry-After value on every 429. The longest threads and largest attachment sets start first, and the Jira export is finished early so Freshservice is never waiting.
Source: Freshservice API documentation, checked 15 Nov 2026
Technical profile
What makes this route technical
Jira Service Management is read through its enhanced search as a licensed agent, and Freshservice sets the pace and the limits on the way in through your plan's call allowance and its 40 MB per ticket for files.
- Exporting from Jira: the old search endpoints are going away
- Atlassian marks the older Jira Cloud search endpoints, GET and POST /rest/api/3/search, as deprecated and currently being removed, so an export has to page through the enhanced search instead.
Source: Atlassian developer documentation, checked 15 Nov 2026
- Exporting from Jira: internal comments are a separate switch
- The Get request comments endpoint of Jira Service Management lets a caller filter public and internal comments separately and returns 50 per page by default.
Source: Atlassian developer documentation, checked 15 Nov 2026
- Exporting from Jira: files can be 1 GB, or 2 GB if an admin raised it
- Jira Cloud's per-file attachment limit is 1 GB by default, and a Jira admin can raise the maximum to 2 GB.
Source: Atlassian Support, checked 15 Nov 2026
- Exporting from Jira: a knowledge base can have several sources
- A Jira Service Management knowledge base can draw on Confluence spaces, folders or pages, cross-site Confluence spaces and third-party folders, so its articles may not sit in one place.
Source: Atlassian Support, checked 15 Nov 2026
- Importing into Freshservice: 40 MB for every file on a ticket
- The total size of all attachments on one Freshservice ticket, counting the ticket and every note on it, cannot exceed 40 MB.
Source: Freshservice API documentation, checked 15 Nov 2026
- Importing into Freshservice: the Tickets API takes incidents only
- Freshservice's Tickets API supports only the incident ticket type, so service requests are created by placing a request on a service catalog item.
Source: Freshservice API documentation, checked 15 Nov 2026
- Importing into Freshservice: an unknown email becomes a new contact
- When a Freshservice ticket is created with an email that matches no contact, Freshservice adds a new contact for that address.
Source: Freshservice API documentation, checked 15 Nov 2026
- Importing into Freshservice: ticket creation is capped per plan
- Freshservice allows 50 Create Ticket calls a minute on Starter, 80 on Growth, 140 on Pro and 160 on Enterprise.
Source: Freshservice API documentation, checked 15 Nov 2026
- Importing into Freshservice: a note is private unless told otherwise
- A Freshservice note is private by default, and the user_id parameter creates it as another agent or user.
Source: Freshservice API documentation, checked 15 Nov 2026
- Importing into Freshservice: workflows are not muted by an import
- Freshservice says its workflows, business rules, Slack and Teams notifications keep running during a bulk migration and recommends muting them before it starts.
Source: Freshservice support documentation, checked 15 Nov 2026
Facts checked 15 Nov 2026 against Atlassian and Freshservice documentation. Each fact links its source.
Jira Service Management to Freshservice questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
How do we migrate from Jira Service Management to Freshservice?
An engineer reads your service spaces as a licensed agent through Jira's enhanced search, maps request types to tickets and catalog items with you, loads a free 100-record sample, then runs the full load paced to your Freshservice plan. A delta sync copies anything changed in Jira before cutover, and Jira stays read-only until you sign off.
Will Jira internal comments land as Freshservice private notes?
Yes. Internal comments are read separately from public ones and created as private notes, which Freshservice makes private by default. Public comments become replies and public notes. Each note is created as its original author, so agents see who wrote what.
What happens to Jira attachments that are larger than Freshservice allows?
They are linked, not attached. Freshservice caps all the files on one ticket at 40 MB together, while a single Jira file can be 1 GB. Files that fit are attached to the matching note, and larger ones go to storage you own with a link in a private note.
Do original created and resolved dates survive in Freshservice?
They are kept in custom date fields, because Freshservice does not document a way to set the original created date on import. Your reports are pointed at those fields. What your account does with a past date is confirmed during your free sample, before anything is committed.
Which Freshservice plan do we need for our Jira request types, problems and changes?
Service catalog and SLA management start on Growth, and problem, change and release management start on Pro. Starter has no service catalog. We check your plan against the request types in scope on the scoping call, and tell you before the sample what the plan cannot hold.
Does the Confluence knowledge base move into Freshservice solutions?
Yes. Each linked Confluence source is mapped to a solution category, folders keep the page tree, and pages become articles. A Jira knowledge base can draw on several spaces, cross-site spaces or third-party folders, so we list every source on the scoping call. Page permissions are set again in Freshservice.
Will Jira Assets become Freshservice assets with their relationships?
Yes, on request. Object types become asset types, objects become assets and references become relationships between assets, agents and requesters. Relationships are created last, once both ends exist. Assets Discovery schedules and Assets automation are set up again by your Freshservice admin.
Will customers get Freshservice emails while history is loading?
Not if your admin pauses the rules first. Freshservice keeps running workflows and business rules during an import and notes that a plain API load triggers many notifications. Your admin pauses Workflow Automator rules and requester notifications for the window, and we confirm on the sample that nothing was sent.
Can each Jira service space become its own Freshservice workspace?
Yes, on accounts that have workspaces. A ticket is created in a workspace by its workspace ID and stays there, because Freshservice moves a ticket between workspaces only through a separate Move operation. Spaces can also be merged into one workspace by agreement.
What does a Jira Service Management to Freshservice migration cost?
The price is set by what moves: work items and the comments and attachments on them, how many files pass 40 MB, assets and articles, and spaces. You get a fixed quote within 24 hours of the scoping call, after a free sample migration of 100 of your records.
How it compares
Four ways to run Jira Service Management to Freshservice
The same data, moved four different ways. This is what changes between them.
Object coverage (incidents, problems, changes, requests, KB)
MigrateX
Every object in the mapping on this page, plus the ones you ask for during scoping.
Automated migration software
Tickets and contacts are covered. Problems, changes and request items often are not.
Vendor CSV import
One object per file, and only the fields the export template exposes.
In-house scripts
Whatever you have time to build before the cutover date.
Work notes vs comments fidelity
MigrateX
Each entry is posted separately, private stays private, public stays public.
Automated migration software
Threads usually arrive, but per-entry author and visibility can be flattened.
Vendor CSV import
Notes collapse into one field on the ticket, if they come across at all.
In-house scripts
Possible, but it is the part teams most often run out of time for.
Attachments
MigrateX
Uploaded against the right note, and re-hosted with a link when they exceed the Freshservice cap.
Automated migration software
Supported up to the destination cap. Oversize files are skipped.
Vendor CSV import
Not carried by a CSV import.
In-house scripts
Needs its own download, retry and upload pipeline.
Original IDs cross-referenced
MigrateX
Every source id is stored on the destination record and handed back as a map.
Automated migration software
Often kept as a tag or a single text field.
Vendor CSV import
Lost once the file is imported.
In-house scripts
Only if you design the mapping table up front.
Delta sync before cutover
MigrateX
Included. Anything created or changed during the bulk pass is synced at cutover.
Automated migration software
Usually a paid upgrade on the top tier.
Vendor CSV import
You would re-export and re-import by hand.
In-house scripts
Requires change tracking and idempotent writes on both sides.
Rate-limit handling
MigrateX
Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.
Automated migration software
Backs off, but a long run can still stall and leave partial records.
Vendor CSV import
Not applicable, and the file size limits bite instead.
In-house scripts
The most common reason a home-grown run dies overnight.
Validation report
MigrateX
Counts per object and per status on both sides, with every default and placeholder listed.
Automated migration software
A run log and an error list, rather than a reconciliation.
Vendor CSV import
Row counts in a spreadsheet.
In-house scripts
You write the reconciliation queries yourself.
Rollback plan
MigrateX
Every write is tagged, so a batch can be reversed without touching your own records.
Automated migration software
Some approaches can clear a migration, some cannot.
Vendor CSV import
Manual cleanup of everything the import created.
In-house scripts
Only if you built the tagging in from the start.
Who does the work
MigrateX
A MigrateX engineer runs it and stays on the cutover call.
Automated migration software
You run the software. Support answers tickets.
Vendor CSV import
Your admins, one file at a time.
In-house scripts
Your engineers, instead of your roadmap.
Guides
Guides for a Jira Service Management to Freshservice migration
Related routes
Other routes we run
Built for your security review, from the first call.
Read how we handle your data
SOC 2 Type II
Independently audited controls over how we handle your data.
GDPR compliant
Data processing agreement available.
HIPAA compliant
Business associate agreement available.

Start your Freshservice move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.






