Speed.
Move faster from discovery to build preparation. Generate PO reports, ESR summaries, and starter iFlow ZIPs without repeating manual spreadsheet work.
PI/PO to SAP Integration Suite migration
Assess PI/PO migration scope and automate the repeatable work.
POMigrate helps teams reduce repeated manual checking, prepare consistent migration outputs, and see missing mappings, WSDLs, adapters, and other gaps before the project plan becomes unclear.
Expert-led by Yee Loon Khoo, combining SAP integration migration experience with the POMigrate toolset.
Plain version
POMigrate helps automate mass migration operations where automation makes sense.
It does not magically migrate everything.
It is for the parts of migration that are repeated many times: collect evidence, build reports, prepare mappings, generate iFlows, create packages, upload, validate, and track gaps.
If a step can be automated safely, POMigrate tries to automate it. If it needs human decision, it should be shown clearly instead of hidden.
The useful output is not only generated iFlows. It is also the reports and gaps that tell the team what still needs review.
POMigrate helps automate mass PI/PO migration preparation by downloading PO and ESR data, building interface and mapping reports, extracting and enriching message mappings, generating reviewable iFlow ZIPs, creating Integration Suite packages, uploading generated iFlows, building configuration workbooks, applying reviewed configuration plans, checking tenant values, preparing Partner Directory plans, and running validation checks so teams can repeat the work consistently and still see what needs manual review.
Migration outcomes
What changes when the repeated work is handled properly.
Cost.
Reduce effort spent on repetitive migration tasks. Automate interface extraction, report building, readiness checks, and package preparation.
Visibility.
See what is really inside your PI/PO landscape. Consolidate ICO, classic interface, adapter, mapping, WSDL, and function-library details into reviewable reports.
Consistency.
Apply the same migration logic across every interface. Use standard naming, report views, iFlow generation patterns, and Partner Directory planning.
Control.
Keep migration decisions in human hands. Review what to migrate, redesign, retire, or generate before applying changes to SAP Integration Suite.
Feature list
What the tool can do
Download PO design evidence
Download PO interface and directory XML into a local workspace so the migration view starts from actual system evidence.
Download ESR objects
Download operation mappings, message mappings, service-interface WSDLs, message type WSDLs, RFC structures, external definitions, IDoc WSDLs, and function libraries.
Extract ESR mappings and structures
Extract message mappings, WSDLs, RFC structures, external definitions, IDoc structures, XSLT mappings, Java mapping placeholders, and function libraries into a usable local workspace.
Build PO and ESR reports
Build interface, channel, adapter, routing, mapping, WSDL, function library, and final review views into Excel and SQLite reports.
Show mapping readiness
Show which mappings are available, missing, linked to structures, using function libraries, XSLT, Java, or custom logic.
Link WSDLs into mappings
Attach source and target WSDL structure links to extracted message mappings when matching structures are available.
Embed mappings and function libraries
Embed available graphical mappings, XSLT mappings, WSDL files, function libraries, and placeholders into generated iFlow ZIPs.
Inspect adapter templates
Show which adapter patterns are covered by templates and which ones still need manual design or template work.
Generate Sync iFlows
Generate reviewable request-response iFlow ZIPs for suitable PI/PO patterns.
Generate inbound-processing iFlows
Generate PIP01-style inbound-processing iFlow ZIPs for repeatable inbound patterns.
Generate outbound-processing iFlows
Generate PIP07-style outbound-processing iFlow ZIPs for repeatable outbound patterns.
Generate endpoint paths
Generate sender, receiver, and ProcessDirect endpoint paths from interface, adapter, channel, and destination metadata.
Package function library exports
Prepare ESR function library ZIPs and indexes for manual CI handling where direct upload is not automated.
Create Integration Suite packages
Create Cloud Integration design-time packages based on the software components used by the source interfaces.
Upload or recreate generated iFlows
Upload generated iFlow ZIPs by package or iFlow id, with recreate support when a clean artifact refresh is preferred.
Validate uploaded iFlows
Run Cloud Integration validation checks by package, by iFlow id, or across generated packages.
Build iFlow configuration workbooks
Generate reviewable iFlow configuration workbooks from generated ZIPs, adapter metadata, PO channels, and discovered parameters.
Map PO values through rules
Map PO channel attributes and normalized endpoint values into CPI parameters using explicit, reviewable rules.
Apply iFlow configuration plans
Apply frozen configuration plans to deployed iFlows so repeated parameter updates do not need manual CI editing.
Check deployed iFlow configuration
Compare deployed CI parameter values against expected configuration plans to confirm what was actually applied.
Track credential references
Show credential aliases, usernames, key aliases, and authentication methods without copying PO passwords.
Build Partner Directory plans
Prepare reviewable Partner Directory plans for receiver and interface determination, with simple and complex cases separated.
Check and apply Partner Directory plans
Check a frozen Partner Directory plan against the tenant, then apply selected records when reviewed.
Generate repeatable launchers
Generate batch launchers so download, report, build, upload, configuration, validation, and Partner Directory steps can be repeated.
Report ready and pending items
Create interface summary, ready interface, pending interface, embedded mapping, missing mapping, upload, validation, configuration, and generation summary reports.
Outputs
What the team gets
- A practical readiness view from PI/PO evidence to CI tenant output.
- Clear interface inventory for assessment, planning, and migration waves.
- Adapter and channel reports that show what each flow needs.
- Mapping readiness views that separate available assets from gaps.
- ESR structure readiness for WSDL, RFC, IDoc, and external definitions.
- Generated iFlow ZIPs that can be reviewed before upload.
- CI package and upload outputs that show where artifacts were placed.
- Configuration workbooks that show which parameters need attention.
- Frozen apply plans that show what will be changed in CI.
- Configuration check results that show whether tenant values match.
- Validation results that show design-time readiness in CI.
- Partner Directory plans for routing records that need review.
- Ready and pending lists that separate usable output from follow-up work.
- Visible review gaps so uncertainty is not hidden.
Important
What it is not
It is not a one-click migration tool.
It does not replace consultants, developers, testing, or proper design decisions.
Generated iFlows are starting points for review, configuration, validation, and refinement.
Runtime configuration still needs careful review. Carrying values from a production PI/PO system into CPI without checking can move production endpoints, credentials, paths, or other risky values into the new tenant.
Some interfaces should be migrated. Some should be redesigned. Some should be retired. The tool helps make that easier to see.
Who built it
Yee Loon Khoo
I have worked for many years across multiple SAP integration projects, mainly around PI/PO, CPI, SAP Integration Suite, and migration-related work.
POMigrate is my way of turning those years of SAP integration project experience into a practical tool: less repeated checking, less manual rebuild work, and clearer visibility before migration effort is committed.
Contact
Planning a PI/PO to SAP Integration Suite migration?
Start with a clear assessment. What interfaces exist, what is repeatable, what is risky, and what can be generated safely?