Migrate RMsis data to a different JIRA + RMsis Instance

Owned by Sanjay Sahani
Last updated: Feb 14, 2023 by Pritam Kumar
2 min read

Question : How can I migrate RMsis data from one instance (test instance) to a different RMsis + JIRA Instance (Production Instance)?

Answer : 

  • If you want to migrate RMsis data from one RMsis + JIRA instance to a different instance, you have the following options :

    • If you can take a backup of your JIRA database (test instance) and restore the same database to your production instance, you can follow the steps mentioned below to move your RMsis data to new server:

      • Take a backup of your JIRA database and restore it on the new instance.

      • Take a backup of your RMsis database (test instance).

      • Install RMsis on the production instance.

      • Restore RMsis database on the production instance.

      • You may need to regenerate the license key for RMsis if your system code changes 

      • RMsis system code depends on the RMsis Base URL / RMsis Host Name / Reverse Proxy Host Name + the Port Number on which it is configured.

      • Please let us know if this is required. We will enable license key regeneration for your RMsis License.

    • If you can not restore the JIRA database of the test instance to your Production instance JIRA, then you can use the CSV Export-Import functionality in RMsis to move your data to a new server.

    • Please follow the steps mentioned below to move your RMsis data from the test instance to the production instance in this case :

      • Export RMsis data in CSV files.

      • Create a new database for RMsis.

      • Install RMsis on the production instance and use the new database.

      • Use the CSV import process to import the data.

      • This method can be used for Planned Requirements, Unplanned Requirements, Test Cases, Test Runs, Traceability information,Test Case Relationships. 

        • Details about data import and export are available at https://optimizory.atlassian.net/l/cp/ErFBn613

        • Please note that this feature still has limited capability and details not mentioned above will not be imported. It will have to be updated manually.

          • Data corresponding to the following fields in Planned (or Unplanned) requirements will not be imported: External Sources, Internal Sources, Baselines, and Comments.

          • If you have baselined or committed a requirement then this information will not be imported and the requirement in the new project will be treated as a newly created requirement (non-baselined / non-committed).

          • If you have created multiple versions of a requirement, then this information will not be imported and different versions of a requirement will be imported as separate requirements.