Troubleshoot import warnings and errors
- Last Updated: August 13, 2026
- 1 minute read
- Automate MFT
- Documentation
Automate MFT reports warnings and errors during the import process.
During validation, Automate MFT analyzes the exported MOVEit Automation task and identifies any issues, configuration differences, or unsupported functionality that may affect the imported task. Validation messages are classified as either warnings or errors. Warnings identify configuration that requires review. Blocking errors prevent the task from being imported.
The following table describes some common warnings and errors, their causes, and recommended actions.
| Warning or error | What it means | Recommended action |
|---|---|---|
|
The imported schedule was converted to UTC because Automate MFT cannot determine the time zone used by the MOVEit Automation server. |
Review and configure every imported schedule. If the MOVEit Automation server was not using UTC, update the schedule Time Zone field to match the original server time zone and verify the intended run times. |
|
MOVEit Automation stores only the SSH host key fingerprint, while Automate MFT requires the full host public key. |
Configure the host public key manually on the imported endpoint before using the connection. |
|
A custom MOVEit Automation script could not be imported and was replaced with a comment in the task. |
Review the comment, recreate the script logic manually in Automate MFT, and validate the task before use. |
|
A secure MOVEit Automation parameter was imported as a standard Automate MFT parameter because Automate MFT does not support secure task parameters. Parameters consumed directly by supported PGP, Zip Advanced, Unzip Advanced, or Ignore All Files steps are not added as task parameters. |
Review the parameter value and determine whether additional security controls or configuration changes are required. |
|
A key, certificate, or related secret could not be imported successfully. |
Recreate or import the required key or certificate manually and update any affected authentication methods, endpoints, or task steps. |
|
A MOVEit Automation macro has no equivalent in Automate MFT and could not be translated. |
Review the affected task step and manually update the configuration to achieve the same behavior. |
|
A |
Define the parameter on the imported task or replace the macro with an Automate MFT-supported value. |
|
Automate MFT could not decrypt a specific encrypted value, such as a host credential, proxy password, or secure task parameter. |
Verify the passphrase when applicable and manually configure the affected credential or parameter if necessary. |
|
A credential uses server-key encryption or could not be decrypted because no valid passphrase or override was available. |
Re-export the task from MOVEit Automation using passphrase encryption, and retry the import. |
|
All non-disabled Traditional Source steps use the same Delete Original or Rename Original behavior. Automate MFT automatically added one task-level Update Original step. |
Verify that the task-wide Update Original behavior is appropriate for every source. For Rename, verify the rename mask and overwrite setting. |
|
A host or step-level authentication configuration is unsupported, or a POP3 host cannot be mapped. Affected Source, Destination, or Email steps are replaced with comments. |
Review the comments and determine whether the task remains usable without the unavailable host. If the host is POP3 and the server supports it, consider replacing it with an IMAP endpoint. |
|
A Source or Remove From Cache step was found inside a ForEach or If container, where Automate MFT does not support that step type. The step was replaced with a comment. |
Recreate the step outside of the container and remove the generated comment step for it. |
|
The supplied passphrase could not decrypt the exported task data. |
Verify the export passphrase and retry the import. |
|
The export contains encrypted credentials, but no passphrase was provided during import. |
Restart the import and provide the passphrase used when exporting the task. Server-key exports are not supported; re-export using passphrase encryption. |
|
The task references keys or certificates that are not included in the exported XML. |
Re-export the task from MOVEit Automation with Export Keys and Certificates enabled. |
|
The exported task is a MOVEit Automation Sync task, which has no equivalent in Automate MFT. |
Recreate the required synchronization workflow manually in Automate MFT. |
|
The task uses a host type that is not supported by Automate MFT, such as AS1, AS2, or AS3. |
Replace the unsupported host type or recreate the workflow manually using supported Automate MFT functionality. POP3 is handled separately as a gracefully blocked host whose affected steps become comments. |
|
The export contains multiple unrelated root tasks, but Automate MFT can import only a single root task. |
Re-export an individual task and import each task separately. |
|
All exported tasks reference one another, so Automate MFT cannot determine a root task. |
Re-export an individual task from MOVEit Automation. |
|
The task contains no source steps, or all source steps became unavailable because they reference unsupported hosts or authentication methods. |
Review the source configuration, resolve unsupported dependencies, and ensure that at least one valid source remains before retrying the import. |
|
A mapped endpoint or authentication method is missing a required value, such as Host, Bucket, Username, KeyCertId, or Authority. |
Correct the source configuration or complete the imported configuration before retrying. |
|
The authentication method type is not supported by the mapped endpoint type. |
Correct the MOVEit Automation authentication configuration and re-export the task. |
|
The import exceeds an Automate MFT limit: 20 schedules, 20 endpoints, 20 authentication methods, 20 KeyCerts, 100 non-comment steps, 10 source steps, or 10 destination steps. |
Reduce the task complexity in MOVEit Automation and retry the import. Derived entities and nested action steps count toward these limits. |
|
A mapped value is invalid, such as an SMTP FromEmail address or an overlong KeyCert passphrase. |
Correct the value in MOVEit Automation or recreate the affected configuration manually. |
|
Traditional Source steps have incompatible Delete/Rename settings, rename masks, or rename-overwrite policies, so one task-wide Update Original step cannot represent them safely. |
Make all non-disabled Source steps use the same compatible configuration and re-export the task.
Uniform Delete or Rename configurations are converted automatically.
Advanced tasks should use an explicit |