You can select to migrate endpoints for a specific partner, a list of partners, or all partners. Run the migration tool through the command line interface. The migration process creates endpoints that are associated with specific partners.

For each partner that you specify, the migration tool fetches associated OEM endpoints and their configuration data and creates Informatica Managed File Transfer objects. The migration tool creates Informatica Managed File Transfer resources, connections, and web users in

B2B Data Exchange

and Informatica Managed File Transfer.

An OEM host and mailbox corresponds to a resource in Informatica Managed File Transfer. When the migration tool migrates a host and mailbox combination, the migration tool creates a corresponding resource in Informatica Managed File Transfer. The migration tool migrates mailbox passwords automatically.

For an OEM endpoint that is connected to a server hosted in a partner environment, the migration tool creates an MFT Remote Receive endpoint and an MFT Remote Send endpoint. For an OEM endpoint where the partner connects to the organization server, the migration tool creates an MFT Hosted Receive endpoint and an MFT Hosted Send endpoint.

The Send endpoint is assigned the same name as the original OEM endpoint. The Receive endpoint is provided a name with the format

<prefix>_<original OEM endpoint name>

, where the prefix can be customized in the migration configuration file. The OEM endpoint that has been migrated is renamed in the format

OEM_MFT_<original OEM endpoint name>

. If the migrated OEM outbound endpoint was the default endpoint for an account, the account is updated and the generated send endpoint is designated the default outbound endpoint.

All the common fields for the OEM Managed File Transfer endpoint and the Informatica Managed File Transfer endpoint are copied to the created endpoint without change, for example, read patterns, schedules, and backup options.

An OEM mailbox contains a set of actions that are performed for files to be sent or received. Each OEM Managed File Transfer host and mailbox has a set of properties which can be used to customize file transfer. For example, a native command can be run to post a file transfer (inbound or outbound) by setting the corresponding host property. For Informatica Managed File Transfer endpoints, the endpoints are associated with projects instead that perform actions for files to be sent or received.

The generated Informatica Managed File Transfer endpoints are provided template projects. To support the OEM scenarios, the template projects have corresponding variables that are defined using the values from the OEM Managed File Transfer host and mailbox. Host and mailbox properties are mapped to the corresponding Informatica Managed File Transfer project variables and populated during endpoint migration.