Documentation > Migrations

Solr Migration Option 2 - New Index with the Default Configuration

Migrations

The simplest route when your configuration is close to stock: a new index already carries a configuration made for its Solr version.

If your old schema is essentially the stock Opensolr / Drupal / WordPress / Search API Solr config, you do not need a custom conversion. Create a new index and accept the modern default schema. Zero schema-conversion work.

  1. Create a new Opensolr index in a region that runs a current Solr version (each region card on Add New Index shows its version: regions). Pick a non-colliding name — e.g. add a _v2 suffix. For hybrid search, pick a region with site search.
  2. Update your client to point at the new index:
    • Drupal Search API Solr: Configuration → Search and metadata → Search API → your server → edit → change Solr core / path. Then drush search-api-solr:get-server-config & upload to the new index.
    • Drupal Opensolr Search module: Settings tab → Save & Connect against the new index.
    • WordPress Opensolr Search plugin: Settings tab → Save & Connect against the new index name.
    • Site search crawler: start a crawl on the new index (crawl your site); it fills the index from your start URLs.
    • Direct API / SolrJ / pysolr / SolrClient: change the connection string in your application config.
  3. Reindex from source-of-truth. Trigger your normal indexing pipeline against the new index. Verify numFound matches expectations; run sample queries.
  4. Cut over. When satisfied, delete the old index from the control panel.

Why this is the simplest path: the new index ships with a schema and solrconfig made for its Solr version out of the box — PointFields, leader/follower terminology, unified highlighter pre-configured.

Solr migration

Option 2: a new index with the default configuration (this page)