This document is intended for use by internal staff only.



When existing MigrationStudio customers are preparing for a move to ManagementStudio it's important that both products are run "side-by-side" for a period to allow the upgrade to be planned, data collected, and the upgrade executed without any interruption in service.

This article describes a suggested approach to achieving a side-by-side installation with both websites running on the same IP port. Note that an alternative solution is to use a different IP port for each website; however, for most corporate environments, running websites on non-standard ports (i.e. ports other than 80 or 443) will not be possible due to firewall policies.

Solution Overview


  • MigrationStudio setup:
    • v7 (latest) installed 
    • Hosted on IIS Default Web Site 
    • Running on one of the standard ports (80 or 443)
  • ManagementStudio setup:
    • Installed on the same IIS server as MigrationStudio
    • Hosted on separate IIS web site

Side-by-Side Installation

The main challenge with running both products in


During the version upgrades we will be probably be required to install ManagementStudio alongside MigrationStudio. DC   has completed this with Richards help on his server. Here are the findings.


V10 will need DNS entry in the target environment. In my LAB the domain was msl.local so a  new DNS entry was created


ManagementStudio.msl.local     point to the IIS Server IP Address


On IIS in the default website should be bound to the server name or address already in use by V7. My existing URL was 

http://MSAD/migrationstudio   so a binding is required for the server name on port 80 as I do not use SSL.




The binding for V10 needs to be on port 80 but this time referencing the new DNS entry.



Finally the JSON file must be changed to the correct hostname.  On my server the file is located in    C:\inetpub\MigrationStudioV10


You may also require local host entry like this. managementstudio.msl.local