Run Command Flags.


Table of Contents



Overview

This article describes the key sf sfdmu run flags referenced in migration notes for the current engine line.

diagnostic

Flag: --diagnostic

Enables extended diagnostic logging for a run and writes additional run snapshot details to the log output.

For update/upsert troubleshooting, diagnostic output now includes expanded skip details (same-data skips, no-match skips, and other skip reasons).

In diagnostic mode, this is also written as a dedicated line in the .log file: [diagnostic] update skipped summary: ....

anonymise

Flag: --anonymise

Enables anonymization for sensitive values in .log files by replacing values with deterministic per-run hash tokens (for example, accessToken<ABCDEF12AB34CD56> and path<11F2AA55CC77EE99>).

Use this flag together with --diagnostic before sharing logs.

For the complete masked/non-masked list, see: /full-documentation/reports/the-execution-log#what-is-masked-and-what-is-not

filelog

Flag: --filelog

Controls whether a .log file is written (1) or skipped (0).

apiversion

Flag: --apiversion

Forces a specific Salesforce API version for the current run.

If --apiversion is not provided and apiVersion is not set in export.json, SFDMU auto-detects the default API version:

  • org -> org: lower value of max source API version and max target API version
  • org -> csvfile or csvfile -> org: max API version supported by that org

path

Flag: --path

Sets the base working directory for the run.

By default, SFDMU expects export.json in this directory. Runtime folders and relative resources are also resolved from this base directory.

file

Flag: --file

Sets an explicit export.json file to execute.

  • Relative values are resolved against --path.
  • Absolute values are used as-is.
  • Other runtime folders and relative resources still use --path as the base directory.

In diagnostic mode, the .log file includes the resolved export.json path. If this path differs from --path, an additional diagnostic note is written.

failonwarning

Flag: --failonwarning

Treats any warning as an error. On the first warning, SFDMU stops execution and returns exit code 8 (WARNING_AS_ERROR).

verbose

Flag: --verbose

Legacy compatibility flag. In the current engine, it does not change runtime behavior.

concise

Flag: --concise

Legacy compatibility flag. In the current engine, it does not change runtime behavior.

usesf

Flag: --usesf

Legacy compatibility flag. In the current engine, it does not change runtime behavior.

Related Articles

Last updated on 21st Feb 2026