As of SOAtest and Virtualize 2026.2, the Parasoft Embedded Data Repository server has been removed, and the standalone Parasoft Data Repository Server is no longer supported. Any embedded and standalone servers from previous versions of the application must be migrated to a MongoDB installation to continue using them. The migration process can be automated with a utility available on the Parasoft Marketplace.
If you are looking to move a data repository from one MongoDB server to another, see Copying and Pasting Repository Data.
When migrating from an old, embedded data repository server, you can use a utility to automatically copy data from an existing workspace into a MongoDB Server. The new MongoDB Server must be up and running and the old installation must have been removed or at least not running.
./run_embedded_migration.sh --data-dir <path-to-workspace> \ --destination-uri mongodb://<destination-host>:<destination-port> \ --destination-username admin |
run_embedded_migration.bat /data-dir:"<path-to-workspace>" ^ /destination-uri:"mongodb://<destination-host>:<destination-port>" ^ /destination-username:admin |
When migrating from a remote Parasoft Data Repository Server, make sure both it and the new destination MongoDB Server are running. Note: To make it easier to connect existing assets to the new MongoDB Server, consider deploying it on the existing host, port, and credentials that assets are already using.
./run_embedded_migration.sh \ --source-uri mongodb://<source-host>:<source-port> \ --source-username admin \ --destination-uri mongodb://<destination-host>:<destination-port> \ --destination-username admin |
run_embedded_migration.bat ^ /source-uri:"mongodb://<source-host>:<source-port>" ^ /source-username:admin ^ /destination-uri:"mongodb://<destination-host>:<destination-port>" ^ /destination-username:admin |