MOVEit Automation - Can tasks be exported and imported between two systems of different software versions or configurations? - Progress Community

Loading

Skip to Main Content

MOVEit Automation - Can tasks be exported and imported between two systems of different software versions or configurations?

Unexpected issues can occur in the export and import processes for different systems on different versions or with configuration components that have different IDs and details.

Sep 19, 2025
Knowledge

Title

MOVEit Automation - Can tasks be exported and imported between two systems of different software versions or configurations?

URL Name

moveit-automation-can-i-export-and-import-tasks-between-two-systems-of-different-software-versions

Article Number

000203846

Environment

Product: MOVEit Automation Version: All Supported Versions OS: All Supported Platforms

Question/Problem Description

Can admins export and import tasks between two systems of different software versions?
Why is a task import erroring with "The name already exists" when this environment does not have a task with a name that already exists?

When exporting a task from a newer version to an older version, the SSH client key fails to be imported.

Steps to Reproduce

Clarifying Information

Error Message

In the MOVEitC logs: LogCmd: cfgsec_update script 381650186 Custom Script Name err=2850 This name already exists. user=(a local user) IP=127.0.0.1 MOVEit Central Admin 9.6.0.454

Defect Number

Enhancement Number

Cause

The cause of import issues between systems of different versions or configurations is usually that the Host, Script, Task or other component IDs may not match up. The import process compares the IDs of the components to determine if the imported task is referencing something that already exists in the system. If two components have the same name but different IDs, Automation will not overwrite the existing component in it's configuration and will instead error.

Resolution

The best practice is to export/import tasks between systems of the same version and from a consistent Source environment (e.g. a Development or a Test environment) into a consistent Destination environment (e.g. Production).

Performing this operation between different versions can potentially introduce unexpected behaviors. It is not supported to export from a newer version and to import into an older version.

Workaround

Rewrite the task or the component into the new destination environment manually. This will assign a new ID to the components, and this will cause issues for updating the components with an import process in the future, as Automation will flag the name as "The Name already exists."

Administrators may also strip the Source task from the offending components (e.g. a particular script) and reimport the task to the Destination. Then replace the stripped componenets manually.

Notes

Keyword Phrase

Last Modified Date

9/19/2025 4:39 PM

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

MOVEit Automation - Can tasks be exported and imported between two systems of different software versions or configurations? - Progress Community