Elasticsearch has moved towards the removal of types in its system, which began with version 5.0 and has been progressively implemented through versions 6.0, 7.0, and 8.0. Originally, types were intended to provide multi-tenancy within a single index, but they proved to be problematic and incompatible with Lucene. To ease the transition for users, Elasticsearch introduced changes such as enforcing compatible mappings for fields with the same name across different types, preventing multiple types in new indices, and deprecating APIs that accept types. The transition involves adopting new "typeless" APIs, which no longer require or support types in URL paths, request bodies, or response bodies. Users are advised to perform certain upgrades, such as moving to version 6.8 before 7.0, stopping the use of _default_ mappings, and making adjustments to API calls to accommodate these changes. The ultimate goal is to eliminate the use of types entirely by version 8.0, requiring users to adapt their systems to the new typeless structure.