Elastic Enterprise Search end of life is not a routine major upgrade. Elastic published the retirement notice 15 April 2025, and there is no Enterprise Search in Elastic 9.x. If you depend on App Search migration paths or need a Workplace Search alternative, this is a re-platforming programme: map APIs, relevance, connectors and permissions before copying indices.
Which dependency do you actually have?
| Dependency | What disappears in 9.x | Redesign focus |
|---|---|---|
| App Search | Product/API layer | Engines, search keys, relevance, synonyms, curations, analytics |
| Workplace Search | Product layer | Connectors, identity mapping, document permissions, sync semantics |
| Elastic web crawler | ES-managed crawler path | Extraction rules, scheduling, indexing destination |
| Native Elasticsearch only | Nothing from Enterprise Search | Confirm genuinely native before major upgrade |
If you cannot answer this from configuration and code, the estimate is premature.
Retirement is not the same as end of support
- Retirement notice: 15 April 2025, no new major releases
- 8.x maintenance: until 15 Jan 2027
- 8.x support tail: until 15 Jul 2027
Elastic 8.19 documentation states Enterprise Search is discontinued in Elastic 9.0.0, including App Search, Workplace Search, the Elastic Web Crawler and managed connectors. “Upgrade Enterprise Search 8 to 9” has no valid target.
Pair this with Elasticsearch 8.x EOM planning and the EOL hub.
What App Search teams must replace
App Search hid Elasticsearch behind engines, search keys, relevance tuning, curations and analytics:
Engines: which indices/aliases represent the same corpus?
Search API: native queries or a compatibility service?
Search keys: browser auth without cluster credentials?
Relevance, synonyms, curations: translate and replay-test
Analytics: which click/query events survive?
Crawler: Open Web Crawler, self-managed crawler or OpenSearch ingestion?
For Adobe Commerce or Magento site search using App Search, see Commerce search cutover, native catalogue search is a different path.
Workplace Search: identity and connectors
The hard parts are content-source connectors, document permissions, incremental sync and ACL trimming. Inventory every source, sync cursor, deleted-document handling and retention before selecting a target. A workplace search alternative that cannot reproduce access trimming is not equivalent.
Target options (honest trade-offs)
Native Elasticsearch: Elastic's supported direction: native queries, Open Web Crawler, self-managed connectors. Lowest change on Elastic licensing.
OpenSearch: valid when licence posture, AWS operations or portability justify re-platforming. Build a feature matrix first.
Either path needs traffic replay and relevance acceptance tests. Our ecommerce OpenSearch case is a UAE reference architecture, not an Australian client claim.
Australian delivery
Source/target clusters, snapshots and dual-write queues can stay in ap-southeast-2 or ap-southeast-4. See Sydney & Melbourne residency.
Readiness checklist
- Inventory App Search / Workplace Search APIs and consumers
- Map relevance, synonyms, curations and analytics requirements
- Document connector permissions and sync semantics
- Choose native ES vs OpenSearch from feature matrix
- Replay production queries before cutover
- Plan rollback before 15 January 2027
Limitations
Not legal or procurement advice. Re-check Elastic retirement and EOL pages before production. MSAZN proof is UAE. label geography honestly in bids.
Sources: Elastic EOL / Enterprise Search retirement, verified 8 August 2026.
Next step: Book a version audit · EOL hub · Enterprise Search dependency scoping
