datastax · aimurphy · Jun 1, 2026 · Jun 1, 2026 · Jun 1, 2026
diff --git a/antora.yml b/antora.yml
@@ -57,8 +57,7 @@ asciidoc:
     dsbulk-migrator: 'DSBulk Migrator'
     cass-migrator: 'Cassandra Data Migrator (CDM)'
     cass-migrator-short: 'CDM'
-    cass-migrator-repo: 'https://github.com/datastax/cassandra-data-migrator'
-    cass-migrator-shield: 'image:https://img.shields.io/github/v/release/datastax/cassandra-data-migrator?label=latest[alt="Latest cassandra-data-migrator release on GitHub",link="{cass-migrator-repo}/packages"]'
+    cass-migrator-repo-url: 'https://github.com/datastax/cassandra-data-migrator'
     sstable-sideloader: '{astra-db} Sideloader'
 
     # Astra role attributes (compare with astra-vector-docs antora.yml)

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
@@ -40,8 +40,7 @@
 * xref:sideloader:troubleshoot-sideloader.adoc[]
 
 .{cass-migrator}
-* xref:ROOT:cassandra-data-migrator.adoc[]
-* {cass-migrator-repo}/releases[{cass-migrator-short} release notes]
+* {cass-migrator-repo-url}[About {cass-migrator}]
 
 .{dsbulk}
 * xref:dsbulk:overview:dsbulk-about.adoc[]
diff --git a/modules/ROOT/pages/cassandra-data-migrator.adoc b/modules/ROOT/pages/cassandra-data-migrator.adoc
diff --git a/modules/ROOT/pages/components.adoc b/modules/ROOT/pages/components.adoc
@@ -163,7 +163,7 @@ It offers extensive functionality and configuration options to support large and
 
 You can use {cass-migrator-short} by itself, with {product-proxy}, or for data validation after using another data migration tool.
 
-For more information, see xref:ROOT:cassandra-data-migrator.adoc[].
+For more information, see the {cass-migrator-repo-url}[{cass-migrator-short} repository].
 
 === {dsbulk}
 

