ECH Version Upgrade: Basic, Standard, and Advanced

Overview

A fixed-price, time-boxed implementation engagement to upgrade one (1) Elastic Cloud Hosted (ECH) deployment from version 8.19.x to the current generally available Elastic release (9.x) in a single upgrade step. The engagement covers pre-upgrade assessment, remediation assistance, upgrade execution, post-upgrade validation, and an engagement report. This engagement is limited to one (1) ECH deployment only. Any additional clusters, deployments, environments, or expanded scope are expressly out of scope unless otherwise agreed in a mutually executed change order.

Scope

• Pre-upgrade assessment of the existing ECH environment, including cluster health, Elastic version, architecture, plugins, data volume, and potential upgrade blockers
• Identification of risks and provision of actionable remediation recommendations
• Remediation assistance to address pre-upgrade issues (settings, plugin compatibility, configuration adjustments)
• Execution of one (1) upgrade step from version 8.19.x to the current generally available Elastic release (9.x)
• Rollback planning and readiness validation prior to upgrade execution
• Post-upgrade validation of cluster health, index consistency, and data integrity
• Hyper-care support for monitoring and troubleshooting immediately following upgrade completion
• Delivery of an engagement report covering the pre- and post-upgrade assessments, upgrade steps taken, and next-step recommendations

Out of scope

This engagement does not include:

• Upgrade of more than one (1) ECH deployment
• Upgrade of self-managed deployments (including ECK, ECE, or self-orchestrated environments)
• Upgrade of Serverless projects
• Upgrade from versions earlier than 8.19.x (see Standard or Advanced tiers)
• Multi-step upgrade paths (more than one intermediate version hop)
• Performance testing beyond review of available cluster diagnostics and metrics
• Custom architecture design deliverables beyond the written recommendations included in the engagement report
• Ongoing support, operational ownership, or post-engagement remediation assistance unless separately purchased
• Project management beyond internal Elastic delivery coordination

Any work outside the scope above requires a mutually executed change order and may result in additional fees, revised assumptions, and schedule changes.

Engagement timeline

• Scheduled to commence approximately 6–8 weeks after purchase, subject to resource availability and Customer readiness
• Delivered by an Elastic Consultant or a certified partner resource under Elastic oversight
• Unless otherwise agreed in writing, the services will be delivered remotely
• Delivery is expected to occur over contiguous business days or contiguous calendar weeks, as scheduled by Elastic
• If delivery is delayed, interrupted, or rescheduled due to Customer availability, access issues, environment readiness, or other Customer dependencies, Elastic may reassign resources, adjust the schedule, or require an Order Form (change order)
• Time scheduled for the engagement that cannot be used due to Customer delay, unavailability, failure to meet dependencies, or inability to provide required access will count against the total consulting days

Fixed-price conditions and assumptions

The fixed price is based on the following assumptions and conditions:

• Customer provides all required access, credentials, documentation, and relevant architectural information before the kickoff call
• Customer designates a single point of contact and ensures appropriate technical stakeholders are available and responsive throughout the engagement
• The target infrastructure is provisioned, accessible, operational, and ready for configuration at the start of the engagement
• Customer objectives, priorities, and the search use case are defined and agreed before kickoff
• The engagement covers a net-new (greenfield) implementation only; migration or evaluation of an existing deployment is out of scope
• The engagement is limited to one (1) in-scope dataset, up to five (5) sample queries, and advanced RBAC for the users and document-level controls defined in Scope
• The engagement is limited to the configuration of one (1) self-managed deployment (including ECE/ECK) of up to ten (10) nodes only
• No material changes to scope, target environment, architecture, or objectives are introduced after kickoff
• Elastic's configuration and recommendations depend on the completeness, accuracy, and timeliness of the information and data provided by Customer or made available from the target environment during the engagement

If any of the above assumptions are not met, Elastic may adjust the schedule, limit the services performed to fit the fixed-price scope, or require an Order Form (change order).

Deliverables

• Pre-upgrade assessment findings (documented)
• Upgrade execution (one upgrade step: 8.19.x → 9.x)
• Post-upgrade assessment summary
• Engagement report covering pre/post-upgrade assessments, upgrade steps, and next-step recommendations

Completion

The engagement will be considered complete upon delivery of the engagement report and post-upgrade assessment, and confirmation that the upgraded ECH deployment is operational at the target version. The engagement may also be deemed complete if Customer delays, is unavailable, fails to meet required dependencies, or is otherwise unable to participate after Elastic has made commercially reasonable efforts to schedule and deliver the services within the agreed scope.

General terms

Capitalized terms used but not defined in this package description have the meanings given to them in the Order Form, the applicable Service Description, or the Elastic Services Agreement.

