Why Migrate From Jira?
Starting February 2, 2021, Atlassian will stop selling new server licenses for many of their products, including Jira Software. At the same time, they will increase the price for the remaining on-premise alternative, Jira Data Center, for which the smallest order will correspond to ordering 500 users.
While Atlassian is investing in its cloud services to provide feature upgrades, that doesn’t mean everyone can - or wants to - move to the cloud.
Many customers in high assurance industries or running projects on secure networks are unable to ever use a cloud-based solution for regulatory, security or compliance reasons.
In addition, Jira Cloud has known issues of poor performance, inflexible data localization options and increasing instability and unreliability due to the need to have many plugins installed to achieve basic functionality. In addition, the cost grows exponentially as you add users and plugins since all plugins have to be licensed at the same license tier, regardless of how many users actually use each plugin.
To learn about the other reasons why people are looking to switch from Jira to Spira, take a look at our whitepaper - SpiraTeam, the Seamless Alternative to Jira
New Simplified Migration Process
To make things easier, we have just released a new migration tool that will migrate entire projects from Jira to Spira. This new migration tool will work with:
- Jira Cloud, Server and Data Center
- Spira Cloud and On-Premise
The migration tool consists of an easy to use wizard that allows you to connect to your Jira instance:
and then connect to your Spira instance:
The migration tool lets you map the different Jira issue types to the appropriate Spira artifact type:
Currently, the following artifact types in Spira can be mapped to Jira issues: - Requirements (used for user stories, features, epics, etc.) - Tasks (used for tasks and sub-tasks) - Incidents (used for all other issue types such as bugs, defects, issues).
The migration wizard will automatically create a new project in Spira to hold all the artifacts with the same name as that used in Jira.
What is Imported?
The migration tool will import the following artifacts:
- Product Definition together with components, priorities, types and statuses
- Custom Properties and Custom Lists
- Users (but not their roles and permissions)
- Incidents, together with their associated lists of priorities and statuses
- Any attachments associated with the requirements, tasks and incidents
Any of the Jira issue types that are mapped to requirements in SpiraTeam:
Will be imported into SpiraTeam as types of requirement:
Any of the Jira issue types that are mapped to tasks in SpiraTeam:
Will be imported into SpiraTeam as types of task:
Any of the Jira issue types that are mapped to incidents in SpiraTeam:
Will be imported into SpiraTeam as types of incident:
Where Can I Learn More?
To learn more about the new Jira Importer and why you should consider migrating to Spira: