Skip to content
Get a quote

Jira Service Management to Freshdesk migration

We migrate Requests, Service Projects, Agents, and conversation history from Jira Service Management into Freshdesk Tickets, Groups, and Agents, resolving the Request Type-to-Ticket Field schema, reconstructing SLA goals from JSM Premium, and flagging Confluence Knowledge Base visibility before any data moves.

Short answer

FlitStack AI migrates tickets, products, ticket field configurations, agents and sla policies from Jira Service Management to Freshdesk, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

By

Source Jira Service Management
DestinationFreshdesk
TicketProductTicket Field ConfigurationAgentSLA Policy
Mapped field by field · sample run · one-click rollback

What moves from Jira Service Management to Freshdesk?

Moving from Jira Service Management to Freshdesk is a platform-model migration, not a straight record copy.

Read the full summary

JSM uses Service Projects with Request Types, SLA definitions, and a separate customer portal; Freshdesk uses a unified Ticket object with customizable Ticket Fields and a single agent-facing interface. Requests map to Tickets on a per-project basis, but the Request Type schema must be translated into Freshdesk Ticket Field configurations before import. SLA definitions on JSM Premium move as Freshdesk SLA policies with calendar and first-response/resolve goals reconstructed from JSM's SLA goal data. Automation rules, Jira user actors, and Jira-specific workflow conditions do not migrate; we deliver a written automation inventory for the customer admin to rebuild in Freshdesk. The Knowledge Base lives in Confluence on the JSM side and must be re-associated with Freshdesk's Helpspot-style articles, with visibility flags explicitly checked to prevent migrated Confluence pages from going public unintentionally.

1:1

Request → Ticket

JSM Requests map to Freshdesk Tickets on a per-project basis.

How it maps

Summary maps to Freshdesk subject, description maps to ticket body as HTML, priority maps to Freshdesk priority (urgent/high/medium/low), and status maps to Ticket status (open/pending/resolved/closed). We use JSM's issue key as a custom field ticket_reference__c for cross-system audit. Custom fields on the Request Type translate to Freshdesk Ticket Fields of equivalent type. The JSM issue key becomes a custom reference field on the Freshdesk Ticket for audit trail continuity.

1:1

Service Project → Product

JSM Service Projects map to Freshdesk Products, which organize Tickets by product or service line.

How it maps

Each JSM project portal URL is preserved as a Product external_url__c custom field for reference. Portal branding, email request channels, and chat configuration from the JSM project are noted as manual reconfiguration items post-migration since Freshdesk's product-level settings include portal page configuration that differs structurally from JSM's portal editor.

configuration

Request Type → Ticket Field Configuration

JSM Request Types define the intake form shown to portal customers.

How it maps

Each Request Type's field schema maps to a Freshdesk Ticket Field group. We translate JSM custom field types (text, dropdown, multi-select, date, user picker) to Freshdesk field types. Request Type visibility flags on the JSM portal do not have a direct Freshdesk equivalent; we set visibility on the Freshdesk portal section level instead. This is a manual configuration step after import with the customer admin.

1:1

Agent (JSM) → Agent

JSM Agents (billed users who resolve tickets) map to Freshdesk Agents by email.

How it maps

JSM's agent permission levels (admin, user, jira-software-user) map to Freshdesk's agent permission groups (agent/admin). JSM Customers (portal-only users who submit but cannot resolve) map to Freshdesk Contacts if they need agent-level access or remain as unauthenticated requesters on the Freshdesk portal if not. We set agent_type on every imported user based on the JSM user type to prevent unintended Freshdesk agent seat expansion.

1:1

SLA Definition → SLA Policy

JSM SLA definitions with goal minutes, starting conditions, and pause conditions map to Freshdesk SLA policies on Growth tier and above.

How it maps

We reconstruct the SLA calendar from JSM's business hours configuration and create Freshdesk SLA policies with first-response and resolution goals matching the JSM source. JSM's SLA breach actions (notify, escalate) translate to Freshdesk SLA violation actions. If the destination Freshdesk plan is lower than Growth, SLA policies are not available and SLA goals are logged as custom ticket fields for reference rather than enforced.

1:1

Comment / Conversation → Conversation

JSM Request comments (public portal replies and internal notes) map to Freshdesk Conversations.

How it maps

Public comments from customers map to Freshdesk incoming conversations; agent comments map to outgoing conversations. Internal JSM notes require Freshdesk's private note feature which is available from Pro tier. If the destination is on Growth, internal notes migrate as ticket_field_value entries on a dedicated internal_note__c custom field rather than as native private notes. Author, timestamp, and HTML body are preserved.

