Migrating JSM to Freshdesk takes 10–18 business days via API. Biggest risks: admin attribution on comments, 20 MB attachment limits, and Freshdesk's per-endpoint rate caps (80 ticket creates/min on Growth).
There is no native migration path from Jira Service Management to Freshdesk; all ticket, comment, and attachment data must be extracted via the Jira REST API and loaded through the Freshdesk API. The fundamental data model difference is that JSM issues inherit a project → issue type → workflow hierarchy with Atlassian Document Format (ADF) rich text, while Freshdesk uses a flat ticket model with HTML content and integer-based status codes. Custom work is required to convert ADF to HTML, map Atlassian account IDs to email-based Freshdesk contacts, rebuild SLA policies and automation rules manually, and handle field-level transformations such as tag truncation and status compression. Teams with over 10,000 tickets or any custom fields should plan for an API-based migration taking 10–18 business days.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Quick Answer
A Jira Service Management (JSM) to Freshdesk migration is a medium-to-high complexity data transfer requiring API-based extraction and loading. Realistic timeline: 10–18 business days for most teams. The single biggest risk is losing author attribution on comment threads — if your migration script creates comments using a single admin API key without mapping the original author's user_id, every comment in Freshdesk appears as the admin. JSM SLA policies, automation rules, and Confluence knowledge base articles have no 1:1 equivalent in Freshdesk and must be manually rebuilt. Teams with under 10K tickets and no custom fields can use CSV for basic ticket data; everyone else should use an API-based approach or a managed migration service.
JSM API pagination trap
The JSM Service Desk API (/rest/servicedeskapi/) uses start/limit parameters, while the Jira platform API uses startAt/maxResults. Mixing these in a single extraction pipeline causes silent data truncation.
Trial account trap
If you test migration scripts on a Freshdesk trial account, the 50 requests/minute cap means even a modest 5,000-ticket test run will take hours and generate hundreds of 429 errors. Provision a paid Growth account before running meaningful tests.
Freshdesk notes that per-minute rate limits are rolling out in batches, so confirm the
Freshdesk notes that per-minute rate limits are rolling out in batches, so confirm the actual limit behavior in your target account before sizing the cutover window. (support.freshdesk.com)
Freshdesk enforces a 20 MB attachment limit per conversation on paid plans (15 MB on trial/free)
JSM issues with attachments exceeding this limit fail silently — the ticket is created but the attachment is dropped. Pre-scan your largest tickets first and split or archive oversized attachments before loading.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of Jira Service Management
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm Freshdesk can hold your support model
Walk your current workflow through Freshdesk: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated Jira Service Management → Freshdesk timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
Jira Service Management → Freshdesk specifics
- Complexity mismatch
- JSM is built for ITSM workflows — change management, asset management, incident queues. Teams doing pure customer support often find Freshdesk's UI faster to adopt.
- Atlassian ecosystem dependency
- JSM works best alongside Confluence and Jira Software. Teams that don't use the full Atlassian stack pay for overhead they never touch.
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full Jira Service Management export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the Jira Service Management export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in Jira Service Management where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
Jira Service Management → Freshdesk specifics
- JSM Request Types
- Freshdesk has no concept of request types with distinct portal forms per issue type. Workaround: use Freshdesk ticket forms (Enterprise plan only) or flatten into a custom dropdown.
- Linked Issues
- JSM supports parent/child and "blocks/is blocked by" relationships. Freshdesk has parent-child tickets but no arbitrary link types. Preserve other link references as private notes.
- Approvals
- JSM's built-in approval workflows have no Freshdesk equivalent. Archive approval history as notes.
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass Jira Service Management → Freshdesk field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the Jira Service Management → Freshdesk field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where Freshdesk has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
Jira Service Management → Freshdesk specifics
- Picklists/Enums
- Jira dropdown values must match the exact string values pre-configured in Freshdesk. If a Jira value doesn't exist in Freshdesk, the API rejects the ticket creation. Pre-create every destination enum before loading. (developer.atlassian.com)
- Rich Text
- JSM ADF JSON must be parsed and converted to HTML tags (<p>, <ul>, <strong>) to render correctly in Freshdesk.
- Statuses
- Convert JSM workflow states to Freshdesk integer status codes: 2=Open, 3=Pending, 4=Resolved, 5=Closed.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a Freshdesk sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Freshdesk sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under Freshdesk's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
Jira Service Management → Freshdesk specifics
- Field-level spot check
- Sample 5–10% of tickets. Verify status, priority, type, custom fields, assignee, and requester match the source.
- Conversation integrity
- For sampled tickets, verify comment count, author attribution, chronological order, and public/private visibility.
- Attachment integrity
- Open 20+ historical attachments in Freshdesk. Confirm PDFs open correctly, images render inline, and files are attributed to the correct conversation entry.
- Automation smoke test
- Trigger each rebuilt automation rule and confirm expected behavior.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in Freshdesk, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while Jira Service Management stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from Freshdesk's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze Jira Service Management and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep Jira Service Management read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile Jira Service Management and Freshdesk record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in Freshdesk, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep Jira Service Management read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
-
Record-count reconciliation
Total tickets in JSM (via JQL count) vs. total tickets in Freshdesk. The numbers must match exactly.
Jira Service Management → Freshdesk specifics
- SLA policy validation
- Create a test ticket in Freshdesk and verify SLA timers activate correctly.
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
JSM Freshdesk Object Mapping
| Jira Service Management field | Freshdesk field | Notes |
|---|---|---|
| Issue (Service Request / Incident) | Ticket | JSM Issue Keys (e.g., IT-123) cannot become Freshdesk Ticket IDs. Store the JSM key in a custom field like cf_jsm_key for searchability. |
| Comment (public) | Reply | Public comments map to Replies. Author must be matched by email/user_id. |
| Comment (internal) | Private Note | Internal comments map to Private Notes. |
| Reporter / Customer | Contact | Created via POST /api/v2/contacts. Deduplicate on email — duplicate submissions return HTTP 409. |
| Assignee (Agent) | Agent | Must be pre-provisioned in Freshdesk. Cannot be created via the ticket-create API. |
| Organization | Company | Load companies before tickets. Multi-org associations require custom Freshdesk configurations. |
| Project | Group (or Product) | No direct equivalent. Use Freshdesk Groups for agent routing or Products for multi-brand support. |
| Labels | Tags | Freshdesk enforces a 32-character limit per tag. JSM labels exceeding this are silently rejected. |
| Component | Tag or Custom Field | No native equivalent. Flatten into tags or a dropdown custom field. |
| Attachment | Attachment | Must download from JSM API, then upload to Freshdesk via multipart/form-data. 20 MB per-conversation limit on paid plans. |
| Request Participants | cc_emails + custom field or archive | No first-class participant collection in Freshdesk. Design a fallback rule. |
| Request Type | Ticket form, type field, tag, or custom field | Design choice, not a true 1:1 map. Freshdesk ticket forms require the Enterprise plan. |
| SLA Policy | SLA Policy | No migration path. Rebuild manually in Freshdesk Admin → SLA Policies. |
| Automation Rule | Dispatch'r / Observer / Supervisor | No migration path. Rebuild manually. |
| Knowledge Base (Confluence) | Solutions (Knowledge Base) | Requires a separate extraction and transformation pipeline. |
| Custom Fields | Custom Fields (prefixed cf_) | Must be pre-created in Freshdesk Admin before API writes. Use GET /api/v2/ticket_fields to discover API names. |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets | medium | JSM issue keys cannot become Freshdesk ticket IDs and must be stored in a custom field; Freshdesk lacks a built-in ticket external ID for idempotent upserts, requiring a local crosswalk table. |
| Comments / Conversations | high | Author attribution is easily lost if comments are not individually mapped from Atlassian accountIds to Freshdesk user IDs, and ADF content must be converted to HTML to render correctly. |
| Contacts | low | Contacts can be created via API or CSV import with email-based deduplication, and Freshdesk returns HTTP 409 on duplicates, making this a relatively safe operation. |
| Custom Fields | medium | All custom fields must be pre-created in Freshdesk Admin before API writes, and picklist values must match exactly or the API will reject the ticket creation. |
| Attachments | medium | Attachments must be individually downloaded from the JSM API and re-uploaded via multipart/form-data to Freshdesk, which enforces a 20 MB per-conversation limit on paid plans. |
| Tags / Labels | medium | Freshdesk enforces a 32-character limit per tag, and JSM labels exceeding this length are silently rejected, requiring truncation or remapping before loading. |
| SLA Policies | high | There is no automated migration path; JSM's calendar-based, JQL-conditioned SLA policies must be completely rebuilt manually in Freshdesk's priority-based model. |
| Organizations / Companies | low | Companies can be imported via CSV or API and should be loaded before tickets, though multi-org associations require custom Freshdesk configuration. |
| Knowledge Base Articles | high | Confluence knowledge base content requires a completely separate extraction and transformation pipeline with no native import path into Freshdesk Solutions. |
| Linked Issues / Approvals | medium | JSM's arbitrary link types and built-in approval workflows have no Freshdesk equivalent and must be archived as private notes, resulting in reduced functionality. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Comment Author Attribution Loss
If historical comments are created using a single admin API key without mapping each original author's Atlassian accountId to a Freshdesk user_id, all comments appear as authored by the admin account.
ADF to HTML Conversion
JSM stores descriptions and comments in Atlassian Document Format (a proprietary JSON structure) that must be parsed and converted to standard HTML before loading into Freshdesk.
Freshdesk API Rate Limits
Freshdesk enforces account-wide per-minute rate limits with per-endpoint sub-limits, meaning a history-preserving migration of 100K tickets on a Growth plan requires a minimum of ~42 hours of continuous error-free execution.
Workflow State Compression
JSM's multi-level workflow states with custom transitions must be compressed into Freshdesk's four linear integer status codes (Open, Pending, Resolved, Closed), requiring a deliberate mapping strategy.
SLA and Automation Rebuilds
JSM SLA policies (calendar-based with JQL conditions) and automation rules have no migration path and must be manually rebuilt in Freshdesk using its distinct business-hour and priority-based models.
Identity Model Mismatch
JSM uses opaque Atlassian accountIds while Freshdesk uses email as the primary contact identifier, requiring every author and reporter to be resolved from accountId to email and then matched or created in Freshdesk.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate Jira Service Management to Freshdesk without losing data?
Yes, if you use an API-based migration. CSV exports from JSM do not include comment threads, attachments, or custom field relationships. An API-based approach extracts all ticket data including conversations and attachments, preserving full history in Freshdesk. The key requirement is building a user-mapping table to maintain correct author attribution on every conversation entry.
How long does a Jira Service Management to Freshdesk migration take?
A typical migration takes 10–18 business days end-to-end: 2–3 days for discovery and mapping, 3–5 days for script development, 2–3 days for test migration, 2–3 days for UAT, and 1–2 days for production load and cutover. Volume, custom field complexity, and attachment count are the primary variables.
What Jira Service Management data cannot be migrated to Freshdesk?
Automation rules, SLA policies, approval workflows, linked issue relationships (beyond parent-child), request participants, multi-cycle SLA records, and audit/change logs have no migration path to Freshdesk. These must be rebuilt manually or archived externally. Confluence knowledge base articles require a separate migration pipeline.
Does Freshdesk have an official Jira Service Management import tool?
No. Freshdesk does not offer a native import tool for JSM data. You can use Freshdesk's CSV importer for basic ticket data, but it does not support comments, attachments, or custom field relationships. API-based migration or a third-party tool is required for complete data transfer.
How much does a JSM to Freshdesk migration cost?
Costs vary by method. A DIY API-based migration costs 2–3 weeks of engineering time (roughly $5K–$15K in loaded labor). Third-party SaaS tools charge per-record fees, typically $2K–$8K for 50K tickets. Managed migration services range from $3K–$20K depending on volume, custom fields, and zero-downtime requirements.