Before importing tasks, review the source MOVEit Automation environment and the target Automate MFT tenant.

This topic explains how to export an individual MOVEit Automation task and import it into Automate MFT using the import wizard.

During the import process, Automate MFT analyzes the exported MOVEit Automation task and converts supported configuration into Automate MFT entities such as endpoints, authentication methods, schedules, keys, certificates, and task steps. When matching entities already exist in the tenant, Automate MFT reuses them instead of creating duplicates.

Before you begin

Before you migrate a task from MOVEit Automation to Automate MFT, verify the following requirements:
  • You have access to the source MOVEit Automation environment.
  • You have access to the target Automate MFT tenant.
  • Your Automate MFT user account has the Administrator (system) or Editor (system) role.

    Only users assigned the Administrator (system) or Editor (system) role can import tasks. Custom roles cannot import tasks, even if they have equivalent permissions.

  • The Import option is available from the New Task menu on the Tasks page.
  • You have identified the individual MOVEit Automation tasks that you want to migrate.
  • You have reviewed the selected tasks for unsupported dependencies, such as Sync tasks and unsupported host types. For more information on unsupported dependencies, see Review import issues.
Important: Do not enable Auto-Run for an imported task until you have reviewed and tested the task and disabled the equivalent scheduled task in MOVEit Automation. If both tasks run, the same files might be processed more than once.

Supported export type

Automate MFT supports importing individual MOVEit Automation task exports, one-by-one. Export the task from within the task itself by using the task-level Export action.

Automate MFT does not support importing a MOVEit Automation bulk export that contains multiple unrelated root tasks. If an export contains multiple unconnected root tasks, the import fails and Automate MFT displays an error.

If an export contains a root task and referenced child tasks, Automate MFT imports only the selected root task. Referenced child tasks are not imported as separate Automate MFT tasks. Run Task steps or post-run task references are imported as comments where applicable and will need to be manually rectified after import.

The import API can be used for advanced migration scenarios where users want to automate the validation and import of multiple task exports. Even when tasks are imported through the API, each imported task must be reviewed, configured, and tested before production use.