PI to CPI migration

PI to CPI migration turns your existing SAP PI/PO content into Cloud Integration artifacts. Figaf Tool reads a PI object, builds the corresponding IFlow, and lets you review the result before anything is created on the target tenant.

Migration is assisted, not automatic. Every flow follows the same arc: choose the object, configure how it should be migrated, run Check to build the target model, read the migration logs, then Migrate — after which the IFlow still has to be configured and deployed. Some constructs are deliberately left for you to finish, so read Supported cases before planning a migration.

Requirements:

  1. All required Agent Systems have been configured (see Agent Configuration to learn how to do that).

  2. Enable PI to CPI migration on Configuration page.

  3. Configure Channel Mapping Templates if default templates don’t match.

  4. Configure Migration license for PI objects which you want to migrate (see Configure Object Licenses for details).

Since 2107 version Figaf Tool supports PI to CPI migration cases. On PI to CPI migration page you can migrate PI Integration object, Operation mapping or B2B.

1. What you can migrate

  • PI Integration objects (ICOs and receiver determinations) into IFlows.

  • Operation mappings, either as their own IFlow or embedded into an existing one as a local process.

  • B2B content, into Trading Partner Management objects — see B2B.

Once an object is migrated you can also hand its test cases to Testing Tool, so the migrated scenario can be compared against the original. That is a separate step, not part of the migration itself.

2. In this section

Get started with PI to CPI migration

The Overview, Migration, Configuration and Channel Mapping Templates pages, and the end-to-end flows for each kind of object.

Supported cases

Which PI scenarios, mappings, conditions and adapters are covered, and what each one produces on the CPI side.

File Content Conversion migration

How File Content Conversion of file channels is reproduced, which channel parameters are carried over and where the result differs from PI.

Wildcard ICO migration

How ICOs with a wildcard (*) sender or receiver are migrated, where their channels come from and what to expect per migration profile.