HQ 2.0 and Voyager Server 3.0 Migration Guide
Introduction
This migration guide is designed to help system administrators and IT engineers transition from earlier versions of HQ and Voyager Server to the latest HQ 2.0 and Voyager Server 3.0 release.
Why Move to the New Release
Upgrading to HQ 2.0 and Voyager Server 3.0 provides organizations with a faster, more secure, and future-ready platform for enterprise data discovery. Migrating ensures improved performance, enhanced security, long-term product support and access to the latest bug fixes and feature enhancements.
What Makes This Upgrade Different
This release represents a major step forward in Voyager’s platform modernization. The entire system has been upgraded with faster, more secure, and more reliable core components — spanning the search foundation, key libraries, and runtime frameworks. Because these are significant upgrades, the migration pathway includes a few additional preparation steps to ensure a smooth transition. Our team has documented the process clearly and provided guidance to make upgrading straightforward and low-risk — so you can benefit from Voyager’s modernized foundation with confidence.
Migration Methods
Customers have 3 migration methods available. Each varies in complexity, speed, and suitability depending on your system’s size, configuration, and stability.
Migration Method | Pros | Cons | Best For | Estimated Effort |
|---|---|---|---|---|
1: Re-Index in HQ 2.0 Fully rebuilds the index from source repositories. | ✅ Safest, cleanest approach ✅ Ensures content and configurations are up-to-date | ❌ Time-intensive ❌ Heavy performance load | Environments running a small to medium size index with content that is not up-to-date | High |
2: Solr-to-Solr Migration Transfers existing indexed data directly between Solr instances. | ✅ Faster than re-indexing ✅ Preserves indexed data | ❌ Requires more upfront migration preparation and configuration | Environments running a medium to large index with content that is up-to-date | Medium |
3: Using Snapshots Exports/imports existing index snapshots. | ✅ Fast and simple ✅ Minimal downtime | ❌ Requires validation | Environments running a small to medium size index | Low |
Once you’ve selected a migration method, use the appropriate guide below to get started:
Method 1: Full Reindex Migration
Method 2: Solr-to-Solr Migration
Method 3: Snapshot Migration
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.