Case study
AppSearch Crawler Overhaul for a Japanese Engineering Conglomerate
How SquareShift resolved Elastic App Search crawler errors and migrated 200K+ documents from Swiftype for a Japanese engineering conglomerate.
A global Japanese conglomerate in electrical engineering and software, running search across four B2B and B2C web platforms.
Its legacy Swiftype search needed a stable path onto Elastic App Search without disrupting live document indexing.
Documents migrated from Swiftype to Elastic App Search. B2B and B2C domains unified under one crawler. Indexing failures resolved for reliable site search.
Key servicesHow SquareShift delivered it.
The challenge
The client — a global Japanese engineering and software conglomerate — ran four domain-specific PHP web applications on Swiftype, Elastic’s legacy site-search product. It wanted to move onto Elastic App Search, but crawler tuning and document ingestion problems stood in the way of a clean cutover.
What we delivered
SquareShift worked directly with Elastic’s Japan and US engineering teams to tune crawler settings and resolve indexing failures. The team migrated more than 200,000 documents from Swiftype to App Search, covering all four domains without disrupting the live search experience.
The payoff
All four B2B and B2C domains now run on a fully functional Elastic App Search crawler, with the Swiftype-era incompatibilities resolved. Site search is reliable and real-time across every domain the client migrated.
A crawler migration lives or dies on indexing accuracy, not speed. Get the document parsing wrong and every downstream search query inherits the error across every domain it touches.
Platform & Software Engineering Practice Lead, SquareShift
Where this work sits