Export Communications Manager instance configuration

ExportInstanceConfiguration.exe is a command-line tool designed to export a single Communications Manager instance configuration into a .zip file. This configuration can be later imported to another Communications Manager instance.

This tool does not support Communications Manager

5.2, 5.3, and 5.4.

The tool can perform configuration export with or without infrastructure.

If exported without infrastructure, configuration contains the following items:
- The dp.ini, dm.ini and itp.cfg configuration files of Communications Manager Core.
- The itprep.ini and pwdblacklist.txt configuration files of Communications Manager Repository.
- The itpmdkapi.ini configuration file of Communications Manager RestAPI.
- The log configuration of the Communications Manager Designer.
- The log configuration of the Communications Manager Composer.
- The custom Communications Manager Core scripts.
- The contents of the Did, Watermarks and Resources subfolders of the Communications Manager Core work folder.
If exported with infrastructure, configuration contains the items above and also the registration information (partner, customer, an so on) of the source Communications Manager instance.

Internal settings (such as internal addresses) will not be transferred by the import/export mechanism. These settings will be removed either by the export, or later by the import.

Before you start

Make sure the account used to run ExportInstanceConfiguration.exe is included in the local Administrators group on the target server.
Check your Communications Manager version. ExportInstanceConfiguration tool supports the Communications Manager product starting from version 5.2.0.

Parameters

To view the list of parameters for ExportInstanceConfiguration.exe, run it without any parameters.

Parameter	Required / Optional	Description
Product!Version	Required if Communications Manager installation is not active	The Communications Manager version to export from. Enter version number in the format Major.Minor Example: Product!Version=2025.3 If omitted, defaults to the currently active Communications Manager installation.
Instance!Number	Required for on-premise installation	The number of the Communications Manager instance to export from. On Docker, this defaults to 1.
Instance!ExportConfigurationFile	Required	The file to write the configuration export to.
Instance!ExportInfrastructure	Required	Boolean flag that specifies whether the configuration is exported with or without infrastructure settings. If set to True, configuration export will include infrastructure settings. If set to False, configuration export will not include infrastructure settings. When exporting from Communications Manager versions earlier than 5.5, it is not possible to add infrastructure to the export. In these cases, the Instance!ExportInfrastructure parameter will not be available.

Notes on usage

To create an export from an older Communications Manager version, use the following procedure:

Open the Software\Tools folder of the Communications Manager 2025.3 installation package and locate the following files:
- ExportInstanceConfiguration.exe
- ExportIsntanceConfiguration.exe.config
- Nlog.config
- All .dll files.
Copy these files to the server on which the old Communications Manager version is installed. All files must be placed in the same folder.
From that folder, run ExportInstanceConfiguration.exe. If creating an export from an older Communications Manager version, some configuration items may not be compatible with newer versions. Such items will be removed from the export. The result is a partial export, which can still be imported, although missing these items.

Check your Communications Manager version. The import tool works only on Communications Manager 5.5.0 version and higher, supporting only configuration export files created with the ExportInstanceConfiguration tool from the version to which you need to import.