---
title: "Migrating the server from Drupal to Acquia Search powered by SearchStax"
date: "2025-02-12T10:51:33+00:00"
summary: "Migrate your Drupal server to Acquia Search powered by SearchStax with this step-by-step guide for seamless setup."
image:
type: "page"
url: "/acquia-cloud-platform/migrating-server-drupal-acquia-search-powered-searchstax"
id: "bf2bacd5-a672-4ce9-a6ff-e9189cc7ac33"
---

1.  If your Search Index uses Solr Autocomplete, delete it at `/admin/config/search/search-api/index/name_of_index/autocomplete`  
     
    
    ![Deleting the Autocomplete](https://acquia.widen.net/content/rvzxiduyeo/web/1f024_SCR-20260428-jpdw.png?w=1090&v=3b43edaf-16b7-462f-95ac-d3233e904c86&itok=yDf4G_Fo)
    
2.  In the administration menu of your application, click **Configuration**.
3.  In the **Search and metadata** section, click **Migrate from Solr to SearchStax**.
4.  Click **Migrate**.

![The "Migrate from Solr to SearchStax Site Search" page in the Drupal administration panel, guiding users through migrating search functionality from Solr to SearchStax. It includes three sections: Migrate search servers, where the Acquia Search API Solr server is ready for migration; Copy search indexes, which lists the Acquia Search Solr Index but indicates that its server has not been migrated yet; and Switch index of search views, which allows switching search views to the new index but remains…](https://acquia.widen.net/content/bhukcfysgs/web/search-searchstax_migrate-server.png?w=1090&v=8f4d726a-9a5f-4405-8ae8-79ebafd5a20a&itok=R_8oifXJ)

4.  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.
5.  Skip this step if you see your apps in the list.
    1.  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](https://www.searchstax.com/docs/searchstudio/creating-a-searchstax-studio-app-2/).  
        After you create the app, navigate back to **Configuration** > **Search and Metadata** > **Migrate from Solr to SearchStax**.
    2.  Click **Migrate**, and toggle the refresh button under the SearchStax app to migrate if you do not see the app in the list.
6.  Select the app you want to connect to from the list.
7.  Select **Search view and display**, and choose the desired view to fetch the settings from.
8.  Click **Migrate server now**.

![The "Migrate server Acquia Search API Solr server" page in the Drupal administration panel. A status message confirms that the login was successful. The page provides options to select a SearchStax app for migration, ensuring that it is an unused app not yet linked to any Search API server. Users can also choose whether to migrate settings from an existing search view and display. The Detected languages section lists supported languages, including English (text\_en) and German (text\_de), along with…](https://acquia.widen.net/content/y89yss2em3/web/search-searchstax_migrate-server-now.png?w=720&v=cee9da69-4661-4367-81ca-b530b70a70f8&itok=oRgx5fPz)

After successful migration, the system displays several success status messages that indicate the artifacts that are migrated.

![A web interface showing successful migration status messages for SearchStax Site Search configuration. For example, Added English synonyms to the SearchStax app.](https://acquia.widen.net/content/qz3ohvwwe5/web/search-searchstax_migrate-status-messages.png?w=720&v=834087b8-f91b-49b6-8f08-2c780cbc2328&itok=3q8r0wJ0)

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:

1.  Navigate to **App Settings > Languages** in SearchStax and add the required language.
2.  Optionally, configure **Search Profiles** with **Data Filters** to customise search behaviour per language.

For full configuration instructions, refer to the [SearchStax multi-language documentation](https://www.searchstax.com/docs/searchstudio/searchstax-studio-multi-language-experiences/).

Next step
---------

[Migrate the index from Drupal to Acquia Search powered by SearchStax](/acquia-cloud-platform/migrating-index-drupal-acquia-search-powered-searchstax "Migrating the index from Drupal to Acquia Search powered by SearchStax")