/
Method 1: Full Reindex Migration

Method 1: Full Reindex Migration

Overview

This migration method rebuilds your HQ 2.0 and Voyager Server 3.0 environment using configuration data from a previous version, followed by a complete re-index of all repositories.

When to Use This Method

Choose this method when you want the cleanest, most reliable migration with complete data and configuration integrity. This approach is ideal for environments that have been running for a long time, undergone major upgrades, or where index inconsistencies exist. It ensures a fully refreshed and optimized index, though it requires more time and system resources to complete.

Preparing for Migration

Step 1: Install Voyager Server 3.0

Go to the Voyager download page and run the installer for Voyager Server 3.0 into a new directory on your machine. A new voyager/server_3.0 directory will be created when the installation is complete. 

 

Step 2: Install HQ 2.0

Go to the Voyager download page and run the installer for HQ 2.0 into a new directory on your machine. A new Voyager/HQ directory will be created when the installation is complete.

 

Step 3: Copy Configurations for Voyager HQ and Server

HQ

  1. Go to your HQ 1.X home directory, copy the /config folder — and optionally the /py and /logs folder. Transfer these folders into your HQ 2.0 home directory.

  2. Make a copy of the hq VMOPTIONS File in the HQ folder within your HQ 1.X directory. Open the copied file and under the DIRECTORIES section, add the VM option similar to the one below:

-Dhome.dir=D:\voyager\hq-home-2.0

IMPORTANT: Ensure that the VM option above corresponds to the correct file path in your HQ 2.0 install directory.

  1. Then, move this hq VMOPTIONS File to the HQ installation directory.

Server

  1. Go to the Server 2.X data directory, copy the /config folder — and optionally the /logs and /meta folders. Transfer these folders into your Server 3.0 data directory.

  2. Make a copy of the Voyager VMOPTIONS File in the app folder within your Server 2.X directory. Open the copied file and under the #Directory section, add the VM option similar to the one below:

-Ddata.dir=D:\voyager\server-data-3.0

IMPORTANT: Ensure that the VM option above corresponds to the correct file path in your Voyager Server 3.0 install directory.

  1. Then, move this Voyager VMOPTIONS File to the Server-3.0 app directory. 

NOTE: The /meta folder can take a significant amount of time to copy over to the new directory. If you would like to migrate this file then it is recommended to move the file instead of copying it over.

 

Step 4: Preparing for Saved Search Migration 

Before stopping the previous versions of HQ and Server, you will need to create a Snapshot of your Saved Searches and migrate them over to your Server 3.0 install directory:

  1. For Server 2.X, open Manage UI and go to Manage -> Index -> Snapshots.

  2. Select Snapshots and then click Create Snapshot.

  3. Name the Snapshot and check the following options shown in the image below.

  1. When complete, then select Create New Snapshot. A ZIP file with your Saved Searches and Display Templates have been saved as a Snapshot. This file is located in voyager/server_X.X/data/snapshot and can be migrated from your Server 2.X to your new Server 3.0 instance.

NOTE: You will return to the remaining steps for the Saved Search migration after completing the full re-index migration process outlined in this guide.

 

Step 5: Start Server 3.0

  1. Launch Server 3.0; it will auto-upgrade the configuration files and migrate over the settings, repositories, and other configurations from Server 2.X.

  2. If needed, activate the new Server 3.0 instance using the license key that was issued to you.

 

Step 6: Start Voyager HQ 2.0

  1. Launch HQ 2.0; it will auto-upgrade the configuration files and migrate over the settings, repositories, pipelines and other configurations from HQ 1.X. 

  2. If needed, activate the new Voyager HQ 2.0 instance using the license key that was issued to you.

IMPORTANT: Ensure that HQ 1.X and Server 2.X are fully shut down before proceeding. If these services remain active when launching Server 3.0 and HQ 2.0, then the application will fail to start properly.

 

