Acquia Search powered by SearchStax provides quick and relevant search results.

This page provides information about how to get started with Acquia Search powered by SearchStax by using your existing Drupal search configurations and index data.

Key concepts for migration

Before you migrate from Acquia Search (Solr) to SearchStax Site Search, you must understand the shift from infrastructure-managed indexing to an application-centric model. Use the following terminology mapping to align the Drupal configuration:

• SearchStax App: In the Site Search ecosystem, an App serves as the logical equivalent of a Solr Core or Collection. It acts as the primary container for index data, relevance rules, and analytics.
• Search API Server: In Drupal, a Server represents the remote connection to the SearchStax App API. While Acquia Search typically uses internal authentication, SearchStax uses specific App Endpoints and API Keys to facilitate the connection.
• Search API Index: An Index object defines the specific subset of Drupal entities, such as Nodes, Media, and Users, to synchronize with SearchStax App.
• Multisite indexing: If a single SearchStax App is shared across multiple Drupal environments or sites, you must implement Unique Index IDs or Site Prefixes. This implementation ensures that data remains logically partitioned in the App, prevents document collision, and ensures that search results scope correctly to the requesting site.

For details and multisite guidance, refer to Acquia Search powered by SearchStax Onboarding process.

Migration checklist

Use the following checklist to migrate to Acquia Search powered by SearchStax:

Manual migration

Migrate existing Drupal indexes and views to Acquia Search powered by SearchStax manually. For more information, visit Moving Drupal Indexes and Views to Site Search Manually.

Acquia recommends that you use the manual migration guide only in the following scenarios:

• Drupal views implementation includes complex configurations.
• Site uses a complex language setup with custom language fields.
• Modules link directly to the index, such as a custom facets module.
• Site is small enough to reindex in minutes and requires a straightforward migration path.
• Issues are encountered with the migration module approach.

Next step

Prepare for the migration to Acquia Search powered by SearchStax

Migrating to Acquia Search powered by SearchStax

5

5