Articles Tagged 'migration'

This articles describes the steps to migrate an existing Git repository to remote (either self-hosted or hosted by a cloud provider like GitHub).

We have had lots of customers recently migrate their data from other systems to Spira using our migration tools. One question that often comes up, is  - how to handle the import of users that will ultimately be connecting to Spira with Single Sign On (SSO). This article provides some general guidance.

We have had some questions asked about the TestRail migration tool. This KB provides some additional information about what is migrated and how the artifacts relate between SpiraTest and TestRail.

This article explains how to properly move from the Spira Jira Server dataSync to the Jira Cloud dataSync without disrupting the previously synchronized data, ensuring the data synchronization continues to function as expected.

This article explains the process for making a backup image of your "on-premise" SpiraTeam (or SpiraTest, SpiraPlan) instance and preparing it so that it can be sent to Inflectra to host on our cloud environment. This can happen when you have been using SpiraTeam on-premise, but now want to migrate to the cloud.

This article explains the process for taking a SpiraTeam (or SpiraTest, SpiraPlan) backup image from Inflectra's cloud servers and installing it on a local "on-premise" instance of SpiraTeam. This can happen when you have been using SpiraTeam in the cloud, but now want to host it locally.

This article describes the process and steps for moving your SpiraTest, SpiraPlan or SpiraTeam database from one computer to another.
The article will refer to SpiraTeam, but it applies equally to the other products.

We have a migration tool that makes it easy to move from Jira (cloud, server and data-center editions) to Spira (SpiraTest, SpiraTeam and SpiraPlan editions). This article provides some more information on exactly what is migrated in each module.

When you want to migrate your requirements, test cases, defects and other data from HP/Micro Focus ALM to SpiraTeam, you will need to make sure you have all of the ALM client components installed. However the ALM Components are normally loaded using the insecure Internet Explorer 11 (IE11) web browser. To avoid needing to use this browser, you can use the Micro Focus ALM Client Launcher instead. This article explains how.

When you are running the import from HP / MicroFocus ALM into Spira, you sometimes come across error messages that look like the following:

Error "The field <RQ_USER_17> cannot be used with requirement type <Non Functional>"

When you want to migrate your requirements, test cases, defects and other data from HP ALM to SpiraTeam, you will need to make sure you have all of the HP ALM client components installed.

Sometimes it is necessary to move a SpiraTeam, SpiraTest, SpiraPlan, or KronoDesk installation to another server, without wanting to lose all of your data. This KB will guide you through the steps of transferring the install over, and optionally upgrading the application. This guide will walk you through the recommended steps when needing to move both the application and database to new servers.

Sometimes customers want to download their list of tickets and file attachments. This article explains how to read the data that we provide.

You can use the Spira Project Backup & Migration Tool to move projects between one instance of SpiraTest and another pretty easily. However there is a known issue that can sometimes occur if you have deleted custom properties.

This post shows you how you can migrate or downgrade a SQL Server database from one version to a lower or earlier one. E.g. 2016 to 2014, 2014 to 2012, 2012 to 2008 etc. This can be useful if you maintain a heterogeneous environment of SQL Server instances and you have a backup from a newer version that needs to be hosted onto an older version. This happens to us quite a bit when customers installed a trial on SQL Server Express (latest version) and we need to host it on one our cloud servers.