diff --git a/atvm/docs/automation/guide.md b/atvm/docs/automation/guide.md
index 5888f75..4c344a0 100644
--- a/atvm/docs/automation/guide.md
+++ b/atvm/docs/automation/guide.md
@@ -34,7 +34,8 @@ Run ATVM CMC automation tests on the designated automation VM without unintended
 - Always include `--test_partition` on `cmc-templates.py` commands unless the operator explicitly asks not to.
 - Default plugin-bearing templates to `--use_specified_plugin iscsi` unless the operator explicitly requests a different plugin.
 - Do not add plugin or integration-type arguments to `cmc-systemOS`; that template should be planned without `--use_specified_plugin`, without `--integration_type`, and without watcher integration/plugin metadata.
-- For `cmc-migrateops-compute-migration` to VMware, default to `--vm_platforms vmware` and `--set_static_ip_dest` unless the operator explicitly says otherwise.
+- For `cmc-migrateops-compute-migration`, default to `--set_static_ip_dest` unless the operator explicitly says otherwise.
+- For `cmc-migrateops-compute-migration` to VMware, default to `--vm_platforms vmware` unless the operator explicitly says otherwise.
 - For `cmc-reboot`, treat `--use_specified_plugin both` as an exception case that requires an extra confirmation.
 - When `cmc-reboot` is planned with `--use_specified_plugin both`, warn that FC+iSCSI together may hit a "chicken before the egg" timing problem where iSCSI disks are not attached before mTDI / CMC services start.
 - For `cmc-reboot`, prefer `--use_specified_plugin fc` or `--use_specified_plugin iscsi` unless the operator explicitly reconfirms that `both` is really intended after seeing that warning.
@@ -174,6 +175,10 @@ python3 ./run-sorry-cypress.py --config_file <config-file> --build_name <hyphena
   - `--specify_vms <vm1> <vm2> ...`
 - Compute migrateops platform:
   - `--vm_platforms vmware|ovirt|openshift|proxmox`
+- Default compute migrateops options:
+  - `--ignore_force_shutdown`
+  - `--test_partition`
+  - `--set_static_ip_dest`
 - Default compute migrateops vmware options:
   - `--ignore_force_shutdown --vm_platforms vmware --test_partition --set_static_ip_dest`
 
diff --git a/atvm/docs/automation/run-learnings.md b/atvm/docs/automation/run-learnings.md
index 6737d96..be5864f 100644
--- a/atvm/docs/automation/run-learnings.md
+++ b/atvm/docs/automation/run-learnings.md
@@ -19,6 +19,13 @@ This file stores run-specific examples only when a run produced a new learning r
   - Default to watcher-backed launch using the combined `start-atvm-run.sh` wrapper unless the operator explicitly asks to run without watcher.
   - After command execution, report the exact executed `cmc-templates.py` and `run-sorry-cypress.py` command strings in the response.
 
+## Run Learning: 2026-05-07 (Default ATVM compute migrateops runs to set destination static IP)
+- Observed requirement:
+  - ATVM compute migrateops runs should default to enabling destination static IP handling to avoid status-check/parser mismatches and keep destination addressing consistent post-cutover.
+- Action for future runs:
+  - For `cmc-migrateops-compute-migration`, include `--set_static_ip_dest` by default unless the operator explicitly asks not to.
+  - Keep platform selection (`--vm_platforms ...`) based on the operator request while retaining this static-IP default.
+
 ## Run Learning: 2026-05-02 (Do not reuse the previous controller status check for a new ATVM request)
 - Observed failure mode:
   - A later ATVM run request was blocked because the assistant reused the immediately previous controller status result instead of performing a fresh live running-state check at request time.