Jira Servicenow Integration , Bulk Import

mdshahvez11
Tera Contributor

‎06-10-2025 03:16 AM

Hello everyone,

I'm currently working on a bulk migration from Jira to ServiceNow.

While I'm able to fetch the data successfully, I'm encountering an issue with the comments.

For each Jira issue, I’ve created a separate subflow where I pass the Issue ID and fetch all related comments. This part works — I'm able to retrieve all comments from Jira.

However, when I try to update them into a string field in the staging table, only one comment (out of 4–5) gets stored.

I’ve attached screenshots of the subflow and execution logs for reference.

Any insights on why only one comment is being saved and how I can store all comments properly would be appreciated.



mdshahvez11_0-1749550362843.pngmdshahvez11_1-1749550366713.png

 

0 Helpfuls
  • 594 Views
10 REPLIES 10

Vishal36
Mega Guru

‎06-12-2025 06:37 PM

Hi @mdshahvez11, 

If you’re running into issues migrating Jira comments into ServiceNow—like only one comment showing up, or broken threads—you’re not alone. Jira and ServiceNow handle comments, relationships, and metadata very differently. Here are a few things worth considering:

  • Data structure mismatch: Jira comments are often threaded and stored differently than how ServiceNow expects them. You may need logic to reformat them.
  • Handling relationships: Linked issues, parent-child tasks, and attachments need to be migrated with references intact, or you’ll lose context.
  • Bulk logic limitations: When using sub flows, only the last iteration may persist if you’re overwriting a single field. You’ll need to aggregate all the comments into one field or write a loop that adds new comments instead of replacing old ones.
  • Error handling and retries: What happens if a record fails mid-migration? Do you retry from the beginning or just for that one? These edge cases matter at scale.

If you're open to another less technical and automated approach, you may consider, an enterprise –grade migration tool and ServiceNow partner, OpsHub Migration Manager (OMM) that can help you with:

  • Phased migrations with zero downtime and non-disruption
  • Full fidelity migration: Sync not just field values, but comments, history, and relationships between records.
  • No manual scripting: You don’t have to write sub flows or custom scripts for every field, comment, or attachment. OpsHub handles the whole migration—end to end—without a single line of code.

 

Hope it helps!

0 Helpfuls