Page Comparison

...

1. Open the folder where the utility files were extracted.

2. (Optional) Open a command prompt at that location.

3. Execute the utility by running the program: vera.jira.cloud.migration.utility.exe

   1. Note: the utility supports two arguments: skip_export and skip_import

      1. Running the utility with the skip_export argument (e.g. vera.jira.cloud.migration.utility.exe skip_export) will cause the utility to not attempt to export project fields from Jira Server.

         1. Code Block
            language bash
            vera.jira.cloud.migration.utility.exe skip_export

      2. Running the utility with the skip_import argument (e.g. vera.jira.cloud.migration.utility.exe skip_import) will cause the utility to not attempt to import project fields to Jira Cloud.

         1. Code Block
            language bash
            vera.jira.cloud.migration.utility.exe skip_import

The utility is interactive and may present questions to the user. For example, a user may choose not to store their Jira Server password in the config.json file. When the utility is executed, it will ask for the password:

...

The utility will ask for the following information if it is missing or incorrect:

• Jira Server URL

• Jira Server Username

• Jira Server Password

• Project Keys to Export

• Jira Cloud URL

• Jira Cloud Username

• Jira Cloud API Key

The utility may also ask if the user wants to overwrite previously exported projects. This only happens when there are previously export files in the Exports directory and the “overwrite_previous_exports” property is set to ask or missing.

After executing the utility, congratulations! Your projects have been migrated! See the next step for more information: 3. Review Logs and Exports