Skip to content

Rework data migration docs and add reindex to Serverless steps#4914

Closed
kilfoyle wants to merge 15 commits intoelastic:mainfrom
kilfoyle:4353/rework-ech2ess-mig
Closed

Rework data migration docs and add reindex to Serverless steps#4914
kilfoyle wants to merge 15 commits intoelastic:mainfrom
kilfoyle:4353/rework-ech2ess-mig

Conversation

@kilfoyle
Copy link
Contributor

@kilfoyle kilfoyle commented Jan 30, 2026

Please see the newer version of this PR: Rework migrate data docs (Take 2)



This PR:


Closes: #4353
Rel: https://github.com/elastic/docs-team/issues/30
Rel: https://github.com/elastic/docs-content-internal/issues/467

@elastic elastic deleted a comment from github-actions bot Feb 5, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

✅ Vale Linting Results

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@kilfoyle kilfoyle changed the title DRAFT ONLY: Rework data migration docs Rework data migration docs and add reindex to Serverless steps Feb 6, 2026
@kilfoyle kilfoyle marked this pull request as ready for review February 6, 2026 18:06
@kilfoyle kilfoyle requested a review from a team as a code owner February 6, 2026 18:06
Copy link
Member

@PeteGillinElastic PeteGillinElastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! A few thoughts below.


:::{important}
Kibana assets must be migrated separately using the {{kib}} [export/import APIs](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-saved-objects) or recreated manually.
Templates, data stream definitions, and ILM policies, must be in place _before_ you start data migration.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's an important wrinkle here. You do want your templates set up with things like the correct index mappings and most other index settings. But a lot of the time you do not want your ingest pipelines in place before you reindex. The reason being that the data will have been run through whatever pipeline is in place in ECH when it was ingested there, and (unless it happens to be idempotent) you don't want to run it through the same pipeline a second time in serverless.

This is potentially an awkward thing from an ergonomics perspective. I think that @pete-naylor has thought more about how to handle it smoothly than I have, so I'll defer to him.

Copy link
Member

@PeteGillinElastic PeteGillinElastic Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Of course, if you are going to be switching the thing that was previously writing into ECH to write into serverless instead, you presumably do want the ingest pipelines in place before you start doing that...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching that @PeteGillinElastic! I rephrased the warning to try and catch the nuance about ingest pipelines.

screen3

Not really related to this, but I've also expanded the parent Migrate your Elasticsearch data landing page to summarize the different data types and migration methods, so maybe that'll help.

@kilfoyle
Copy link
Contributor Author

@shainaraskas and @eedugon Thanks very much for your feedback! Edu, the detail you provided about the various data types is super helpful so I've incorporated that into the main Migrate your Elasticsearch data page.

@eedugon
Copy link
Contributor

eedugon commented Feb 13, 2026

@shainaraskas and @eedugon Thanks very much for your feedback! Edu, the detail you provided about the various data types is super helpful so I've incorporated that into the main Migrate your Elasticsearch data page.

Wow, the new content feels really awesome, that's exactly what was missing! It would be great if we get some review by product experts to ensure everything is technically accurate.

I'll review and share some comments soon.

@ppf2
Copy link
Contributor

ppf2 commented Feb 18, 2026

Here's a suggestion for an alternate format:

  1. We can create pages for each migration method: Reindex from remote, Logstash and snapshot/restore.
  2. Then create from-to tables like the following which links to the documentation page for these methods.

For example, for the "To Serverless" scenario, currently the only supported From for reindex from remote is Hosted:

From To Supported Methods
Hosted Serverless Reindex from remote*, Logstash
ECE Serverless Logstash
ECK Serverless Logstash
Serverless Serverless Logstash

*Technical Preview

@kilfoyle
Copy link
Contributor Author

kilfoyle commented Feb 19, 2026

@ppf2 I can try what you suggest. To start, I'd need to verify that the tables are correct and exhaustive.

Would you be able confirm if these are right? Or would you have an idea who best to ask?

I do worry that these tables would over-complicate things a bit. The reason for the current page organization is that it imitates how we organize the "Deploy" section, but I'm open to changing that.

To Elastic Cloud Hosted:

From To Supported Methods
ECH ECH reindex from remote, restore from snapshot, Logstash
ECE ECH reindex from remote, restore from snapshot, Logstash
ECK ECH reindex from remote, restore from snapshot, Logstash
Serverless ECH reindex from remote, Logstash
Self-managed ECH reindex from remote*, restore from snapshot, Logstash

To Elastic Cloud Enterprise:

From To Supported Methods
ECH ECE reindex from remote, restore from snapshot, Logstash
ECE ECE reindex from remote, restore from snapshot, Logstash
ECK ECE reindex from remote, restore from snapshot, Logstash
Serverless ECE Logstash
Self-managed ECE reindex from remote, restore from snapshot, Logstash

To Elastic Cloud on Kubernetes:

From To Supported Methods
ECH ECK reindex from remote, restore from snapshot, Logstash
ECE ECK reindex from remote, restore from snapshot, Logstash
ECK ECK reindex from remote, restore from snapshot, Logstash
Serverless ECK reindex from remote, Logstash
Self-managed ECK reindex from remote, restore from snapshot, Logstash

To Elastic Cloud Serverless:

From To Supported Methods
ECH Serverless reindex from remote*, Logstash
ECE Serverless Logstash
ECK Serverless Logstash
Serverless Serverless Logstash
Self-managed Serverless not currently supported
  • Technical preview starting in 9.3

To Elastic Self-managed:

From To Supported Methods
ECH Self-managed reindex from remote, restore from snapshot, Logstash
ECE Self-managed reindex from remote, restore from snapshot, Logstash
ECK Self-managed reindex from remote, restore from snapshot, Logstash
Serverless Self-managed reindex from remote, Logstash
Self-managed Self-managed reindex from remote, restore from snapshot, Logstash

@kilfoyle
Copy link
Contributor Author

@ppf2 I've opened a new PR that follows your suggestion of having a single page for each migration method:

Rework migrate data docs (Take 2)

I think it could work nicely.

@eedugon
Copy link
Contributor

eedugon commented Feb 24, 2026

@kilfoyle : the serverless row in one of these blocks is probably incorrect:

image

Whatever is the right value should probably be the same in both cases.

And in this block I have a question:

image

How is it possible to support using Logstash to send data from ECE or ECK to Serverless but not from a self-managed cluster to Serverless? I'm tempted to say that has to be a mistake, as technically speaking, an ECK or ECE Elasticsearch cluster is the same as a self-managed cluster: they run on self-managed infrastructure, and all of them have HTTP endpoints controlled and created by the user.

Copy link
Contributor

@eedugon eedugon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small comment added, sorry I haven't been able to review the entire PR again. If needed please let me know!! :)

@kilfoyle
Copy link
Contributor Author

Thanks @edu! I've added your suggestions in the new PR.

I'll close this PR in favour of the new one: #5244

@kilfoyle kilfoyle closed this Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Migration] Rework and expand data migration section

5 participants