Version One to Jira Migration

[Media One]

Hi,

We are looking at migrating from VersionOne to JIRA. Could you please help with importing data from VersionOne to JIRA.?

If using .csv is the only proven way, do you have documentation on how to export all the details to .csv file from VersionOne (story details like tasks, attachments, conversations) etc.

[Jack Brickey]

TBH, I have never seen any discussion of migrating from V1. I suspect CSV is the only way. I  have done a number of imports from CSV and they vary from pretty straightforward to quite tedious and painful. I am in the process of migrating a project/team from Freshdesk and it falls into the later. Here are some thoughts that hopefully help...

• The simpler you can make the import the better. Only pull over what you truly need. Consider forgoing attachments, and any unnecessary fields
• Take the opportunity to refactor the project and make it cleaner than it was in V1 if possible. 
• For the CSV file, pay attention to all date fields and make them consistent throughout. The importer uses simpledateformat, e.g. M/dd/yy hh:mm = 11/16/20 15:55
• Users - if the users already exist in the Jira instance convert all user fields (assignee, reporter, etc) to the email addresses
• Concatenation may be needed if you are combining multiple fields from V1 into Jira
• Be sure to create a custom field to capture the V1 ticket number in Jira. This will allow users to access the original ticket in V1 if anything is missing.
• If there are any Cascading fields it should take the following form - PrimaryField -> SecondaryField. The "->" is used by the importer to translate this. 
• Be sure to set the Resolution field for all "Closed/Done" V1 issues. This may require you to add a column into the CSV file.
• Plan to run thru several "test imports" until you get it just right. Use 3-5 issues for these test imports and inspect the results w/in Jira once complete. Once you are happy w/ the results be sure to save the configuration file for the import AND don't change anything w/ your CSV file.
• Ultimately, you will likely want/need to perform some cleanup post import. You can do this by performing an advanced search for issues and then use Bulk edit function.

You might wish to peruse this list of articles - Support Articles on CSV Importing  

[Deleted user]

Hi,

We can help you to migrate from CSV.

You can try our tool here https://app.help-desk-migration.com/,

but you would need to check with Version One on How to get the CSV.

[Artem Fomin - DevOps Action]

V1 migrations are somewhat tricky. Some fields are challenging to get through CSV, and you can't transfer attachment data this way, so you'd want to leverage REST API as well.

How easy the export is going to be depends on the plan you are on (e.g. if you have Ultimate edition, pulling CSV data is going to be much easier through Analytics). In order to pull the attachments, you need to look into V1 REST API.

Then, there is Atlassian documentation on CSV-driven import of comments and attachments (e.g. format of comments, file structure of attachments, etc).

Or, you can outsource this to migration experts who have done this before. We'd be able to complete this work faster and cleaner than you would on your own.