Your PI/PO landscape, rebuilt for BTP.
PI/PO is being retired. CodeForge inventories every interface, documents what it actually does, and migrates it to Integration Suite — proven against its original behavior before anything deploys.
PI/PO reaches end of mainstream maintenance in 2027, end of full support in 2030. 15,000+ enterprises are still running it today.
The harder problem usually isn't migration — it's that nobody has a reliable inventory of what's actually running. Interfaces built a decade ago keep working right up until someone has to change them. CodeForge starts by making that landscape visible.
How it works
Four stages, one interface at a time.
Each stage runs against your own landscape and your own BTP tenant. Nothing moves to the next stage on its own — a KloudData architect decides, per interface.
Read, document, and score
Parses every ICO in your Integration Directory export — XML, Java, Groovy, XSLT — and builds a complete inventory: what system it connects, what triggers it, and what its mapping does, documented in plain language even for interfaces nobody currently maintains.
Migrate the straightforward cases
For deploy-ready interfaces, CodeForge generates a complete Integration Suite iFlow. For complex ones, it produces an architecture blueprint and an annotated skeleton for a KloudData architect instead.
Prove it before it ships
Diffs every mapping step against what the new iFlow actually implements, then classifies each gap in plain English — even when old and new field names share no words at all.
Ship it to BTP
Uploads and deploys one reviewed interface at a time to your Integration Suite tenant, then confirms it's running before moving to the next.
What you get
A full inventory, not just a migration.
Before anything is generated, tested, or deployed, you have a document trail for the entire landscape — including the interfaces nobody has looked at in years.
- Per-interface documentation. What system it talks to, what triggers it, and what its mapping logic actually does — in plain language, not just XML.
- Dependency mapping. Which interfaces share adapters, mappings, or downstream systems, so a change in one doesn't surprise you in another.
- Complexity scoring. A consistent, defensible score per interface, so prioritization is based on evidence rather than institutional memory.
- An audit-ready record. Every interface's original behavior, its migration decision, and its review sign-off, in one place.
- Coverage for the undocumented. Interfaces built years ago by people no longer at the company are documented exactly like anything built last quarter.
- A prioritized plan. A tiered view of what can migrate on its own and what needs an architect first, before you commit to a timeline.
Ready to see your own PI/PO landscape?
Talk to KloudData about scoping an assessment of your Integration Directory export.
Talk to an Expert