Upgrading MigrationStudio to ManagementStudio

Modified on Tue, 01 Mar 2022 at 03:51 PM



This guide has been written to assist customers in 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.


  • MigrationStudio upgraded to the latest version (the consultant will provide a download link and walk through this upgrade)
  • The MigrationStudio IIS server must be running PowerShell 5.x or later
  • 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 that 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 that 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
    • A new SSL certificate is required for HTTPS installations (see HTTPS Installs in v7 and MS22 Side-by-Side Installation)

MigrationStudio Export

Ensure this part is undertaken a few days before the migration to ManagementStudio to allow the dev team to process the log files.

  • 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

Export the MigrationStudio Data:

  • Logon to MigrationStudio with the Admin account
    • Note: This must be the account named 'Admin', not other accounts with the role 'Admin'
  • If any connectors are running, stop them
  • Open the Portal -> Plugins -> v7 to v10 Data Migration
  • Generate Data CSVs ZIP -> Select Real -> Run
  • This will take around 5 - 10 mins for a 10k user database. 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 <MigrationStudio Uploads Folder>\API\v7_Data_Migration\

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 a "Project 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 -> <Each Module> -> Process Workflow -> Set the Readiness Status for each Process and Sub-process -> Save Changes
    • Administration -> Project Settings -> Save Changes (This ensures blank fields are populated)

  • Import the MigrationStudio Data
    • Update License
      • The migration will fail if there are not enough licenses to hold the incoming Apps, Users, Devices.
    • Download the import script Migrate Data to v10.ps1 from the MigrationStudio Product Updates webpage
    • Extract this into a folder
    • RDP to the ManagementStudio IIS web server
    • Create a new folder on the ManagementStudio IIS webserver called Import Data
    • Configure the Migrate Data to v10.ps1 file:
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 = 1

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.
Note: Single \ 

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

Path to the MigrationStudio files as setup during the installation. This can be checked in Admin->Initial Setup->Upload Folder
Note: Double \\
  • 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…
  • Configure Connectors - verify the Connector schedules in Administration -> Scheduled TaskManager. For example: 
  • Once full confidence in the system has been achieved, Administration -> Global Settings -> Check Email Enabled -> Save
  • Setup new users account as required
  • Optional: Change the MigrationStudio user accounts to Read Only for all the modules


Further Support

If you require further support, please visit ManagementStudio's Service Desk to search the knowledge base or create a new support ticket.