---
title: "Jira Service Management to Intercom Migration | FlitStack AI"
description: "Migrate Jira Service Management to Intercom with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/helpdesk/jira-service-management/to/intercom"
---

# Jira Service Management to Intercom migration

We migrate Requests, Customers, Comments, and Attachments from Jira Service Management into Intercom as Conversations and Contacts, preserving comment timestamps and author attribution while flagging the SLA and asset gaps that require post-migration configuration or admin rebuild.

Short answer

FlitStack AI migrates conversations, contacts, users, messages and attachments from Jira Service Management to Intercom, 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: 2-4 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/helpdesk/jira-service-management/to/intercom#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Jira Service Management ![](https://flitstack.ai/platforms-trim/jira-service-management.webp)

Destination Intercom ![](https://flitstack.ai/platforms-trim/intercom.webp)

Conversation Contact User Message Attachment

Mapped field by field · sample run · one-click rollback

## What moves from Jira Service Management to Intercom?

Moving from Jira Service Management to Intercom is a shift from an IT-service-management platform built on Jira's issue model to a customer-experience platform built on conversation threads.

Read the full summary

JSM represents support as Requests with a structured workflow and SLA clock; Intercom represents it as Conversations with a message timeline and resolution state. We map JSM Requests to Intercom Conversations, JSM Customers to Intercom Contacts, and preserve comment history with original author attribution. SLA definitions, service project configurations, request type schemas, and Knowledge Base articles migrate as written inventories for Intercom admins to rebuild using Intercom's Articles and SLA products. Automation rules and workflow configurations do not migrate as code; we deliver a written rulebook covering every JSM automation trigger and action so the destination team can rebuild in Intercom's Workflow Builder. Asset records in JSM's object schema have no direct Intercom equivalent and are flagged for a dedicated reconciliation pass.

1:1

### Request → Conversation

JSM Requests map to Intercom Conversations.

How it maps

The Request summary becomes the Conversation subject, description becomes the initial message body, and status (Open, Pending, Resolved, Closed) maps to Intercom's open, closed, or snoozed states. We preserve the original created\_at and updated\_at timestamps from Jira. Request priority (Low, Medium, High, Critical) migrates as a custom conversation attribute. Linked SLA status migrates as a custom attribute if the destination Intercom plan includes SLA tooling.

1:1

### Customer → Contact

JSM customers (portal users who submit requests) map to Intercom Contacts by email.

How it maps

The customer's display name, email, and any Jira user properties (department, organization) migrate as Contact attributes. JSM agents who are also customers (dual-role) are set as Intercom Users first, then added as Contacts if their contact identity is needed for customer-initiated conversations.

1:1

### Agent → User

JSM agents (licensed resolvers) map to Intercom Users.

How it maps

We resolve by email match and assign to the corresponding Intercom Inbox. Agent role hierarchy (Admin, Agent, Requester-only) maps to Intercom's admin, agent, and viewer roles. The agent's Jira group membership is preserved as an attribute for inbox routing configuration post-migration.

1:1

### Comment → Message

JSM comments on requests map to Intercom Conversation parts.

How it maps

Public comments become Intercom user messages; internal notes become Intercom internal notes. Author attribution migrates by resolving the Jira user email to an Intercom User or Contact. Timestamps are preserved to maintain conversation sequence. Attachments within comments migrate as part of the attachment batch.

1:1

### Attachment → Attachment

File attachments on JSM requests and comments are downloaded from Atlassian's CDN and re-uploaded to the corresponding Intercom Conversation part.

How it maps

Large attachment batches (over 500 files or 10 GB total) are chunked and processed in parallel to avoid timeout. We preserve original filenames and detect file type from MIME headers.

configuration

### Service Project → Inbox

Each JSM Service Project maps to an Intercom Inbox.

How it maps

The project's portal settings, request type list, and team permissions map to the Inbox's routing rules and team membership. Multi-project JSM instances create multiple Intercom Inboxes, which the Intercom admin consolidates or routes between post-migration. The Inbox name and visibility settings are configured before conversation import begins.

******What moves 12 objects

Jira Service Management Intercom

- Request Conversation 1:1
- Customer Contact 1:1
- Agent User 1:1
- Comment Message 1:1
- Attachment Attachment 1:1
- Service Project Inbox transformed

\+ 6 more in the mapping below

## How Jira Service Management and Intercom 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.

| Dimension               | Jira Service Management                                                      | Intercom                                                                                        |
| ----------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Primary object model    | Request (issue-based) with structured workflow and SLA clock                 | Conversation (message thread) with resolution state and assignee                                |
| Customer representation | Portal customers vs licensed agents with separate user types                 | Contacts and Users unified under a single contact model                                         |
| SLA tracking            | Project-level SLA definitions with goals, start conditions, pause conditions | Intercom SLA tool (Premium plans) with inbox-level and conversation-level targets               |
| Knowledge management    | Knowledge Base articles in Confluence spaces linked to JSM projects          | Intercom Articles with collections, sections, and in-app placement                              |
| Automation scope        | Automation rules with triggers, conditions, and Jira-specific actions        | Workflow Builder with conversation triggers, conditions, and actions scoped to Intercom objects |
| Pricing model           | Per-agent (licensed resolvers) with Free tier up to 3 agents                 | Conversation-based with Starter at $39/seat/month plus conversation packs                       |
| Asset tracking          | Object schemas and object types with cross-reference support (CMDB)          | No native asset or configuration management; requires third-party or custom build               |

## What to watch for in a Jira Service Management to Intercom migration

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

high

### JSM SLA definitions and breach history have no native Intercom equivalent

JSM stores SLA definitions as project-level objects with goals, starting conditions, and pause conditions.

How we handle it

Intercom's SLA product applies forward-looking targets to conversations, not historical breach records. We preserve JSM SLA breach history as conversation attributes during migration, but SLA goal and pause condition logic cannot transfer as Intercom SLA rules. If the customer relies on SLA reporting for ITSM compliance, we recommend scheduling a separate Intercom SLA configuration sprint with the Intercom admin after migration. SLA Premium features in JSM also require JSM Premium; if the source was on Standard, SLA data may be incomplete.

high

### Automation rules and workflow configurations do not migrate as code

JSM automation rules use Jira-specific triggers (time in status, issue created, field changed) and actions (transition issue, send email, assign, create sub-task) that have no direct Intercom Workflow Builder equivalent.

How we handle it

We export the automation rule JSON and deliver a written inventory with trigger, condition, action, and recommended Intercom Workflow mapping. The customer's Intercom admin or implementation partner rebuilds rules post-migration. Skipping this step leaves new conversations without escalation routing, auto-closure, or SLA warning notifications.

medium

### JSM-Intercom sync issues are documented in the Atlassian Community

Atlassian Community reports (November 2025) document an active sync issue where Jira tickets linked to Intercom conversations stop updating comments and status changes.

How we handle it

This affects teams using the Jira-Intercom integration app. During migration scoping, we identify any active Jira-Intercom webhook or app connections and disable them before migration to prevent bidirectional write conflicts. After migration, the customer decides whether to re-enable the integration or rebuild linking logic using Intercom's outbound webhook API.

medium

### Knowledge Base article dates reset to migration date

Confluence-based Knowledge Base articles migrated to Intercom Articles inherit the migration timestamp rather than the original Confluence creation or publish date.

How we handle it

This is a known Intercom Articles import behavior. We document the original article dates in a supplementary CSV so the customer can manually restore publish dates post-migration if article recency is used for search ranking or internal policy purposes.

low

### CC users and inline images require non-standard handling

JSM CC users (additional participants on a request who are not the requester or assignee) have no Intercom equivalent.

How we handle it

We map CC users to a Conversation tag and optionally to a custom Contact attribute for visibility. Inline images in JSM comments are hosted on Atlassian's CDN and require re-upload to Intercom's CDN; we handle this as part of the attachment migration batch but flag any images exceeding Intercom's 10 MB per-file limit for manual re-upload.

## How the migration runs

1. ### Discovery and scope definition

   We audit the source JSM instance across project count, request type schemas, custom field inventory, SLA definitions, active automation rules, Knowledge Base Confluence spaces, and attachment volume.

   What this step covers

   We pair this with a review of the destination Intercom workspace: plan tier, existing Inboxes, installed apps, and current Workflow Builder rules. The discovery output is a written migration scope that identifies every object that transfers, every object that requires rebuild documentation, and any plan-tier constraints (Intercom SLA requires a Starter plan or above; Intercom Articles requires a specific plan tier).

2. ### Schema pre-creation and field mapping design

   We pre-create the Intercom workspace structure: Inboxes (one per JSM Service Project), Collections (for Knowledge Base articles), custom Contact attributes (for JSM custom fields), and conversation tags (for JSM Request Types).

   What this step covers

   We design the field mapping document covering every JSM Request field, Comment field, and Customer property, mapping each to an Intercom Conversation part, Contact attribute, or conversation tag. Schema is validated in an Intercom sandbox workspace before production migration begins.

3. ### User and contact reconciliation

   We extract every distinct JSM customer email and agent email.

   What this step covers

   Customers resolve to Intercom Contacts by email match. Agents resolve to Intercom Users by email match and are assigned to Inboxes. Any JSM user without a matching Intercom account is held in a reconciliation queue for the customer's Intercom admin to provision. JSM CC users are mapped to tags rather than contacts because Intercom has no CC equivalent.

4. ### Knowledge Base migration

   We export Confluence articles from linked JSM spaces via the Confluence REST API, strip Confluence-specific macros and formatting that Intercom does not render, and import articles into Intercom Collections and Sections.

   What this step covers

   We preserve article titles, body content, and image references (re-uploaded to Intercom's CDN), and document the original Confluence publish dates in a supplementary CSV. The article URL structure and internal linking are noted for the customer's admin to update post-migration.

5. ### Conversation import in dependency order

   We run production migration in record-dependency order: Contacts and Users first (so author attribution resolves), then Conversations (Requests mapped to Intercom Conversations with initial message body from description), then Conversation parts (Comments mapped to message parts and internal notes), then Attachments (processed in batches to handle size constraints).

   What this step covers

   SLA breach history migrates as conversation attributes in a separate pass after conversations are created. Each phase emits a row-count reconciliation report before the next phase begins.

6. ### Cutover, delta pass, and automation handoff

   We freeze JSM writes during cutover, run a final delta migration of any requests modified during the migration window, then enable Intercom as the system of record.

   What this step covers

   We deliver the automation rule inventory document, the SLA configuration guide, and the Knowledge Base article URL mapping to the customer's Intercom admin. We support a one-week hypercare window where we resolve any record reconciliation issues. We do not rebuild JSM automation rules as Intercom Workflow Builder code inside the migration scope; that is a separate Intercom implementation engagement.

![](https://flitstack.ai/platforms/jira-service-management.svg) Jira Service Management ![](https://flitstack.ai/platforms/intercom.svg) Intercom

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Intercom Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**2-4 weeks** Typical, smaller accounts

**4-8 weeks** Large or heavily customised accounts

A quote scales with request volume, attachment size, custom field complexity, and whether SLA and automation rebuilds are in scope. JSM and Intercom subscription costs remain the customer's separate recurring spend. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Jira Service Management to Intercom →](https://flitstack.ai/contact)

## Why teams move from Jira Service Management to Intercom

- End users found JSM's interface too developer-centric for day-to-day support work, causing tickets to pile up because requesters avoided the portal. Intercom's messenger-first experience reduces the clicks to submit and resolve a conversation, which operational teams report directly lowers backlog growth and improves MTTR. Reddit reviewers who moved noted that simpler interfaces eliminated the need for constant user education.
- JSM integrations with Slack, Active Directory, and asset tracking required workarounds and broke frequently during Atlassian updates. Intercom's native integrations with Slack, Salesforce, HubSpot, and Segment are AppExchange-adjacent and maintained at Intercom's velocity rather than relying on Atlassian Forge apps that catch up late to API changes. Teams managing multi-tool stacks report fewer broken connections after switching.
- JSM's ITSM template approach requires significant customization to handle normal HR, facilities, and customer-facing support workflows. Reviewers on Capterra and TrustRadius cite steep learning curves, inflexible configuration, and the need for constant Jira admin involvement as friction points that Intercom's visual Workflow Builder and inbox routing replace with faster time-to-configuration for non-technical teams.
- JSM lacks native live chat, chatbot, custom reporting, and telephony features that modern customer support stacks bundle. Intercom's Fin AI Agent, proactive outbound messaging, and in-app product tours fill gaps that JSM closes only through third-party integrations. Teams that consolidated onto Intercom report reduced tool sprawl and lower total monthly SaaS spend.
- Reporting in JSM for non-ITSM audiences often ends up in exported spreadsheets because the native dashboards are Jira-centric. Intercom's reporting covers conversation volume, first response time, CSAT, and revenue attribution without export work. Teams switching report that support managers can self-serve reporting without Jira admin access.

Questions, answered

## Jira Service Management to Intercom migration questions

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

Migrations under 10,000 requests, 2,000 contacts, and no Knowledge Base article migration land between two and four weeks. Migrations with large attachment batches (over 50 GB), multi-project JSM setups, Confluence Knowledge Base migration, or historical SLA record preservation move to four to eight weeks because of attachment chunking, article restructuring, and SLA reconciliation work. Migration partner timelines from SaaSy (Intercom Gold Partner) confirm this range for mid-market complexity levels.

Do JSM Automation Rules and SLA definitions migrate to Intercom?

Automation rules do not migrate as Intercom Workflow Builder code. JSM automation rules use Jira-specific triggers and actions (transition issue, send email, create sub-task) that have no direct Workflow Builder equivalent. We deliver a written automation inventory with trigger, condition, action, and recommended Intercom Workflow mapping so the customer's admin rebuilds them. SLA definitions are preserved in a structured JSON document; if the destination Intercom plan includes SLA tooling, we configure inbox-level SLA targets matching the JSM definition. Historical SLA breach records transfer as conversation attributes.

Can we migrate our JSM Knowledge Base articles to Intercom Articles?

Yes. Confluence articles linked to JSM projects migrate to Intercom Articles within Collections and Sections. We preserve article titles, body content, and image references (re-uploaded to Intercom's CDN). Note that article publish dates reset to the migration date; we document original dates in a supplementary CSV for manual restoration. Article URL structure and internal Confluence links require post-migration updates.

What happens to our JSM Assets and CMDB data?

JSM Assets (object schemas, object types, and asset records) have no direct Intercom equivalent. Intercom does not have a native CMDB or asset management product. We export the Assets CSV data and deliver it as a structured inventory for the customer to integrate with a dedicated asset management tool post-migration or to store as a reference dataset outside Intercom. Asset-to-ticket linkages that existed in JSM are documented as a separate reference map.

Do we lose historical comments and conversation history?

No. We migrate the full comment history on every JSM Request as Intercom Conversation parts. Public comments become user messages; internal notes become Intercom internal notes. Author attribution, timestamps, and attachment references all transfer. The conversation timeline order is preserved by setting the Intercom part timestamp to the original Jira comment timestamp. Attachments embedded in comments are handled in the attachment migration batch.

What happens to our JSM reporting and dashboards?

JSM reports and dashboards do not migrate to Intercom. JSM reporting is built on Jira's issue data model with custom filters, SLAs, and project-level metrics. Intercom's reporting covers conversation volume, first response time, CSAT, and team performance. We deliver a written inventory of every JSM report and dashboard configuration so the customer's Intercom admin can rebuild equivalent reports in Intercom Analytics. SLA performance reports require rebuilding in Intercom's SLA tool if the destination plan includes it.

Can FlitStack AI migrate from Intercom back to Jira Service Management if needed?

Yes. Intercom to JSM is a supported migration direction. The mapping reverses: Intercom Contacts map to JSM Customers or Agents depending on role; Conversations map to JSM Requests; conversation parts map to JSM comments. The key difference is that Intercom does not have a native ITSM request type or SLA structure, so request type schemas and SLA definitions are built fresh on the JSM destination rather than migrated from Intercom.

## Related migrations

[![](https://flitstack.ai/platforms-trim/intercom.webp) Migrate to **Intercom** Every source we move into Intercom, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/helpdesk/intercom) [**Freshservice to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshservice/to/intercom) [**Kustomer to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/kustomer/to/intercom) [**Zendesk to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zendesk/to/intercom) [**Salesforce Service Cloud to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/intercom) [**Gorgias to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/gorgias/to/intercom) [**Freshdesk to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshdesk/to/intercom) [**Jira Service Management to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/jira-service-management/to/zendesk) [**Jira Service Management to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/jira-service-management/to/freshdesk)

## Sources: official documentation

1. [Import your user data into Intercom — Intercom Help](https://www.intercom.com/help/en/articles/177-import-your-user-data-into-intercom)
2. [Import your customers — Intercom Academy](https://academy.intercom.com/import-your-customers)
3. [Create and track Custom Data Attributes (CDAs) — Intercom Help](https://www.intercom.com/help/en/articles/179-create-and-track-custom-data-attributes-cdas)
4. [Events limits, troubleshooting and F.A.Q — Intercom Help](https://www.intercom.com/help/en/articles/5245634-event-limits-troubleshooting-and-f-a-q)
5. [Historical data migration to Intercom — Intercom Help](https://www.intercom.com/help/en/articles/9396032-historical-data-migration-to-intercom)
6. [Data hosting and residency — Intercom Help](https://www.intercom.com/help/en/articles/data-hosting)
7. [Setting up a Custom Object — Intercom Help](https://www.intercom.com/help/en/articles/6298280-setting-up-a-custom-object)

Get a quote

## Moving from Jira Service Management to Intercom?

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

[Get a quote](https://flitstack.ai/contact)