Step 7: Validate Functionality

In the new HQ 2.0 instance, confirm that the repositories, pipelines, data sources and other configurations are loaded correctly from HQ 1.X. 

 

Initial Step: Migrating Saved Searches Using Snapshots

For migrating and importing the Saved Searches from HQ 1.X and Server 2.X to HQ 2.0 and Server 3.0, you will need to use the Snapshot option in Manage UI.

NOTE: The Saved Search migration preparation should already be completed in the following section of this guide — Method 1: Full Reindex Migration | Step 4: Preparing for Saved Search Migration

 

To complete the migration of your Saved Searches, please go through the following steps:

Steps:

  1. Once the Snapshot has been created, then go to Manage UI for Server 3.0 and select Import Snapshot.

  2. Select the My Computer option and click Browse.

  1. Choose the generated snapshot file located in the following file path for the install directory for your previous version of Voyager Server and select Open: voyager/server_X.X/data/snapshot

  2. Select Import Snapshot and the importing status will appear. A pop-up message in Server 3.0 will indicate when the importing process is completed.

  3. Navigate back to the Snapshots page with the list of your snapshots and under the Actions column, select the Apply icon.

  1. Ensure the desired settingss are selected and under Select An Action, switch Merge to Replace.

 

  1. Select Apply to proceed. You will be redirected to the Snapshot Status page, where you can monitor the progress of your snapshot as it is loaded into your Voyager Server 3.0 instance. Once the process is complete, then your snapshot settings will be successfully migrated.

 

Quality check

In Navigo, preview the saved searches:

  • Click the Saved button located next to your Cart.

  • Check through the My Saved Searches to ensure they all have been properly migrated from the previous version.

  • Select a few Saved Searches from the list to verify that the correct search parameters and corresponding results are displayed as expected.

 

Step-by-Step Migration Guide:

For customers wanting to fully rebuild their HQ 2.0 index from source repositories in HQ 1.X, this method ensures that all configurations, metadata, and content are freshly indexed using the latest system architecture and runtime components. Follow the steps below to perform a complete re-index migration:

Steps:

  1. Open HQ (Admin Console)
    Sign into HQ with an admin account.

  2. Confirm license status
    In Settings → License, verify the license is valid on the new host. You can also confirm the V3 license key is applied in the license.dex file that’s located in the /server_3.0/data/config folder; dual-license is fine during transition.

  3. Verify global settings
    In System → Info, confirm base URLs, proxies, SSL/cert settings, and any directory path mappings that may differ on the new server.

  4. Validate pipelines
    Open Pipelines and check each pipeline and its configured steps by selecting Edit option. Review the migrated pipelines to identify any deprecated steps or references to old hosts/paths.

 

  1. Choose index strategy per repo

    1. Full Re-index (recommended after migration) to rebuild everything on HQ 2.0.

    2. If needed, update endpoints for the repositories and save changes.

  2. Re-index repositories
    Go to Repositories and for each migrated repo:

    • Select the ellipses icon next to the repository and select Index.

    • Continue this process for all desired repositories.

      • NOTE: Be sure to not index too many repositories at once in order to prevent indexing errors and overloading the indexing Agent(s).

  1. Monitor progress & health

    1. In HQ, go to Indexing → Metrics: watch scanning, extracting and indexing status.

    2. Go to System → Logs in HQ: download log files to check for connector authorization or mapping errors.

  2. Fix & rerun as needed
    If needed, resolve any broken connections, bad filters, or pipeline step errors. Then select Rebuild for the affected repositories in the index.

 

Quality check

In Navigo, preview the indexed content items/results:

  • Run representative queries, verify result counts.

  • Check key facets/metadata and permissions behave as expected.

  • Compare sample doc counts vs. the old environment.

 

Need Help?

If you have any questions about the migration process or regarding the HQ 2.0 and Voyager Server 3.0 release, please contact us at support@voyagersearch.com.