[FEAT] 🟣 Phase 7: Cleanup (Weeks 17-18)

Description

Goal: Remove legacy code and decommission 1.0 infrastructure
Timeline: 2 weeks
Business Impact: Cost savings realized
Status: 📋 Planned

Desired Outcome

Business Outcome:

dotCMS operates on a clean, modern OpenSearch 3.x infrastructure with reduced operational costs, improved maintainability, and eliminated technical debt from the migration, while customers continue to experience reliable search functionality on the new supported platform.

Technical Outcome:

All legacy code (ES7ClientToOpenSearch1Adapter, OSClientToOpenSearch1Adapter, feature flags, dual-write logic) removed from codebase, OpenSearch 1.0 infrastructure safely decommissioned with final backup retained, and OpenSearch 3.x running as sole production cluster with clean architecture and comprehensive documentation.

Target Personas

• Developer teams
• Content teams
• DevOps teams
• System administrators (dotCMS)

Links

No response

Start by inventorying the named ES7ClientToOpenSearch1Adapter, OSClientToOpenSearch1Adapter, feature flags, dual-write logic, and OpenSearch infrastructure configuration. The issue provides no files or tests, so first identify the affected code and deployment entry points; done means the legacy components are removed, OpenSearch 1.0 is safely decommissioned with a final backup, OpenSearch 3.x is the sole production cluster, and documentation is complete.