nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Attachment Migration from Non Jira system

Nico Ocampo

Hi Community,

We are migrating a legacy system to JIRA and one of the key ask is the attachment, I am planning to migrate the legacy system's old ticket with their attachment in JIRA Service Management Cloud. Do we have a step here on how to do that?

Thank you in advance.

Accepted answers

Dave Mathijs

Hi @Nico Ocampo welcome to the Atlassian Community!

Have a look at the following documentation article: Import data from a CSV file

Importing attachments

You can attach files to issues created from your CSV file. To do this, specify the URL of your attachment in an Attachments column within your CSV file.

All comments

Dave Mathijs

Hi @Nico Ocampo welcome to the Atlassian Community!

Have a look at the following documentation article: Import data from a CSV file

Importing attachments

You can attach files to issues created from your CSV file. To do this, specify the URL of your attachment in an Attachments column within your CSV file.

Nico Ocampo

Thank you Dave for welcoming me here and providing the link.

Brad Peterson

Hi @Nico Ocampo

There are third-party migration tools available that can help in the migration of the tickets of the legacy system to Jira Service Management Cloud (JSM), along with attachments.

First, you need to define the must-haves you expect from migration and then evaluate the different migrators available in the market. Migration projects are typically complex and require careful planning and strategy. Also, it is not straightforward when it comes to choosing a migration solution.

You can consider the following criteria while evaluating a third-party Migration tool:

Support of legacy tool: As part of the evaluation, check whether the legacy tool is supported by the tool or if the solution supports a way to add custom integration.
Non-disruptive Migration: Migration can cause massive disruptions to operations by not letting users use JSM while the migration is going on. Often the cost of disruption dominates all other explicit and hidden costs. Assess the level of disruption that may be caused by the tool to all aspects of current operations. 
Preservation of Institutional Knowledge: Understand whether the tool preserves historical knowledge of the ticket data.

OpsHub Migration Manager is an Atlassian partner with extensive experience in undertaking complex migration projects ensuring zero downtime, no data loss, data integrity, and full ownership of the migration process, which can be a good choice for the given job. It maintains the relations between tickets related, during the migration. Please browse through Tools Supported by OpsHub, to check the support of the legacy tool. On top of this, OpsHub provides a way to add custom integration for the legacy tool.

Please reach out to OpsHub’s Migration Experts, for an initial free consultation on migration steps. 

Thanks

Brad

Diana_Architect_ZigiWave

@Nico Ocampo hi! Hope you've resolved your case by now! Just to add to Brad's comment - you can check out the marketplace for tools that can help you with the migration (if you're open to using such). Plenty of options to choose from. I'd propose looking at ZigiOps. Along with integrations, ZigiOps can be used as a migration solution.

Regards, Diana (ZigiWave)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management