SAP PI Migration Strategy Steps:

1. Install fresh SAP PO 7.5 system.

2. Establish transport path from PI 7.4 DEV to SAP PO 7.5.
3. Copy ESR objects directly from PI 7.4 DEV to SAP PO 7.5 DEV.
4. Code Retrofitting from PI DEV to PO DEV.
5. Build 3 new instances for PO Single Stack – DEV, QA & PROD.
6. Establish transport path from PO 7.5 DEV -> QA -> PROD
7. Stop the Development in PI 7.4 and continue to use in PO Single Stack.
8. Finish all the code retrofitting from SAP PI 7.4 to SAP PO 7.5.
9. Demise the SAP PI 7.4 Landscape.

ESR objects directly from SAP PI 7.4 DEV to SAP PO 7.5.

10. The good thing about this migration is that we can directly transport the ESR objects from
SAP PI 7.4 to SAP PO 7.5. Obviously, the ccBPM will not copied as it is not supported by SAP
PO Single stack.
11. We need to recreate the ccBPM to NW BPM using the NWDS Process Components and
configure it.
12. For now, the Service Interface, Mappings, External Definitions and rest of the component of
Software component will be copied from Dual Stack to Single Stack. This is awesome! Save
tons of effort.
ID Objects Migration

Configuration
This is used to configure the Systems that are used in the integration and the Renaming rules
that you want to use to rename the objects like Communication Channels, Business
Components, Party and Routing Expressions etc.
Channel Migration
Used for migrating the communication channels.
The migration is being done in each of the above cases.

Scenario Migration
The complete Configuration Scenario Migration is done based on the Sender Agreement
(Receiver Determination if a Sender Agreement doesn’t exists as in the case of IDOC or PROXY).
The tool gets all the objects of the complete configuration scenario by traversing through the
Sender Agreement (Receiver Determination) till the Receiver Agreement of the respective
configuration scenario.
Once you enter Scenario Migration, you will get the below screen in which you find the
corresponding steps to be carried out.
In System Selection, you need to select the source system (in which you have all your classical
dual stack based configuration objects) and the target system (in which you want to create the
ICO objects for the respective source ID objects).
After providing the details, you move on to Scenario Selection where you need to select a
Sender Agreement / Receiver Agreement (individually or all that exist in a particular
configuration scenario). After migration, the respective IDOC AAE and the SOAP AAE will be
created automatically.
Once you move on to the next option, Scenario Matcher, the tool validates whether all the
involved objects can be migrated to an ICO in the target system.
Next is the Preview and Renaming. Here you can preview all the corresponding objects. You
can rename the objects if you want using the renaming rules that we create as part of the
Configuration migration. You can also check the adapter engine for the communication
channels as part of this task. And as a result, all the ABAP based receiver communication
channels will be transformed to JAVA based communication channels (ABAP IDoc to JAVA IDoc,
ABAP XI to JAVA SOAP and ABAP HTTP to JAVA HTTP).
And finally, Object Creation. This creates all the objects and will be associated to a change list.
You can view this change list in the target system’s integration Directory and can activate the
same.
Configuration Migration
Configuration Migration is used to configure the systems that can be used as the source
systems (you can select the available systems or you can add manually) and also to create any
renaming rules for renaming the objects like Communication channels, Business components,
Party, and Routing expressions.
Renaming the business systems still depend on the transport targets that were defined in the
SLD.
Channel Migration
We go for this option when we want to migrate many channels from one system to another.

Populate the source and destination system details and move on to the next step.
Choose all the communication channels that you want to migrate. And click on Next.
In the Object Creation, you will confirm to create the objects in the target system. All the
objects will be created and associated with a change list in the target system. Log into the
target system, change the details and activate them.

After completion successful testing’s we can move those objects from SAP PO 7.5 DEV to PO 7.5
QA -> PRD