> 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.15/onboard-cortex-xsoar/elasticsearch/migration/manage-partial-migration-to-elasticsearch.md).

# Manage Partial Migration to Elasticsearch

Manage a partial Cortex XSOAR 6.15 migration to Elasticsearch and complete the remaining data migration.

After migrating to Elasticsearch, you can verify that your data was migrated in the `elastic-migration-results` file located in the migration directory.

If you identify that there are items that were not migrated, you can migrate those objects using the migration tool.

{% hint style="info" %}

* You must run the migration tool from the same directory where you originally ran the migration. The migration tool reads from the **`elastic-migration-results`** file located in the migration directory to determine which data must still be migrated.
* Always migrate older data before newer data. Migrating partitions out of order can cause duplicate incident IDs.
* By default, the migration tool skips over objects larger than 100 megabytes. After the migration process runs, you can view the skipped large objects and determine whether to migrate them. For more information, see [Validate the Migration to Elasticsearch](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/elasticsearch/migration/validate-the-migration-to-elasticsearch.md).
  {% endhint %}

1. Stop the Cortex XSOAR server.

   Ubuntu: **`sudo service demisto stop`**
2. Run the **`./elasticMigrator`** command with either **demisto** or **sudo** permissions.

   The migration tool identifies that a migration already executed for your environment.
3. When prompted to view the results of the previous execution, enter **`yes`**.

   ![](https://content.gitbook.com/content/8xEMUKpU65o1wagTHaO3/blobs/OWCPrZ9JeQrNem8xTSXG/f3331266b9409ffd6d3e1a3fb0e7155ae3823b68f20c2b775183ee1eba6a9568.png)

   You can see that the audits object was not migrated.
4. Run the `./elasticMigrator` command and use the `objects-to-migrate` flag to migrate any items that were not migrated.
5. Start the Cortex XSOAR service.

   Ubuntu: `sudo service demisto start`
6. [Validate the migration](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/elasticsearch/migration/validate-the-migration-to-elasticsearch.md).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/elasticsearch/migration/manage-partial-migration-to-elasticsearch.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.