No formal Customer signoff and no milestone or deliverable acceptance process applies to this fixed-price Services Package. Each Service is deemed accepted upon Completion.

"Completion" means, with respect to a Service, the point at which Elastic has performed the activities within the scope of this Services Package, including (where applicable) delivery of any written report, materials, or knowledge transfer session described in this package's scope, or the expiry of the time-boxed engagement period for this package, whichever occurs first. Completion does not require Customer signoff or acceptance of any deliverable.

Customer is solely responsible for the backup, maintenance, and security of its environment, systems, and data. Elastic is not responsible for any configuration changes, data loss, downtime, or other impact to Customer's environment arising from or in connection with the Service.

This engagement delivers a configured net-new, self-managed Elastic document search solution, including search use case analysis, data modeling and ingestion, advanced example query implementation, advanced RBAC configuration, infrastructure provisioning, and a final report, within the defined fixed-price scope. Elastic does not guarantee any specific performance, cost, operational, or business outcome beyond the deliverables defined above. Customer remains solely responsible for ongoing operations, configuration changes made outside the engagement scope, and all post-engagement activities related to its environment.

References in this package to validation, testing, acceptance tests or acceptance test harnesses, golden queries, launch readiness, or go-live describe activities performed, demonstrated, or delivered by Elastic and do not create any Customer acceptance, signoff, testing, or payment condition. Completion occurs as defined in this package regardless of any such activity, and no portion of the fees is withheld or deferred pending any test result, validation, or go-live event.

Overview

A fixed-price, time-boxed implementation engagement to upgrade one (1) Elastic Cloud Hosted (ECH) deployment from a version in the range 7.17.29–8.18.x to the current generally available Elastic release (9.x) across two (2) sequential upgrade steps. The engagement covers pre-upgrade assessment, remediation assistance, upgrade execution across both steps, post-upgrade validation, and an engagement report. This engagement is limited to one (1) ECH deployment only. Any additional clusters, deployments, environments, or expanded scope are expressly out of scope unless otherwise agreed in a mutually executed change order.

Scope

• Pre-upgrade assessment of the existing ECH environment, including cluster health, Elastic version, architecture, plugins, data volume, and potential upgrade blockers
• Identification of risks and provision of actionable remediation recommendations
• Remediation assistance to address pre-upgrade issues at each upgrade step
• Execution of two (2) sequential upgrade steps from the Customer's starting version to the current generally available Elastic release (9.x), including one intermediate version hop
• Rollback planning and readiness validation prior to each upgrade step
• Post-upgrade validation of cluster health, index consistency, and data integrity after each step
• Hyper-care support for monitoring and troubleshooting immediately following final upgrade completion
• Delivery of an engagement report covering the pre- and post-upgrade assessments, upgrade steps taken, and next-step recommendations

Out of scope

This engagement does not include:

• Upgrade of more than one (1) ECH deployment
• Upgrade of self-managed deployments (including ECK, ECE, or self-orchestrated environments)
• Upgrade of Serverless projects
• Upgrade from versions earlier than 7.17.29 (see Advanced tier)
• Upgrade from versions 8.19.x or later (see Basic tier)
• More than two (2) upgrade steps
• Performance testing beyond review of available cluster diagnostics and metrics
• Custom architecture design deliverables beyond the written recommendations included in the engagement report
• Ongoing support, operational ownership, or post-engagement remediation assistance unless separately purchased
• Project management beyond internal Elastic delivery coordination

Any work outside the scope above requires a mutually executed change order and may result in additional fees, revised assumptions, and schedule changes.

Engagement timeline

• Scheduled to commence approximately 6–8 weeks after purchase, subject to resource availability and Customer readiness
• Delivered by an Elastic Consultant or a certified partner resource under Elastic oversight
• Unless otherwise agreed in writing, the services will be delivered remotely
• Delivery is expected to occur over contiguous business days or contiguous calendar weeks, as scheduled by Elastic
• If delivery is delayed, interrupted, or rescheduled due to Customer availability, access issues, environment readiness, or other Customer dependencies, Elastic may reassign resources, adjust the schedule, or require an Order Form (change order)
• Time scheduled for the engagement that cannot be used due to Customer delay, unavailability, failure to meet dependencies, or inability to provide required access will count against the total consulting days

Fixed-price conditions and assumptions

