Skip to content

Add migration hub: consolidate migration docs into a single top-level section#5946

Draft
alexandra5000 wants to merge 9 commits intoelastic:mainfrom
alexandra5000:migration-hub
Draft

Add migration hub: consolidate migration docs into a single top-level section#5946
alexandra5000 wants to merge 9 commits intoelastic:mainfrom
alexandra5000:migration-hub

Conversation

@alexandra5000
Copy link
Copy Markdown
Contributor

@alexandra5000 alexandra5000 commented Apr 16, 2026

Summary

Creates a new migrate/ top-level section consolidating all migration docs currently scattered across Reference, Manage data, and Solutions.

  • Moves 13 existing files (git history preserved), adds new files (section indexes, new guides)
  • Adds redirects for all moved pages
  • Wired temporarily after manage-data in docset.yml — final nav placement is pending elastic/docs-builder#2927

Closes https://github.com/elastic/docs-content-internal/issues/831

What moved where

Old location New location
reference/fleet/migrate-from-beats-to-elastic-agent.md migrate/beats-to-elastic-agent/migrate-from-beats.md
reference/fleet/migrate-auditbeat-to-agent.md migrate/beats-to-elastic-agent/migrate-from-auditbeat.md
manage-data/migrate.md migrate/elasticsearch-data/index.md
manage-data/migrate/migrate-data-between-elasticsearch-clusters-with-minimal-downtime.md migrate/elasticsearch-data/cluster-to-cluster.md
manage-data/migrate/migrate-with-logstash.md migrate/elasticsearch-data/with-logstash.md
manage-data/migrate/migrate-internal-indices.md migrate/elasticsearch-data/system-indices.md
manage-data/migrate/migrate-from-a-self-managed-cluster-with-a-self-signed-certificate-using-remote-reindex.md migrate/elasticsearch-data/remote-reindex.md
manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md migrate/data-management/index.md
manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md migrate/data-management/to-ilm.md
manage-data/lifecycle/index-lifecycle-management/migrate-index-allocation-filters-to-node-roles.md migrate/data-management/to-data-tiers.md
manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle.md migrate/data-management/ilm-to-data-stream-lifecycle.md
manage-data/lifecycle/rollup/migrating-from-rollup-to-downsampling.md migrate/data-management/rollup-to-downsampling.md
solutions/security/get-started/automatic-migration.md migrate/to-elastic-security/automatic-migration.md

What stays in place (linked from hub, not moved)

  • deploy-manage/ — ECE Podman, remote cluster auth, CCS template, Heroku (infrastructure ops)
  • deploy-manage/upgrade/ — Kibana saved object migrations (upgrade context)
  • solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md (product-specific)
  • reference/fleet/migrate-elastic-agent.md (operational agent task, not ingest migration)
  • All troubleshoot/ migration pages

New content added

  • migrate/apm-agents-to-edot/rum-js.md — Preview-state page for Elastic APM RUM JS → EDOT Browser migration; full guide pending EDOT Browser GA
  • migrate/to-edot-collector/from-apm-agents.md — Guide for migrating from APM Server ingestion to the EDOT Collector
  • migrate/to-edot-collector/from-upstream-collector.md — Full guide for migrating from an upstream OpenTelemetry Collector to EDOT Collector

Navigation and titles

All subsection nav titles follow a consistent "Migrate..." pattern. Sections are ordered by expected usage frequency:

  1. Migrate Elasticsearch data
  2. Migrate APM agents to EDOT
  3. Migrate to the EDOT Collector
  4. Migrate to Elastic Agent
  5. Migrate data management patterns
  6. Migrate to Elastic Security

Remaining placeholder

  • migrate/data-management/ecs-field-mapping.md — ECS field mapping migration (content not yet available)

Known build issue

22 validation errors of the form Can not validate docs-content://migrate/... because migrate/ is not yet registered in docs-builder's config/navigation.yml. This requires a separate docs-builder PR and will be addressed once elastic/docs-builder#2927 merges.

🤖 Generated with Claude Code

alexandra5000 and others added 9 commits April 16, 2026 19:38
Update relative links in moved files that relied on their old directory
depth, and update outbound links in external files that still pointed to
the old paths. Also fixes substitute and version syntax hints in
to-edot-collector/index.md.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Update ~30 files that still linked to old paths for docs moved into
the new migrate/ hub.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Kept hub path for Automatic Migration (/migrate/to-elastic-security/automatic-migration.md)
and took upstream's new path for Automatic Import (/explore-analyze/ai-features/automatic-import.md).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@shainaraskas
Copy link
Copy Markdown
Member

Hi - spotted this because I got pinged on elastic/docs-builder#3190

I think this section is too broadly scoped. When people think about moving from one tool to another in terms of internal elasticsearch functionality, they don't think about it as "migrating", but instead, moving between tools or features.

To me, migration (as presented in https://www.elastic.co/docs/manage-data/migrate) is PURELY a "get your data from one source to another" question, e.g. migrating between non-elastic and elastic platform, or migrating between elastic instances for one reason or another. This is a key use case that needs its own space.

Would suggest that these should stay where they are:

  • manage-data/lifecycle/index-lifecycle-management/migrate-ilm.md
  • manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md
  • manage-data/lifecycle/index-lifecycle-management/migrate-index-allocation-filters-to-node-roles.md
  • manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle.md
  • manage-data/lifecycle/rollup/migrating-from-rollup-to-downsampling.md

humbly suggest that moving between ingest tools should also stay out of this section, to keep the core story (which my team owns) clear.

@shainaraskas
Copy link
Copy Markdown
Member

Also to note: big changes are happening in this section right now. This PR definitely can't move forward until #5244 is merged.

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.

2 participants