algolia-migration-deep-dive

name	algolia-migration-deep-dive
description	Migrate to Algolia from Elasticsearch, Typesense, or Meilisearch. Covers data migration, query translation, replaceAllObjects zero-downtime swap, and strangler fig traffic shifting. Trigger: "migrate to algolia", "switch to algolia", "algolia migration", "elasticsearch to algolia", "replace search engine", "algolia replatform".
allowed-tools	Read, Write, Edit, Bash(npm:*), Bash(node:*), Bash(curl:*)
version	1.0.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","search","algolia"]
compatible-with	claude-code

Algolia Migration Deep Dive

Overview

Comprehensive guide for migrating from another search engine (Elasticsearch, Typesense, Meilisearch, or custom) to Algolia. Uses the strangler fig pattern: run old and new in parallel, gradually shift traffic, then cut over.

Migration Planning

From	To Algolia	Difficulty	Duration
Elasticsearch	Medium — query syntax differs significantly	2-4 weeks
Typesense	Low — similar hosted model	1-2 weeks
Meilisearch	Low — similar API concepts	1-2 weeks
Custom SQL LIKE	Low — major upgrade	1-2 weeks
Solr	Medium — config-heavy to API-driven	2-4 weeks

Instructions

Step 1: Assess Current Implementation

# Find all search-related code
grep -rn "elasticsearch\|elastic\|typesense\|meilisearch\|\.search(" \
  --include="*.ts" --include="*.tsx" --include="*.js" src/ | wc -l

# Inventory current search features used
grep -rn "aggregations\|facets\|filters\|sort\|highlight\|suggest" \
  --include="*.ts" --include="*.tsx" src/

// Document current capabilities
interface MigrationAssessment {
  currentEngine: string;
  recordCount: number;
  indexCount: number;
  features: {
    fullTextSearch: boolean;
    faceting: boolean;
    filtering: ;
    : ;
    : ;
    : ;
    : ;
    : ;
    : ;
  };
  : [];  
  : [];       
}