diff --git a/modules/ROOT/pages/faqs.adoc b/modules/ROOT/pages/faqs.adoc
@@ -109,7 +109,7 @@ For any observed problems with {product-proxy} or the other open-source {product
 
 * {product-proxy-repo}[{product-proxy} repository]
 * {product-automation-repo}[{product-automation} repository] (includes {product-automation} and {product-utility})
-* {cass-migrator-repo}[{cass-migrator-short} repository]
+* {cass-migrator-repo-url}[{cass-migrator-short} repository]
 * {dsbulk-repo}[{dsbulk-short} repository]
 
 == Can I contribute to {product-proxy}?

diff --git a/modules/ROOT/pages/feasibility-checklists.adoc b/modules/ROOT/pages/feasibility-checklists.adoc
@@ -153,7 +153,7 @@ By design, a {product-short} migration involves two separate clusters, and it is
 
 If you use non-idempotent operations, {company} recommends adding a reconciliation phase to your migration before and after xref:ROOT:change-read-routing.adoc[Phase 4].
 This allows you an additional opportunity to resolve any data inconsistencies that are produced by non-idempotent operations.
-The xref:ROOT:cassandra-data-migrator.adoc[{cass-migrator-short}] is ideal for detecting and reconciling these types of inconsistencies.
+{cass-migrator-repo-url}[{cass-migrator-short}] is ideal for detecting and reconciling these types of inconsistencies.
 
 However, if your application workloads can tolerate inconsistencies produced by LWTs and non-idempotent operations, you might not need to perform any additional validation or reconciliation steps.
 This depends entirely on your application business logic and requirements.

diff --git a/modules/ROOT/pages/hcd-migration-paths.adoc b/modules/ROOT/pages/hcd-migration-paths.adoc
@@ -25,7 +25,7 @@ During the {product-short} process, you use a xref:ROOT:migrate-and-validate-dat
 
 {company} recommends that you do the following:
 
-* Choose a data migration tool that also includes strong validation capabilities, such as xref:ROOT:cassandra-data-migrator.adoc[{cass-migrator}].
+* Choose a data migration tool that also includes strong validation capabilities, such as {cass-migrator-repo-url}[{cass-migrator}].
 * Be aware of incompatible data types that can fail to migrate from your old cluster.
 
 Data validation tools can identify inconsistencies as missing or mismatched data, but you still need to have a plan to resolve them.

diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
@@ -73,7 +73,7 @@ svg::sideloader:astra-migration-toolkit.svg[role="absolute bottom-1/2 translate-
     <p>{cass-migrator-short} can migrate and validate data between {cass-short}-based clusters, with optional logging and reconciliation support.</p>
 
     <div class="landing-a mt-auto">
-        xref:ROOT:cassandra-data-migrator.adoc[Get started with {cass-migrator-short}]
+        {cass-migrator-repo-url}[Get started with {cass-migrator-short}]
     </div>
 
   </div>

diff --git a/modules/ROOT/pages/migrate-and-validate-data.adoc b/modules/ROOT/pages/migrate-and-validate-data.adoc
@@ -39,7 +39,7 @@ It offers extensive functionality and configuration options to support large and
 
 You can use {cass-migrator-short} alone, with {product-proxy}, or for data validation after using another data migration tool.
 
-For more information, see xref:ROOT:cassandra-data-migrator.adoc[].
+For more information, see the {cass-migrator-repo-url}[{cass-migrator-short} repository].
 
 == {dsbulk}
 

diff --git a/modules/ROOT/pages/troubleshooting-tips.adoc b/modules/ROOT/pages/troubleshooting-tips.adoc
@@ -491,7 +491,7 @@ To report an issue or get additional support, submit an issue in the {product-sh
 
 * {product-proxy-repo}/issues[{product-proxy} repository]
 * {product-automation-repo}/issues[{product-automation} repository] (includes {product-automation} and {product-utility})
-* {cass-migrator-repo}/issues[{cass-migrator-short} repository]
+* {cass-migrator-repo-url}/issues[{cass-migrator-short} repository]
 * {dsbulk-repo}/issues[{dsbulk-short} repository]
 
 [IMPORTANT]

diff --git a/modules/sideloader/pages/prepare-sideloader.adoc b/modules/sideloader/pages/prepare-sideloader.adoc
@@ -161,7 +161,7 @@ If you choose the alternative option, you must modify the commands accordingly f
 * *{sstable-sideloader} doesn't support encrypted data*: If your origin cluster uses xref:6.9@dse:securing:transparent-data-encryption.adoc[{dse-short} Transparent Data Encryption], be aware that {sstable-sideloader} cannot migrate these SSTables.
 +
 If you have a mix of encrypted and unencrypted data, you can use {sstable-sideloader} to migrate the unencrypted data.
-After the initial migration, you can use another strategy to move the encrypted data, such as {cass-migrator-repo}[{cass-migrator}] or a manual export and reupload.
+After the initial migration, you can use another strategy to move the encrypted data, such as {cass-migrator-repo-url}[{cass-migrator}] or a manual export and reupload.
 
 * *{sstable-sideloader} doesn't support secondary indexes*: If you don't remove or replace these in your origin cluster, {sstable-sideloader} ignores these directories when importing the data to your {astra-db} database.
 
@@ -173,7 +173,7 @@ Your administration server must have SSH access to each node in your origin clus
 
 {company} recommends that you install the following additional software on your administration server:
 
-* {cass-migrator-repo}[{cass-migrator-short}] to validate imported data and, with {product-proxy}, reconcile it with the origin cluster.
+* {cass-migrator-repo-url}[{cass-migrator-short}] to validate imported data and, with {product-proxy}, reconcile it with the origin cluster.
 * https://jqlang.github.io/jq/[jq] to format JSON responses from the {astra} {devops-api}.
 The {devops-api} commands in this guide use this tool.
 
@@ -237,7 +237,7 @@ The number of node snapshots that you uploaded to the migration bucket doesn't d
 The success of the import depends primarily on the validity of the schemas and the data in the snapshots.
 
 . After the import, validate the migrated data to ensure that it matches the data in the origin cluster.
-For example, you can xref:ROOT:cassandra-data-migrator.adoc#cdm-validation-steps[run {cass-migrator-short} in validation mode].
+For example, you can {cass-migrator-repo-url}?tab=readme-ov-file#steps-for-data-validation[run {cass-migrator-short} in validation mode].
 
 ==== Migrate multiple nodes to multiple databases
 
@@ -278,7 +278,7 @@ The number of node snapshots that you uploaded to the migration bucket doesn't d
 The success of the import depends primarily on the validity of the schemas and the data in the snapshots.\
 
 . After the import, validate the migrated data to ensure that it matches the data in the origin cluster.
-For example, you can xref:ROOT:cassandra-data-migrator.adoc#cdm-validation-steps[run {cass-migrator-short} in validation mode].
+For example, you can {cass-migrator-repo-url}?tab=readme-ov-file#steps-for-data-validation[run {cass-migrator-short} in validation mode].
 
 === Multiple migrations to the same database
 
@@ -297,7 +297,7 @@ For example, if you have 10 migration IDs for the same database, you must run 10
 Each import must completely finish before starting the next import.
 
 After all of the imports are complete, validate the migrated data in your target database to ensure that it matches the data in the origin cluster.
-For example, you can xref:ROOT:cassandra-data-migrator.adoc#cdm-validation-steps[run {cass-migrator-short} in validation mode].
+For example, you can {cass-migrator-repo-url}?tab=readme-ov-file#steps-for-data-validation[run {cass-migrator-short} in validation mode].
 
 == Next steps
 

diff --git a/modules/sideloader/pages/sideloader-overview.adoc b/modules/sideloader/pages/sideloader-overview.adoc
@@ -4,7 +4,7 @@
 
 {sstable-sideloader} is a service running in {astra-db} that directly imports data from snapshot backups that you've uploaded to {astra-db} from an existing {cass-reg}, {dse}, or {hcd} cluster.
 
-Because it imports data directly, {sstable-sideloader} can offer several advantages over CQL-based tools like xref:dsbulk:overview:dsbulk-about.adoc[{dsbulk}] and xref:ROOT:cassandra-data-migrator.adoc[{cass-migrator}], including faster, more cost-effective data loading, and minimal performance impacts on your origin cluster and target database.
+Because it imports data directly, {sstable-sideloader} can offer several advantages over CQL-based tools like xref:dsbulk:overview:dsbulk-about.adoc[{dsbulk}] and {cass-migrator-repo-url}[{cass-migrator}], including faster, more cost-effective data loading, and minimal performance impacts on your origin cluster and target database.
 
 == {sstable-sideloader} concepts
 

diff --git a/modules/sideloader/partials/validate.adoc b/modules/sideloader/partials/validate.adoc
@@ -1,4 +1,4 @@
 After the migration is complete, you can query the migrated data using the xref:astra-db-serverless:cql:develop-with-cql.adoc#connect-to-the-cql-shell[{cql-shell}] (`cqlsh`) or xref:astra-db-serverless:api-reference:row-methods/find-many.adoc[{data-api}].
 
-You can xref:ROOT:cassandra-data-migrator.adoc#cdm-validation-steps[run {cass-migrator-short} in validation mode] for more thorough validation.
+You can {cass-migrator-repo-url}?tab=readme-ov-file#steps-for-data-validation[run {cass-migrator-short} in validation mode] for more thorough validation.
 {cass-migrator-short} also offers an AutoCorrect mode to reconcile any differences that it detects.