Skip to content

Migrate vScope

Migrating your vScope installation can be done in two ways. Both methods preserve all configurations, including history, Discovery scope, user accounts, presets, Tracker profile settings, and more.

The installer sets the reference path to vScope’s data, saved in the vScopeData folder. If you need to move this folder, rerun the installer to set the new data location. Here’s how to handle common migration cases.


Move to a Different Volume or Location on the Same Server

  1. Stop the vScope service.

  2. Run the vScope installer and specify the new location for the vScopeData folder (e.g., D:\vScopeData). Complete the installation.

  3. Stop the vScope service again (as it will restart automatically after installation).

  4. Delete the newly created vScopeData folder in the new location.

  5. Move the original vScopeData folder to the new location.

  6. Start the vScope service.


Move to a Different Server

When moving vScope to a different server, you can choose between migrating the entire installation, including history and data, or only the settings, users, and Discovery scope.

Option 1: Migrate Everything

This includes inventory data, tags, history, settings, users, and Discovery.

  1. Stop the vScope service.

  2. Copy the vScopeData folder (e.g., C:\vScopeData or D:\vScopeData) to the same location on the new server.

  3. Download the latest vScope installer and run it on the new server. When prompted, select the vScopeData folder’s location.

  4. Log in to the License & Billing Account and activate a valid license.

    If no license is available, contact support for a new license.

  5. Verify that all targets and credentials are accessible from the new server.


Option 2: Migrate Content, Users, and Settings Only

  1. Stop the vScope service.

  2. Copy the vScopeData folder, excluding C:\vScopeData\projects\default\modeldb, to the correct location (e.g., D:\vScopeData) on the new server.

  3. Start the vScope service.

  4. Log in to the License & Billing Account and activate a valid license.

    If no license is available, Contact Support for assistance.

  5. Verify that all targets and credentials are accessible from the new location.


Location of various content:

Locate and copy the relevant files to the same path in the new installation.

  • User Accounts
    C:\vScopeData\global\usermanager

  • Content (eg. Dashboards & Tables) C:\vScopeData\global

  • IT Service Layouts, Sections and Fields
    C:\vScopeData\global\serviceMapper\specs

  • User-Created Rule-Based Tags
    C:\vScopeData\projects\default\global\tags\rulebased