migrate-from-algolia

Migrate Algolia indices and records to Elasticsearch with mappings and analyzers.

6|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/patrykkopycinski/elastic-cursor-plugin --skill migrate-from-algolia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-algolia
Source: https://github.com/patrykkopycinski/elastic-cursor-plugin/tree/main/.cursor/skills/migrate-from-algolia
Command: npx skills add https://github.com/patrykkopycinski/elastic-cursor-plugin --skill migrate-from-algolia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating search from Algolia to Elasticsearch requires translating index schemas, analyzers, synonyms, and data formats while preserving relevance and faceting behavior. This process is error-prone when done manually and often results in broken searches, missing facets, or degraded relevance.

Core Features & Use Cases

  • Index analysis and mapping: Identify Algolia index structure, attributes for search vs display, and facet fields to create equivalent Elasticsearch mappings.
  • Analyzer and synonym handling: Configure analyzers for typo tolerance and import Algolia synonym sets to maintain search behavior.
  • Data export and bulk import: Transform exported Algolia records into Elasticsearch documents and perform bulk indexing, then validate with side-by-side queries.
  • Use Case: Move an e-commerce site's product search from Algolia to Elasticsearch, preserving facets, synonyms, and typo-tolerant relevance.

Quick Start

Use the migrate-from-algolia skill to detect Algolia index schemas, export and transform records, import synonyms, create matching Elasticsearch mappings, and bulk index the data for validation.

Frequently Asked Questions about migrate-from-algolia

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Algolia indices to Elasticsearch while preserving search relevance?

To migrate Algolia indices to Elasticsearch, you need to transform index mappings, configure analyzers for typo tolerance, import synonym sets, and bulk index records. This preserves search relevance and faceting behavior during the transition.

What is the best way to transfer Algolia synonyms and analyzers to Elasticsearch?

Transferring Algolia synonyms and analyzers involves configuring Elasticsearch analyzers for typo tolerance and importing Algolia synonym sets. This maintains equivalent search behavior and relevance after the index migration.

Can I map Algolia facet fields to Elasticsearch mappings automatically?

Mapping Algolia facet fields to Elasticsearch requires identifying Algolia index structure and attributes for search versus display. This allows you to create equivalent Elasticsearch mappings that preserve faceted search configuration.

How do I bulk index exported Algolia records into Elasticsearch?

Bulk indexing Algolia records into Elasticsearch transforms exported Algolia data into Elasticsearch documents. You then perform bulk indexing and validate the migration using side-by-side relevance queries.

Does migrating from Algolia to Elasticsearch break existing typo-tolerant search behavior?

Migrating from Algolia to Elasticsearch can preserve typo-tolerant search behavior by configuring Elasticsearch analyzers specifically to replicate Algolia's typo tolerance and synonym management.

Why does my Algolia to Elasticsearch migration result in missing facets and degraded relevance?

Missing facets and degraded relevance during an Algolia to Elasticsearch migration occur when index mapping transformation and analyzer configuration are done incorrectly. Properly mapping facet fields and importing synonyms resolves this.