If your Search Index uses Solr Autocomplete, delete it at /admin/config/search/search-api/index/name_of_index/autocomplete
In the administration menu of your application, click Configuration.
In the Search and metadata section, click Migrate from Solr to SearchStax.
Click Migrate.
Use your SearchStax Site Search Account credentials to log in. If you enabled two-factor authentication, use the corresponding token. After you log in, the system displays a list of all apps present on your Site Search account.
Skip this step if you see your apps in the list.
If you do not see the desired app in the drop down, create an app by following the steps outlined in Creating a Search App. After you create the app, navigate back to Configuration > Search and Metadata > Migrate from Solr to SearchStax.
Click Migrate, and toggle the refresh button under the SearchStax app to migrate if you do not see the app in the list.
Select the app you want to connect to from the list.
Select Search view and display, and choose the desired view to fetch the settings from.
Click Migrate server now.
After successful migration, the system displays several success status messages that indicate the artifacts that are migrated.
Warnings during migration
When migrating from Drupal Search to Acquia Search powered by SearchStax, you may see the following warning in your Drupal logs or Search API status page:
language-specific field types missing in schema of index Index on server SearchStax
Note
This warning is expected and safe to ignore. It does not indicate a migration failure or indexing problem. SearchStax falls back to default text field processing, and your content is still indexed and fully searchable.
This warning appears when a language configured on your Drupal site does not have dedicated language-specific field types (such as language dictionaries or analyzers) provisioned in the SearchStax application schema.
If you want to resolve the warning and enable language-specific search features (such as stemming, stop words, or synonyms for your language), you can configure this in the SearchStax dashboard:
Navigate to App Settings > Languages in SearchStax and add the required language.
Optionally, configure Search Profiles with Data Filters to customise search behaviour per language.
Migrating the server from Drupal to Acquia Search powered by SearchStax
If your Search Index uses Solr Autocomplete, delete it at /admin/config/search/search-api/index/name_of_index/autocomplete
In the administration menu of your application, click Configuration.
In the Search and metadata section, click Migrate from Solr to SearchStax.
Click Migrate.
Use your SearchStax Site Search Account credentials to log in. If you enabled two-factor authentication, use the corresponding token. After you log in, the system displays a list of all apps present on your Site Search account.
Skip this step if you see your apps in the list.
If you do not see the desired app in the drop down, create an app by following the steps outlined in Creating a Search App. After you create the app, navigate back to Configuration > Search and Metadata > Migrate from Solr to SearchStax.
Click Migrate, and toggle the refresh button under the SearchStax app to migrate if you do not see the app in the list.
Select the app you want to connect to from the list.
Select Search view and display, and choose the desired view to fetch the settings from.
Click Migrate server now.
After successful migration, the system displays several success status messages that indicate the artifacts that are migrated.
Warnings during migration
When migrating from Drupal Search to Acquia Search powered by SearchStax, you may see the following warning in your Drupal logs or Search API status page:
language-specific field types missing in schema of index Index on server SearchStax
Note
This warning is expected and safe to ignore. It does not indicate a migration failure or indexing problem. SearchStax falls back to default text field processing, and your content is still indexed and fully searchable.
This warning appears when a language configured on your Drupal site does not have dedicated language-specific field types (such as language dictionaries or analyzers) provisioned in the SearchStax application schema.
If you want to resolve the warning and enable language-specific search features (such as stemming, stop words, or synonyms for your language), you can configure this in the SearchStax dashboard:
Navigate to App Settings > Languages in SearchStax and add the required language.
Optionally, configure Search Profiles with Data Filters to customise search behaviour per language.
Cloud Platform