Genealogy search moved from SQL Server to Elasticsearch
Challenge
A large genealogy archive searched through Microsoft SQL Server: slow name searches, limited matching across spelling variants and languages, and growing record volumes.
What we did
We rebuilt the full search engine on Elasticsearch: data pipelines from SQL Server, mappings and analyzers for multilingual name matching, relevance tuning and a migration with both systems running side by side.
Result
Search over 100M+ historical records with multilingual name matching, on a platform that scales with the archive.
