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

# Manage Partial Migration to Elasticsearch

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" %}

### Note

* 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.13/learn-about-cortex-xsoar/onboarding-in-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`**.

   ![partial\_migration.png](/files/KIUQeTTg2WuZR8BhKCbQ)

   In the figure above, for example, we 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.13/learn-about-cortex-xsoar/onboarding-in-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 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/manage-partial-migration-to-elasticsearch.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.