What moves10 objects
Jira Service ManagementFreshdesk
  • RequestTicket1:1
  • Service ProjectProduct1:1
  • Request TypeTicket Field Configurationtransformed
  • AgentAgent1:1
  • SLA DefinitionSLA Policy1:1
  • CommentConversation1:1

+ 4 more in the mapping below

How Jira Service Management and Freshdesk differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionJira Service ManagementFreshdesk
Agent count on free tier3 agents permanently freeFree plan for 1 agent; Unlimited Agents plan free up to 10 agents
Ticket modelRequests inside Service Projects with Request Type schemaTickets with customizable Ticket Fields and single product view
SLA modelSLA goals and escalation policies per project, Premium-gatedSLA policies with business hours and first-response/resolve goals from Growth tier onward
User rolesAgents (billed) separate from portal-only CustomersAgents with granular permission sets; no separate customer portal user type
Knowledge Base locationConfluence spaces linked to Service ProjectsFreshdesk Knowledge Base with articles, categories, and portal sections
Automation modelAutomation rules with Jira user actors, Premium-gated execution capsScenario Automations with triggers and actions; freshdesk bot (Freddy) from Pro tier
Pricing structurePer-agent at Standard ~$20/agent/mo and Premium ~$38/agent/mo, both annualGrowth ~$29/agent/mo, Pro ~$49/agent/mo, Enterprise custom; annual discount available

What to watch for in a Jira Service Management to Freshdesk migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Confluence KB articles may go public on migration

JSM Knowledge Base articles live in Confluence with space-level and page-level permissions that do not translate directly to Freshdesk's article visibility model.

How we handle it

A documented migration case showed internal manuals (sales rep materials with restricted Confluence permissions) automatically made public in Freshdesk after Confluence export. We explicitly check each Confluence article's permissions before migration, set Freshdesk article visibility to restricted section or draft for anything without an explicit public flag, and deliver a visibility audit report listing every article and its recommended Freshdesk visibility setting for the customer admin to confirm.

high

Internal notes require Pro tier or become custom fields

JSM separates public portal comments from internal notes (visible only to agents).

How we handle it

Freshdesk's private note feature is available from the Pro tier ($49/agent/month). If the destination Freshdesk is on Growth tier ($29/agent/month), internal JSM notes do not have a native equivalent. We migrate them as structured entries in a dedicated internal_note__c custom ticket field. This is documented explicitly during scoping so the customer can decide whether to upgrade to Pro or accept the custom field approach before migration begins.

medium

JSM automation rules do not migrate to Freshdesk Scenario Automations

JSM automation rules include trigger conditions, action blocks, and Jira user actor references that do not have direct Freshdesk Scenario Automations equivalents.

How we handle it

Atlassian's own JSM-to-Freshdesk migration app (available on the Atlassian Marketplace) excludes automation rules from migration scope, consistent with Freshdesk's different automation model. We do not migrate automation rules as code. We deliver a written inventory of every JSM automation rule with its trigger, conditions, actions, and recommended Freshdesk Scenario Automations equivalent for the customer's admin to rebuild.

medium

Request Type schema requires field-by-field translation

JSM Request Types define intake forms with project-specific custom fields that vary per JSM project.

How we handle it

Freshdesk uses a unified Ticket Field model. Each JSM custom field must be mapped to a Freshdesk Ticket Field of equivalent type before import. Dropdown fields with specific option values require Freshdesk field options created in advance of the ticket import. We handle this with a pre-import field creation pass, but any changes to the JSM Request Type schema during the migration window require a corresponding Freshdesk field update before the delta migration runs.

medium

SLA policies unavailable on Freshdesk Growth and below

Freshdesk's SLA policy feature is available from Growth tier ($29/agent/month) onward.

How we handle it

JSM SLA definitions on Standard tier migrate as Freshdesk SLA policies if the destination is on Growth or above. If the destination Freshdesk plan is lower than Growth, SLA goals are recorded as custom ticket fields rather than enforced natively, and the customer receives a written list of SLA mappings that can be reactivated if they upgrade. We confirm the destination plan tier during scoping and surface this gap as a decision point before any data moves.