• Customer provides all required access, credentials, documentation, and relevant architectural information before the kickoff call
• Customer designates a single point of contact and ensures appropriate technical stakeholders are available and responsive throughout the engagement
• The ECH deployment to be upgraded is accessible to Elastic Consultants with sufficient permissions to perform upgrade operations
• The Customer's starting version is confirmed as being within the range 7.17.29–8.18.x prior to engagement commencement; any change in scope of the upgrade path requires a change order
• Maintenance windows of sufficient duration to perform each upgrade step are agreed and confirmed by Customer prior to each upgrade execution
• Customer is responsible for ensuring all required internal approvals, change management processes, and downtime authorizations are in place before each upgrade window begins
• Customer has an up-to-date snapshot or backup of the deployment prior to each upgrade step
• Scope is limited to one (1) ECH deployment and two (2) upgrade steps; additional deployments or steps require a change order

If any of the above assumptions are not met, Elastic may adjust the schedule, limit the services performed to fit the fixed-price scope, count impacted time against the allocated consulting days, or require a change order.

Deliverables

• Pre-upgrade assessment findings (documented)
• Upgrade execution (two sequential upgrade steps to 9.x)
• Post-upgrade assessment summary (covering both steps)
• Engagement report covering pre/post-upgrade assessments, upgrade steps, and next-step recommendations

Completion

The engagement will be considered complete upon delivery of the engagement report and post-upgrade assessment, and confirmation that the upgraded ECH deployment is operational at the target version. The engagement may also be deemed complete if Customer delays, is unavailable, fails to meet required dependencies, or is otherwise unable to participate after Elastic has made commercially reasonable efforts to schedule and deliver the services within the agreed scope.

General terms

Capitalized terms used but not defined in this package description have the meanings given to them in the Order Form, the applicable Service Description, or the Elastic Services Agreement.

No formal Customer signoff and no milestone or deliverable acceptance process applies to this fixed-price Services Package. Each Service is deemed accepted upon Completion.

"Completion" means, with respect to a Service, the point at which Elastic has performed the activities within the scope of this Services Package, including (where applicable) delivery of any written report, materials, or knowledge transfer session described in this package's scope, or the expiry of the time-boxed engagement period for this package, whichever occurs first. Completion does not require Customer signoff or acceptance of any deliverable.

Customer is solely responsible for the backup, maintenance, and security of its environment, systems, and data. Elastic is not responsible for any configuration changes, data loss, downtime, or other impact to Customer's environment arising from or in connection with the Service.

This engagement delivers a configured net-new, self-managed Elastic document search solution, including search use case analysis, data modeling and ingestion, advanced example query implementation, advanced RBAC configuration, infrastructure provisioning, and a final report, within the defined fixed-price scope. Elastic does not guarantee any specific performance, cost, operational, or business outcome beyond the deliverables defined above. Customer remains solely responsible for ongoing operations, configuration changes made outside the engagement scope, and all post-engagement activities related to its environment.

References in this package to validation, testing, acceptance tests or acceptance test harnesses, golden queries, launch readiness, or go-live describe activities performed, demonstrated, or delivered by Elastic and do not create any Customer acceptance, signoff, testing, or payment condition. Completion occurs as defined in this package regardless of any such activity, and no portion of the fees is withheld or deferred pending any test result, validation, or go-live event.

Overview

A fixed-price, time-boxed implementation engagement to upgrade one (1) Elastic Cloud Hosted (ECH) deployment from a version in the range 7.0.x–7.17.28 to the current generally available Elastic release (9.x) across three (3) sequential upgrade steps. The engagement covers pre-upgrade assessment, remediation assistance, upgrade execution across all three steps, post-upgrade validation, a knowledge transfer session, and an engagement report. This engagement is limited to one (1) ECH deployment only. Any additional clusters, deployments, environments, or expanded scope are expressly out of scope unless otherwise agreed in a mutually executed change order.

Scope

• Pre-upgrade assessment of the existing ECH environment, including cluster health, Elastic version, architecture, plugins, data volume, and potential upgrade blockers
• Identification of risks and provision of actionable remediation recommendations
• Remediation assistance to address pre-upgrade issues at each upgrade step
• Execution of three (3) sequential upgrade steps from the Customer's starting version to the current generally available Elastic release (9.x), including two intermediate version hops
• Rollback planning and readiness validation prior to each upgrade step
• Post-upgrade validation of cluster health, index consistency, and data integrity after each step
• Hyper-care support for monitoring and troubleshooting immediately following final upgrade completion
• Knowledge transfer session: a workshop or walkthrough of the upgrade process and outcomes for Customer technical stakeholders
• Delivery of an engagement report covering the pre- and post-upgrade assessments, upgrade steps taken, and next-step recommendations

Out of scope

This engagement does not include:

