Meet the help desk that knows your IT from day one.

AssetSonar Blog Migrate Jira Issues Assetsonar Itsm

[ITSM | How-to] Migrating Jira Issues into AssetSonar

AssetSonar ITSM Jira migration field mapping modal showing Jira issue fields mapped to AssetSonar ticket fields.

Why It Matters

Jira issues often contain useful operational history, ownership details, priorities, and project-specific fields that teams need after moving service work into AssetSonar ITSM. The Jira migration flow lets you select the projects you want to bring over, map Jira issue fields to AssetSonar ticket fields, and import the data into your ITSM workspace without manually rebuilding each ticket.

Prerequisite

Before starting your migration, ensure your Jira Integration is already configured and active. You can find full setup instructions here.

How to Set It Up

  • Enable the Feature: Navigate to Settings → Integrations → Helpdesk → Jira Integration and check the Enable Ticket Migration box at the bottom of the page.
  • Select Your Projects: Click Import Tickets to open the Migrate Jira issues to ITSM modal. Because Jira issues are scoped to specific projects, select the Jira project or projects you want to migrate data from.
  • Map Your Fields: Click Import Tickets from the migration modal to open the field mapping modal. Select which Jira fields you want to bring into AssetSonar ITSM and map them to the correct Field Name in AssetSonar.
  • Standard Jira fields with native AssetSonar equivalents are pre-mapped. Use the modal to map additional Jira issue fields or custom fields if you want to bring them across.
  • If a matching AssetSonar field does not already exist, enter a new field name in the destination column. AssetSonar creates a new custom field in the ITSM Tickets module when you save the mapping.
  • Click Done once the mapping is ready.
  • Test the Migration: After saving the field mapping, click Test Import Tickets to open the test modal. Enter a Jira issue key, or leave the field blank to test against an issue from the selected migration project. Click Test Mapping to review whether the mapped Jira fields are pulling values correctly.
  • This test also helps confirm that Jira issue fields and Atlassian Document Format content convert correctly into AssetSonar ITSM.
  • Initiate the Import: Once your test is successful, click Sync Now to run the migration. Jira issues are imported into AssetSonar ITSM based on the saved field mapping.

Note: Jira uses the term issues, while AssetSonar ITSM uses tickets. During migration, Jira issues are imported as AssetSonar ITSM tickets. Once imported, these tickets can be managed through AssetSonar’s request management workflows.

Next Steps

Review your active Jira projects, enable the migration setting, select the projects you want to migrate, map the fields you want to import, run Test Import Tickets, review the Test Mapping results, and click Sync Now once the migration is ready.

More Ways to Migrate Your Data

AssetSonar makes it easy to bring your historical helpdesk data into ITSM. Depending on your current setup, check out our other migration guides to find the path that works best for your team:

[ITSM | How-to] Bulk Importing Tickets into AssetSonar
[ITSM | How-to] Migrating Zendesk Tickets into AssetSonar

Was this helpful?

Thanks for your feedback!
Sr. Technical Writer, EZO
Farhad Hassan is a Senior Technical Writer at EZO with over a decade of experience turning complex software and operational workflows into clear, actionable guidance. He creates support content across asset management, equipment maintenance, rental operations, and IT management, helping users understand product capabilities, solve problems, and get greater value from their tools.

Powerful IT Asset Management Tool - at your fingertips

Empower your teams, streamline IT operations, and consolidate all your IT asset management needs through one platform.
capterra
software-advice-2026
Leader
High Performer Mid market