The import process behavior remains the same for a workflow that contains a session that runs a mapping with multiple pipelines. Each mapping name is appended with a number that indicates the order in which mapping needs to run as mentioned in the target load order.

The pipelines with the unsupported transformation or object are imported with broken links in the Model repository. In this case, the number of imported mappings can be less than the total number of pipelines in a PowerCenter mapping based on the target load order. If any pipeline in PowerCenter contains transformations or objects that are not supported in the Model repository, the pipeline is broken with the unconnected objects and it appears within a single mapping in the Model repository.