Web Server Migration


This migration scenario is for Issuetrak 11.0 and above only.  It assumes that you're migrating from an old Web server to a new Web server with the latest version of Issuetrak.  This also assumes that there is only one instance of Issuetrak running on the current Web server.  If your Web server hosts multiple Issuetrak instances, please reach out to Issuetrak Support so that we can collaborate with you on your server migration. This article assumes familiarity with our deployment tools.

Additionally, if you are attempting to migrate a version of Issuetrak older than 11.0, please reach out to Issuetrak Support for assistance. 



  1. Confirm that the site is working properly in its current environment (IEM, OEM, Identity Management / SSO, as applicable).  
  2. Be sure that the new Web server meets all of the system requirements, including the installation of software and features.
  3. Make sure you know your site ID. You can get this from Issuetrak Support.
  4. Download the latest version of Issuetrak from here to your current Web server.  
  5. Use the IDM to generate a JSON of the existing Issuetrak instance.  This will provide a snapshot of the instance's current deployment configuration.
  6. Stop the website in IIS.  
  7. Disable all Issuetrak Scheduled Tasks and Services.
  8. Copy the JSON generated in step 5 to the new Web server.
  9. Take a backup of the following folders in your Issuetrak web folder:
    1. Archives
    2. Dynamic Files
    3. Attachments
    4. Graphics
    5. KBAttachments
    6. Reports
    7. Survey



  1. Download the latest version of Issuetrak from here to your new Web server.  
  2. On the new Web server, open the JSON in a text editor.  Notepad++ is recommended for this, as Windows Notepad tends to malform the displayed file contents.  
    1. Make the necessary changes to the JSON to reflect the new hosting environment:  Web server info, file locations/paths, etc.  
    2. Save the file when this is complete and you've validated the information you entered.
  3. Use the IDM to deploy the JSON you just saved.
  4. Confirm that the site comes up as normal.

If the new server uses the same hostname as the old web server, then it may be necessary to update your environment's DNS to point to the new web server.

  1. Confirm that you can sign into the site.
  2. Navigate to System Settings and update the Application URL (if applicable).
  3. Navigate to the site's Web folder, then overwrite the Attachments, KBAttachments, Graphics, Reports, Surveys, and Archives folders with the backups you took from the old site.  
  4. Confirm that the features of your site are working properly (IEM, OEM, AD integration, and SSO, as applicable).

It may be necessary to create firewall exceptions for the new web server in order for these features to work.

  1. Make sure that the appropriate permissions are set for the Attachments folder location, and set size limits appropriate for your site.  See KB 1578 and KB 1696, respectively, for more information.
  2. If SSL is used (as Issuetrak recommends), make sure to import the appropriate SSL certificate from the old Web server and configure IIS to use its thumbprint for the site's SSL binding.  
  3. If you used the Issuetrak API with the old Web server, test the accessibility of the API with the new Web server.  

Issuetrak Support will be happy to troubleshoot or assist you. You can contact Support at 888-789-8725 (US & Canada), +1 757-213-1351 (International), support@issuetrak.com or https://support.issuetrak.com/.