How the migration runs

  1. Discovery and scoping

    We audit the JSM instance across project count, Request Type schemas per project, custom field types, SLA definitions, user list (agents vs. portal customers), comment and attachment volume, Confluence Knowledge Base spaces, and any JSM automation rules.

    What this step covers

    We pair this with a Freshdesk plan review to confirm whether the destination is on Growth or Pro and whether SLA policies and private notes will be available natively. The discovery output is a written migration scope with a JSM-project-to-Freshdesk-Product mapping, a Request-Type-to-Ticket-Field translation plan, and a Confluence article visibility audit list.

  2. Schema design and Freshdesk field configuration

    We create Freshdesk Ticket Fields to match each JSM Request Type field, build the Product list from JSM Service Projects, configure Freshdesk SLA policies from JSM SLA definitions (if the plan tier supports them), and set up agent permission groups to mirror JSM's agent roles.

    What this step covers

    For Confluence articles, we pre-create Freshdesk article sections and categories matching the JSM project's knowledge base structure and prepare the visibility settings for each article. All Freshdesk schema configuration happens in a sandbox or trial org before any data import.

  3. User reconciliation and agent provisioning

    We extract every distinct JSM user from the Request records and comments and match by email against the Freshdesk agent list.

    What this step covers

    JSM agents become Freshdesk agents; JSM portal customers become Freshdesk Contacts. Any JSM user without a matching Freshdesk account goes to a reconciliation queue for the customer's admin to provision before the main import. Migration cannot proceed past user provisioning because Ticket assignee and conversation author references require a valid Freshdesk agent or contact ID.

  4. Data export from JSM and Confluence

    We export Requests via the Jira Cloud REST API in batches, pulling standard fields, custom fields, comments, attachments, and change history.

    What this step covers

    Attachments are downloaded from Atlassian's CDN in parallel batches. SLA definitions export as structured JSON from the SLA policies API. For Knowledge Base articles, we export Confluence pages via the Confluence REST API, stripping Confluence storage format and converting to HTML, and we capture the Confluence space and page permission data to drive the Freshdesk visibility settings during import.

  5. Data transformation and import in dependency order

    We transform exported JSM data into Freshdesk API payloads: Requests become Tickets with the Ticket Field mapping applied, Service Projects become Freshdesk Products, agents become Agents, customers become Contacts, comments become Conversations, and attachments re-upload to the relevant Ticket or Conversation.

    What this step covers

    SLA definitions create Freshdesk SLA policies before ticket import so that SLA goals are enforced from the first ticket. Confluence articles import after the Freshdesk article sections and categories are created. Import runs in dependency order: agents and contacts first, then products, then tickets with SLA assignments, then conversations and attachments.

  6. Cutover, delta sync, and automation handoff

    We freeze JSM writes during cutover, run a delta migration of any Requests created or modified after the main export window, then enable Freshdesk as the system of record.

    What this step covers

    We deliver the Confluence article visibility audit report, the JSM automation rule inventory with Freshdesk Scenario Automations equivalents, and the Request-Type-to-Ticket-Field mapping reference document to the customer admin. We support a one-week hypercare window for reconciliation issues. We do not rebuild JSM automation rules as Freshdesk Scenario Automations within the migration scope; that is a separate engagement or an internal admin task.

Jira Service Management Freshdesk
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · FreshdeskRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
8-12 weeksLarge or heavily customised accounts

A quote scales with record volume, custom field complexity, and SLA policy reconstruction scope. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Jira Service Management to Freshdesk →

Why teams move from Jira Service Management to Freshdesk

  • JSM's free tier caps at three agents while Freshdesk's Free plan supports one agent and its Unlimited Agents plan supports up to ten agents without a per-agent charge, letting smaller IT teams migrate at no incremental software cost. A sysadmin on r/sysadmin noted the free tier as a primary driver for switching, calling it a universally popular move for teams under ten agents who found JSM's pricing ceiling premature for their scale.
  • JSM's interface carries Jira's developer-first navigation, creating adoption friction for HR, facilities, and finance teams that need a support portal without Jira project management overhead. A review on eesel.ai specifically describes Freshdesk as ideal for customer support teams with intuitive multi-channel management versus JSM's better fit for agile and DevOps workflows, making the switch a practical choice for organizations centralizing non-technical service requests.
  • JSM's per-agent automation execution cap (1,000/user/month in Premium) constrains high-volume IT support operations and forces teams to purchase Enterprise for unlimited executions. Freshdesk's Scenario Automations carry no per-user execution cap on Pro and Enterprise, and the Freddy AI bot for ticket routing and summarization ships on Pro tier without additional per-action costs, making the automation economics substantially more predictable for growing support teams.
  • Atlassian's 2026 points-based API rate limiting changed the throttling model for Forge, Connect, and OAuth 2.0 (3LO) apps, breaking integrations that rely on app-based tokens. Visor.ai's documented JSM-to-Freshdesk migration cited a concrete annual contract renewal deadline as the trigger for their switch, with API rate limit unpredictability contributing to integration instability on the JSM side. Freshdesk's REST API uses a per-minute rate model without a points multiplier, making integration predictability more manageable for teams with high API call volumes.
  • Teams using JSM's Confluence-hosted Knowledge Base find that articles carry Confluence space permissions that do not translate to Freshdesk's article visibility model, risking accidental publication of internal-only manuals during migration. The documented Visor.ai migration specifically encountered this issue, with internal sales rep manuals automatically made public in Freshdesk, requiring post-migration cleanup. Migrating to Freshdesk's native Knowledge Base forces a visibility audit that organizations often defer until the migration surfaces the problem anyway.

