diff --git a/src/content/docs/merge-queue/migrate-partitions-to-scopes.mdx b/src/content/docs/merge-queue/migrate-partitions-to-scopes.mdx
index 29588ecfc5..319751b80f 100644
--- a/src/content/docs/merge-queue/migrate-partitions-to-scopes.mdx
+++ b/src/content/docs/merge-queue/migrate-partitions-to-scopes.mdx
@@ -1,12 +1,16 @@
 ---
 title: Migrate from Partition Rules to Scopes
-description: Step-by-step guide to replace the deprecated partition_rules with scopes and scope-aware CI.
+description: Step-by-step guide to replace partition_rules, which Mergify no longer supports, with scopes and scope-aware CI.
 ---
 
-`partition_rules` are deprecated and will be removed in a future release. This
-guide walks you through replacing them with **scopes**, a more powerful system
-that integrates with your CI and unlocks smarter batching, parallel merge
-queues, and monorepo-aware workflows.
+`partition_rules` are no longer part of the Mergify configuration. A file that
+still declares them is not rejected, but Mergify ignores the section: the queue
+stops splitting into partition lanes, and Mergify opens an automatic migration
+pull request that strips it out.
+
+This guide walks you through replacing partitions with **scopes**, a system that
+integrates with your CI and unlocks smarter batching, parallel merge queues, and
+monorepo-aware workflows.
 
 ## Why Migrate?
 
@@ -176,6 +180,9 @@ Delete the entire `partition_rules` section from `.mergify.yml`. If you
 referenced `partition-name` or `current-partition-name` in your
 `pull_request_rules` conditions, remove those conditions. They no longer apply.
 
+If Mergify has already opened an automatic migration pull request for your
+repository, merging it does this step for you.
+
 ### 4. Enable parallel mode
 
 With partitions, independent lanes ran in parallel by design. With scopes, you
diff --git a/src/content/docs/merge-queue/queue-modes.mdx b/src/content/docs/merge-queue/queue-modes.mdx
index 594166b51f..53ef64497b 100644
--- a/src/content/docs/merge-queue/queue-modes.mdx
+++ b/src/content/docs/merge-queue/queue-modes.mdx
@@ -487,7 +487,8 @@ aren't available depending on the mode:
   independent, so a passing batch can't vouch for any other. It works in serial and parallel modes,
   where a passing batch vouches for the earlier changes it was tested on top of.
 
-- **`partition_rules` are not supported.** Partitions rely on serial ordering; use scopes instead.
+Independently of the mode, `partition_rules` are no longer part of the configuration: use scopes
+instead. See [Migrate from Partition Rules to Scopes](/merge-queue/migrate-partitions-to-scopes).
 
 ## Next Steps