diff --git a/Cloud-Tier.md b/Cloud-Tier.md
index a280d83..13b65ae 100644
--- a/Cloud-Tier.md
+++ b/Cloud-Tier.md
@@ -145,4 +145,4 @@ Or you can run the `weed shell` periodically in some cron job:
 echo "lock;volume.tier.upload -dest s3 -fullPercent=95 -quietFor=1h;unlock" | weed shell
 ```
 
-> **Legacy note:** Previously, this was configured in `master.toml` under `[master.maintenance]`. That mechanism is skipped when an admin server is connected. New deployments should use the admin script plugin worker instead.
+> **Legacy note:** Previously, this was configured in `master.toml` under `[master.maintenance]`. That mechanism is skipped when an admin server is connected. New deployments should use the admin script plugin worker instead. See [[Migrate Maintenance Scripts to Admin Script Plugin]] for details.
diff --git a/Erasure-Coding-for-warm-storage.md b/Erasure-Coding-for-warm-storage.md
index 9bed2ab..10ddcd2 100644
--- a/Erasure-Coding-for-warm-storage.md
+++ b/Erasure-Coding-for-warm-storage.md
@@ -43,7 +43,7 @@ weed admin -master=localhost:9333
 weed worker -admin=localhost:23646
 ```
 
-The `erasure_coding` plugin worker automatically detects volumes that are candidates for EC encoding and executes the encoding. It is enabled by default and configurable from the admin UI at `/plugin`.
+The `erasure_coding` plugin worker automatically detects volumes that are candidates for EC encoding and executes the encoding. It is enabled by default and configurable from the admin UI at `/plugin`. If you are migrating from `master.toml` maintenance scripts, see [[Migrate Maintenance Scripts to Admin Script Plugin]].
 
 ### Detection Thresholds
 
diff --git a/Volume-Management.md b/Volume-Management.md
index 8495cbb..8fade48 100644
--- a/Volume-Management.md
+++ b/Volume-Management.md
@@ -31,7 +31,7 @@ Erasure coding (previously `ec.encode`) is handled by a dedicated **`erasure_cod
 
 See the [[Worker]] page for more details on `weed worker` options and capabilities.
 
-> **Legacy note:** Previously, maintenance scripts were configured in `master.toml` under `[master.maintenance]`. That mechanism still exists as a fallback but is automatically skipped when an admin server is connected. New deployments should use the admin script plugin worker instead.
+> **Legacy note:** Previously, maintenance scripts were configured in `master.toml` under `[master.maintenance]`. That mechanism still exists as a fallback but is automatically skipped when an admin server is connected. New deployments should use the admin script plugin worker instead. See [[Migrate Maintenance Scripts to Admin Script Plugin]] for a step-by-step migration guide.
 
 ## Fix missing volumes
 When running large clusters, it is common that some volume servers are down. If a volume is replicated and one replica is missing, the volume will be marked as readonly.
diff --git a/Worker.md b/Worker.md
index 06cfa81..7562369 100644
--- a/Worker.md
+++ b/Worker.md
@@ -274,8 +274,9 @@ Workers log important events:
 
 ## See Also
 
+- [[Migrate Maintenance Scripts to Admin Script Plugin]] — migration guide from `master.toml` maintenance scripts
 - [SeaweedFS Architecture](https://github.com/seaweedfs/seaweedfs/wiki/SeaweedFS-Architecture)
 - [Maintenance Operations](https://github.com/seaweedfs/seaweedfs/wiki/Maintenance)
 - [Security Configuration](https://github.com/seaweedfs/seaweedfs/wiki/Security-Configuration)
 - [Erasure Coding](https://github.com/seaweedfs/seaweedfs/wiki/Erasure-Coding)
-- [Remote Storage](https://github.com/seaweedfs/seaweedfs/wiki/Remote-Storage) 
\ No newline at end of file
+- [Remote Storage](https://github.com/seaweedfs/seaweedfs/wiki/Remote-Storage)
\ No newline at end of file