Questions, answered

Jira Service Management to Freshdesk migration questions

How long does a Jira Service Management to Freshdesk migration take?

Straightforward migrations under 15,000 Requests, a single JSM project, and no Confluence Knowledge Base export land between three and five weeks. Migrations with multiple JSM projects, complex Request Type schemas, large comment and attachment histories, or a Confluence Knowledge Base with dozens of articles move to eight to twelve weeks because of the field-by-field Request Type translation, the Confluence visibility audit, and SLA policy reconstruction work.

Do JSM automation rules migrate to Freshdesk Scenario Automations?

No. JSM automation rules use Jira-specific triggers (such as issue-assignment events and Jira user actor references) that have no direct Freshdesk Scenario Automations equivalent. We do not migrate automation rules as code. We deliver a written inventory of every active JSM automation rule with its trigger, conditions, and actions, plus a recommended Freshdesk Scenario Automations configuration for the customer admin to implement post-migration. SLA breach notifications, escalation policies, and JSM Premium automation execution caps are explicitly noted in the inventory.

What happens to JSM's Knowledge Base articles during migration?

JSM Knowledge Base articles live in Confluence. We export articles from the linked Confluence spaces, convert them to Freshdesk-compatible HTML, and import them as Freshdesk Knowledge Base articles. The Confluence page permissions do not translate automatically, so we check each article's Confluence permission and set Freshdesk article visibility to match. Any article without an explicit restricted permission is flagged in a visibility audit report for the customer admin to review before publishing. Internal-only manuals and sales documents are set to draft or restricted in Freshdesk unless the customer explicitly approves making them public.

What data is lost in a JSM to Freshdesk migration?

Automation rules, SLA breach audit logs, JSM customer portal branding (reapplied manually), Confluence-specific page permissions, Jira user actor references in automation rules, and any JSM automation execution history are not migratable. Service Projects map to Freshdesk Products but project-level portal email configurations require manual re-setup in Freshdesk. The full ticket text, comments, attachments, change history, SLA goals, and article content transfer. Internal JSM notes on Growth-tier Freshdesk migrate as a custom ticket field rather than as native private notes unless the destination plan is Pro or above.

Can we keep Jira Software while moving support to Freshdesk?

Yes. A hybrid stack is a common pattern. Jira Software continues to handle software development tracking, sprints, and engineering issue management. Freshdesk takes over IT and employee service desk, customer support, and the Knowledge Base. We do not migrate Jira Software project data as part of the JSM-to-Freshdesk scope. If the customer uses JSM's change management module that pulls deployment context from Jira Software, that integration does not have a Freshdesk equivalent and should be documented as a separate integration requirement for the customer's Jira admin.

What happens to JSM's SLA definitions during migration?

JSM SLA definitions with goal minutes, starting conditions, pause conditions, and breach actions map to Freshdesk SLA policies if the destination Freshdesk plan is Growth ($29/agent/month) or above. We reconstruct the SLA calendar from JSM's business hours configuration and create Freshdesk SLA policies with first-response and resolution goals matching the JSM source. If the destination is on a lower plan, SLA goals migrate as custom ticket fields for reference but are not enforced natively. We surface this as a decision point during scoping so the customer can choose the right Freshdesk tier before migration begins.

Get a quote

Moving from Jira Service Management to Freshdesk?

Tell us roughly how many records and objects you have. We scope the mapping and the Freshdesk setup with you, then send a quote.

Get a quote