Introduction
SAP Cloud Integration version 6.82/(8.x→ 8.46), a key capability of the SAP Integration Suite, introduces an innovative solution—Integration Content Migration Agent. This cutting-edge feature is exclusively available to SAP Integration Suite Cloud Integration Premium and Enhanced Editions users in select data centers/regions. For more information on availability of these AI features across SAP BTP regions, see 3463620.
What is the Integration Content Migration Agent?
The Integration Content Migration Agent is an AI-driven tool embedded within the Migration Tool of SAP Integration Suite. Powered by GenAI, it automatically converts SAP Process Integration/Process Orchestration(SAP PI/PO) Java Mappings into Groovy scripts, making them compatible with SAP Cloud Integration (CI).
Why Integration Content Migration Agent?
The Core Problem
SAP PI/PO and SAP Cloud Integration are fundamentally distinct platforms that operate under different architectures and paradigms.
| SAP PI/PO | SAP Cloud Integration |
| Java Mappings (compiled to JAR, executed via Java Mapping API) | No Java Mapping execution support |
| Lookup Service API for adapter calls | No equivalent runtime API in Groovy |
| On-premise, monolithic runtime | Cloud-native, microservices-based runtime |
In SAP PI/PO, Java mapping is a popular mapping type in SAP Process Orchestration, offering flexibility through a Java class that implements the Java Mapping API.
In SAP Cloud Integration (part of SAP Integration Suite), Java mapping cannot run directly in an integration flow. This PI/PO object lack direct equivalents in the Integration Suite.
Core Concept
|
Aspect |
Detail |
|
What it migrates |
Java Mappings (com.sap.aii.mapping.api) from SAP PI/PO |
|
What it produces |
Ready-to-use Groovy scripts stored in Script Collections for integration flows in CPI |
Challenges in Manual Migration
Organizations transitioning from SAP PI/PO to SAP Integration Suite face several obstacles due to the fundamental differences between the two platforms. Key challenges include:
- Extremely labor-intensive: Developers must manually rewrite, test, and validate each individual logic in every Java Mapping.
- Error-prone process: Manual translation increases susceptibility to bugs in logic.
- Costly: Prolonged development time significantly increases expenses and delays cloud adoption.
- Requires dual expertise: Developers must possess a comprehensive understanding of Java mappings for PI/PO and Groovy for Cloud Integration.
| Manual Migration Challenges | Impact |
| Complex conditional logic and Java parsing usages | Difficult to accurately translate without introducing errors |
| Lookup Service calls from mappings | Absence of direct architectural equivalent, requiring major redesign |
| Large quantity of mappings per customer | Prolonged project timelines (weeks to months per project) |
| Retention of core business logic | Heightened risks of functional regression and loss of functionality |
Why GenAI and the Agentic Approach?
The LangGraph framework, which powers the Migration Agent, employs predictable, workflow-driven logic rather than purely autonomous agent reasoning. This ensures consistency and accuracy—critical for enterprise-grade migrations.
Key Benefits of the Migration Agent:
For Integration Developers:
- Significant Time Efficiency: Tasks that can take weeks manually are completed in minutes.
- Lower Skill Barrier: Eliminates the need for mastery of both Java mappings and Groovy.
- Automated Quality Control: Scripts are evaluated for syntax, design guidelines & CleanCore & upgrade readines practices, and Java 17+ compliance before they are delivered.
- Editable Outputs: Generated Groovy scripts remain modifiable, allowing flexibility for developers. Generated scripts are based on groovy script 4.x runtime.
- Preserves Functionality of Lookups: Improves continuity by generating reusable integration flows with the new ProcessDirectService API for handling Lookup Service behavior.
For SAP Customers and Organizations:
- Accelerated Cloud Migration: Minimizes the challenge of Java Mapping conversion, speeding up the transition to SAP Integration Suite.
- Cost-Efficiency: Reduces staff hours dedicated to script migration and testing.
- Modernized Codebase: Converted scripts adhere to CI design guidelines principles, ensuring improved quality over legacy Java Mappings.
- Reusability: Hash-based deduplication prevents redundant migrations, scripts are shared through Script Collections to ensure efficiency.
- Risk Mitigation: Functional equivalence testing during the migration phase ensures businesses retain correct and reliable integration logic.
For SAP Products:
- Streamlined Decommissioning: Breaking adoption barriers for customers on legacy PI/PO platforms enhances overall migration speed to Integration Suite.
- New API Capabilities: The introduction of the ProcessDirectService API benefits all CPI developers, extending CPI’s runtime capability.
- Scalability: Initially geared for single Migration tool, it is designed for future integrations into Mass Migration Tool.
Feature Availability
Access to the Integration Content Migration Agent depends on your SAP Integration Suite service plan. The feature is included in Premium and Enhanced Editions.
Promotional and Commercial Availability:
- AI features will remain free until September 2026 as part of a promotional campaign.
- Availability of this feature depends upon the SAP Integration Suite service plan that you use. For more information about different service plans and their supported feature set, see SAP Note 2903776
- For more details on SAP BTP region compatibility, refer to SAP Note 3463620.
Current Scope and Limitations
Supported:
- Migration of Java Mapping files with a single Java class (entry point) extending the Abstract Transformation class.
- Java mappings based on the lookup service. Lookup Integration flows for external calls associated with Java Mappings. These lookup flows will be generated and activated by the Groovy scripts.
Out of Scope:
- Multiple Java classes with a single entry point, regardless of external dependencies.
- Java classes reliant on external libraries (open source, proprietary, custom, or public libraries).
How to leverage?
In the Artificial Intelligence settings page, of Integration suite tenant you will notice Integration Content Migration Agent. Activate the feature to integrate the Integration content migration agent in the Migration tool. To know more about the SAP PI/PO Migration tool in the cloud integration capability of the integration suite, refer the help documentation
Open the Migration tool, select the integration scenario from the connect SAP Process orchestration system that uses the Java mappings. Applicable patttern will be associated.
After the message mapping and its dependent configurations, you will notice a Java Mapping from ESR page in this wizard. This page will appear if your Integration suite tenant satisfies the Feature Availability section and the integration scenario has a references to the java mappings.
In this page, you have to select the script collection artifact to generate the corresponding groovy script for the java mappings object. If the script collection artifact doesn’t exist, then create by following the help documentation.
In the import method of this wizard page, you will notice “Create with AI” if the script for the java mappings is not generated by AI. Otherwise, Reuse option will be available for reusability instead of creating a similiar/duplicate script via the AI agent.
In the review page, you will notice the envisioned scripts to be created as a parity for the java mappings in the cloud integration for the migrated integration scenario.
On click of the Migrate, the integration scenario and its corresponding dependent objects from the SAP PI/PO system will be migrated to Integration flow along with the dependent artifacts. However, for migrating the Java mappings, AI Agent will be invoked to transform the java mappings to the groovy scripts.
Generated groovy script in the script collection will be automatically referenced in the integration flow, groovy script flow step.
Groovy script generated via the agent will be marked as AI generated script in the script docs.
Important Note:
Unsupported Java mappings will be discovered by the Agent and it will be displayed in the Java Mapping from ESR page of the Migration Tool.
In the future increments, we will start supporting unsupported java mappings. Please refer the upcoming enhancements sections.
How to Maximize the Migration Agent?
Upcoming Enhancements:
- AI-generated scripts will be visually flagged with an AI symbol for differentiation.
- Direct migration of Java Mappings containing
.classfiles into Groovy scripts will be supported. - Improved error handling mechanisms for the failed java mappings for a better visibility and transparency.
- Broader coverage for:
- Multiple Java classes with single entry points.
- Java classes with external library dependencies.
- Migration of custom adapter modules (both sender and receiver) to Groovy scripts.
- Integration within standalone script collection artifact editor for added flexibility.
Summary
The Integration Content Migration Agent acts as an intelligent co-pilot for modernizing the SAP PI/PO objects. Built using advanced AI technologies, it automatically transforms heavily customized Java Mappings into scalable, cloud-native Groovy scripts. By eliminating manual effort, ensuring functional accuracy, and adhering to best practices, this tool enables enterprises to break free from legacy integration barriers and accelerate their journey to cloud adoption.
For more details, visit SAP’s help guide on Integration Content Migration Agent help documentation.
I hope you find the enhancements in this blog post beneficial. If you have any questions or feedback, please leave a comment.
#SAPCHANNEL