• Upgrade of more than one (1) ECH deployment
• Upgrade of self-managed deployments (including ECK, ECE, or self-orchestrated environments)
• Upgrade of Serverless projects
• Upgrade from versions 7.17.29 or later (see Basic or Standard tiers)
• More than three (3) upgrade steps
• Performance testing beyond review of available cluster diagnostics and metrics
• Custom architecture design deliverables beyond the written recommendations included in the engagement report
• Ongoing support, operational ownership, or post-engagement remediation assistance unless separately purchased
• Project management beyond internal Elastic delivery coordination

Any work outside the scope above requires a mutually executed change order and may result in additional fees, revised assumptions, and schedule changes.

Engagement timeline

• Scheduled to commence approximately 6–8 weeks after purchase, subject to resource availability and Customer readiness
• Delivered by an Elastic Consultant or a certified partner resource under Elastic oversight
• Unless otherwise agreed in writing, the services will be delivered remotely
• Delivery is expected to occur over contiguous business days or contiguous calendar weeks, as scheduled by Elastic
• If delivery is delayed, interrupted, or rescheduled due to Customer availability, access issues, environment readiness, or other Customer dependencies, Elastic may reassign resources, adjust the schedule, or require an Order Form (change order)
• Time scheduled for the engagement that cannot be used due to Customer delay, unavailability, failure to meet dependencies, or inability to provide required access will count against the total consulting days

Fixed-price conditions and assumptions

• Customer provides all required access, credentials, documentation, and relevant architectural information before the kickoff call
• Customer designates a single point of contact and ensures appropriate technical stakeholders are available and responsive throughout the engagement
• The ECH deployment to be upgraded is accessible to Elastic Consultants with sufficient permissions to perform upgrade operations
• The Customer's starting version is confirmed as being within the range 7.0.x–7.17.28 prior to engagement commencement; any change in scope of the upgrade path requires a change order
• Maintenance windows of sufficient duration to perform each of the three upgrade steps are agreed and confirmed by Customer prior to each upgrade execution
• Customer is responsible for ensuring all required internal approvals, change management processes, and downtime authorizations are in place before each upgrade window begins
• Customer has an up-to-date snapshot or backup of the deployment prior to each upgrade step
• Appropriate technical stakeholders are available to attend the knowledge transfer session
• Scope is limited to one (1) ECH deployment and three (3) upgrade steps; additional deployments or steps require a change order

If any of the above assumptions are not met, Elastic may adjust the schedule, limit the services performed to fit the fixed-price scope, count impacted time against the allocated consulting days, or require a change order.

Deliverables

• Pre-upgrade assessment findings (documented)
• Upgrade execution (three sequential upgrade steps to 9.x)
• Post-upgrade assessment summary (covering all three steps)
• Knowledge transfer session (workshop/walkthrough of upgrade process and outcomes)
• Engagement report covering pre/post-upgrade assessments, upgrade steps, and next-step recommendations

Completion

The engagement will be considered complete upon delivery of the engagement report, post-upgrade assessment, and knowledge transfer session, and confirmation that the upgraded ECH deployment is operational at the target version. The engagement may also be deemed complete if Customer delays, is unavailable, fails to meet required dependencies, or is otherwise unable to participate after Elastic has made commercially reasonable efforts to schedule and deliver the services within the agreed scope.

General terms

Capitalized terms used but not defined in this package description have the meanings given to them in the Order Form, the applicable Service Description, or the Elastic Services Agreement.

No formal Customer signoff and no milestone or deliverable acceptance process applies to this fixed-price Services Package. Each Service is deemed accepted upon Completion.

"Completion" means, with respect to a Service, the point at which Elastic has performed the activities within the scope of this Services Package, including (where applicable) delivery of any written report, materials, or knowledge transfer session described in this package's scope, or the expiry of the time-boxed engagement period for this package, whichever occurs first. Completion does not require Customer signoff or acceptance of any deliverable.

Customer is solely responsible for the backup, maintenance, and security of its environment, systems, and data. Elastic is not responsible for any configuration changes, data loss, downtime, or other impact to Customer's environment arising from or in connection with the Service.

This engagement delivers a configured net-new, self-managed Elastic document search solution, including search use case analysis, data modeling and ingestion, advanced example query implementation, advanced RBAC configuration, infrastructure provisioning, and a final report, within the defined fixed-price scope. Elastic does not guarantee any specific performance, cost, operational, or business outcome beyond the deliverables defined above. Customer remains solely responsible for ongoing operations, configuration changes made outside the engagement scope, and all post-engagement activities related to its environment.

References in this package to validation, testing, acceptance tests or acceptance test harnesses, golden queries, launch readiness, or go-live describe activities performed, demonstrated, or delivered by Elastic and do not create any Customer acceptance, signoff, testing, or payment condition. Completion occurs as defined in this package regardless of any such activity, and no portion of the fees is withheld or deferred pending any test result, validation, or go-live event.