Project migration

This topic explains how to migrate your virtual services to Service Virtualization.

In this topic:

Migration overview

When you upgrade Service Virtualization to a new version, you must also migrate your virtual services. Migration updates your projects and services, enabling them to work with the new version.

You can migrate virtualization projects from the SV Designer or the Resource Manager migration tool.

Back to top

Migrate from the SV Designer

When you open a project whose version is 4.00 or higher in the Designer after installing a new Service Virtualization version, you are prompted to allow Service Virtualization to migrate the project.

Back to top

Migrate from the Resource Manager migration tool

After installing a new version of Service Virtualization, you can use the Resource Manager command line migration tool to migrate projects from version 4.00 and higher.

You can migrate projects and services stored in the file system or in Application Lifecycle Management (ALM). This is especially useful, for example, if you have a number of projects stored in the file system or ALM and want to migrate them without opening each one in the Designer.

The Resource Manager migration tool lets you migrate the following:

• Virtualization projects (.vproj files). The .vproj file includes information on all project entities (virtual services, service descriptions, simulation models, etc.) included in the project.
• Project archives (.vproja files). A .vproja archive file is created when you export a project from within the Service Virtualization Designer.

You can also specify a folder to migrate. If you specify a folder, all relevant project entities inside the folder are migrated. For example, you may have a folder that contains multiple archived projects.

For details on using the Resource Manager migration tool, see Migrate virtualization projects.

Back to top