This guide has been written to assist customers upgrading from MigrationStudio to ManagementStudio. This process should be undertaken by a ManagementStudio consultant who will work with the customer to deliver the upgrade.


This process assumes that the data in MigrationStudio should be migrated to ManagementStudio.


A spreadsheet showing the roles and responsibilities for the upgrade is available on request.


Prerequisites

  • MigrationStudio upgraded to the latest version (the consultant will provide a download link and walk through this upgrade)
  • Retrieve the logs from the MigrationStudio:
    • Logon to MigrationStudio with an Admin account
    • Open the Portal
    • Browse to Admin -> Product Updates -> Download Logs to This PC
    • Send these logs to the Dev Team for inspection
    • These logs will be used to generate the default project for ManagementStudio
  • Admin logon for MigrationStudio
  • Access to logon to the MigrationStudio IIS server and the SQL Server
  • Access to SQL Server Management Studio (SSMS) with a login which has access to the MigrationStudio database
  • If the ManagementStudio IIS site will be created on a new server, access to the MigrationStudio attachments folder (via a share) will be required from the new server
  • A minimum of 300GB of disk space on the SQL server which will host the ManagementStudio database transaction logs
  • The standard prerequisites for installing ManagementStudio (details here)
  • If both the MigrationStudio and ManagementStudio IIS websites will run on the same web server, consider the following:
    • To ensure both MigrationStudio and ManagementStudio are accessible once the upgrade is complete each website will need to either run on a different port (not recommended in corporate environments) or a new DNS entry will be required for ManagementStudio if the same port is to be used (preferred option)
    • It may make sense to create a DNS entry which includes "managementstudio" as part of the name. i.e. managementstudio.domain.local
    • The DNS entry should point to the IP address of the IIS server

Upgrade Steps

If a change request is required for the upgrade, consider using the steps below in the request.

  • Install ManagementStudio as per the install guide. High-level steps:
    • Install ASP.NET Core Windows Server hosting
    • Create the SQL Database
    • Setup IIS (Already installed)
    • Configure IIS for new service
    • Install ManagementStudio Website and associated Config Files. Ensure a new project has been created with "No Config" in ManagementStudio
    • Create a ManagementStudio folder to store uploads and logs files
  • Import the custom project as supplied by the Dev Team
    • Logon to ManagementStudio with an Admin account
    • Administration -> Global Settings -> Uncheck Email Enabled -> Save
    • Administration -> Project Settings -> Import Project Settings File -> Point at file provided by the Dev Team
    • Restart the client when prompted
    • Administration -> Project Settings -> Save Changes (This ensures blank fields are populated)
  • Export the MigrationStudio Data
    • Logon to MigrationStudio with the Admin account (not an account with Admin rights, but the actual Admin account)
    • Open the Portal -> Plugins -> v7 to v10 Data Migration
    • Generate Data CSVs ZIP -> Select Real -> Run
    • This will take a while and the page may time-out
    • This file should be available for download. Copy this file to the ManagementStudio IIS web server
    • Alternatively this ZIP file will be generated in <ManagementStudio Files>\API\v7_Data_Migration\
  • Import the MigrationStudio Data
    • Download the import script Migrate Data to v10.ps1 from the MigrationStudio Product Updates webpage
    • Create a new folder on the ManagementStudio IIS web server called Import Data
    • Extract the ZIP file to a subfolder within this folder
    • Configure the Migrate Data to v10.ps1file:
Setting and Example ValueDescription
$apiUrl = http://managementstudio.domain.localThe ManagementStudio URL

$apiUserName = "ManagementStudio"

This is the built-in admin account and must be used

$apiPassword = "123456789"

Password for the built-in admin account

$projectId = 2

In ManagementStudio open the target project, then get the Project Id from Administration -> Project Settings

$managementStudioApi = "C:\inetpub\MS22\wwwroot\Automation\ManagementStudioApi"

The path to the API files on the IIS server

$v7DataFolder = "D:\Temp\Migrationv7-MS2022\Real"

The path where the MigrationStudio data was decompressed into

$v7AttachmentsFolder = "D:\\AppTracker\\Attachments"

Path to the ManagementStudio files as setup during the installation. This can be checked in appsettings.json 
  • Save the file
  • Run this script. The data will be imported into ManagementStudio. This may take up to two hours
  • Validate that the data is present
  • Configure internal services - SMTP email, logos etc…
  • Once full confidence in the system has been achieved, Administration -> Global Settings -> Check Email Enabled -> Save
  • Setup new users accounts as required
  • Optional: Change the MigrationStudio user accounts to Read Only for all the modules