> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/elasticsearch/migration/elasticsearch-post-migration-health-check.md).

# Elasticsearch Post Migration Health Check

Perform the following validation checks after migration. For High Availability deployments, perform on each application server, where applicable.

1. Log in to the Cortex XSOAR server using both of these methods:

   Log in using the configured authentication method that was previously used with the Bolt database (e.g., SAML or AD Auth).

   Log in using the default Administrator account.
2. Install the [Elasticsearch Monitoring Pack](https://xsoar.pan.dev/marketplace/details/ElasticsearchMonitoring/) to check indices in Elasticsearch for shards, replicas, and cluster status. Add the Elasticsearch monitoring dashboard after pack installation.

   (High Availability) - Perform only on first app server.
3. (High Availability) - Validate application servers are online by navigating to Settings → Advanced → **App Servers**.
4. Validate integration settings by viewing Settings → **Integrations** and filtering for enabled integrations.
5. Validate that content such as Playbooks and Automations is available, via their respective menus in the UI.
6. Create a new incident, and validate the following:
   * New incident ID should be newer than the previous Incident ID in the system. If the new Incident ID is not newer, this could mean data was not migrated in the correct order, leading to data integrity issues. If data was not migrated in order from oldest to newest, you might need to perform the migration again.
   * Playbooks run successfully.
7. Open migrated incidents and indicators to verify they were migrated correctly.

   Query for historical incidents, for example, the last six months. Open older incidents and review Work Plan and War Room.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/elasticsearch/migration/elasticsearch-post-migration-health-check.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.