During import, Automate MFT validates the exported task and reports warnings and errors. Warnings identify configuration that was changed, ignored, partially imported, or requires review. Errors prevent the import from being completed.

Warnings

Warnings identify settings or behavior that require review or adjustment after import. A warning does not necessarily prevent the task from being imported.

Comments: All warnings displayed during the import process are also added to the imported task as one or more warning summary comments. These comments remain available after the import completes and can be reviewed during task validation.

In some cases, Automate MFT cannot import a task step or configuration directly. When this occurs, Automate MFT replaces the unsupported functionality with one or more comments that describe the original configuration and any required manual actions. Review these comments carefully and recreate the required functionality in Automate MFT where necessary

Step-level comments: For selected step-specific warnings, Automate MFT also inserts a comment directly above the affected step. These comments provide additional context about the affected step and identify any configuration that requires manual review or recreation. Not every warning has a separate step-level comment.

Errors

Errors identify issues that prevent Automate MFT from importing the task. If validation contains errors, resolve the reported issues in MOVEit Automation or adjust the task before trying again.

Examples of errors include:
  • The passphrase is missing or incorrect.
  • The export contains a Sync task.
  • The task uses an unsupported AS1, AS2, or AS3 host type.
  • The export contains multiple unconnected root tasks.
  • Missing required endpoint or authentication method fields.
  • A required key or certificate cannot be found, imported, or associated with the required task configuration.
  • Source delete or rename behavior that cannot be safely represented as one task-wide Automate MFT action

Created and reused entities

During import, Automate MFT converts MOVEit Automation configuration into the equivalent Automate MFT entities. Depending on the task configuration, Automate MFT may create new entities or reuse existing entities in the tenant.

For example, a MOVEit Automation host contains both connection information and credentials. In Automate MFT, these concepts are represented separately as endpoints and authentication methods.

When equivalent entities already exist in the Automate MFT tenant, the import process reuses them instead of creating duplicates. Reuse can apply to keys and certificates, authentication methods, endpoints, and schedules.

Note: The import wizard identifies reused entities by name. To inspect a reused entity before completing the import, open the relevant Automate MFT library page in another browser tab and search for the entity name.
Important: Authentication methods and endpoints created in Automate MFT versions prior to version 1.20 will not be reused during import. If an authentication method or endpoint was created manually prior to 1.20, a new entity will be created during import.