Lesson 4 of 6
What does not migrate
10 min
Listen to this lesson
The migration tool covers patterns, not programs. Whatever a PO scenario does outside the supported components lands on a developer's desk: at Contoso that is the move 8 list (same function, built by hand) and the rebuild 6 list (new design), plus manual adjustments inside many keep and adapt flows. SAP documents the gaps in "Known Limitations of Migration Tooling". This lesson turns that page into a work list.
The gap list
| PO construct | What the tool does | What you build in Cloud Integration |
|---|---|---|
| Custom adapter module | Not imported | Re-implement the logic in a Groovy or JavaScript script step, or with standard flow steps |
| Standard adapter module | Not imported automatically | Equivalent flow steps; SAP points to a released community package that offers some modules as Groovy scripts |
| Java mapping | Converted by the Integration Content Migration Agent, or wrapped in a Groovy script | Review and test the generated script; rewrite complex mappings |
| ccBPM or BPM, N:1 and M:N mappings | Not supported; Migration Assessment only identifies the process | Redesign: aggregation, JMS queues, or a new process design |
| 1:N multi-mapping | Mapping imported, splitting not done | Add the split yourself; SAP offers pipeline templates for one-to-many |
| Sync-async bridge | Not supported | Redesign the message correlation |
| RFC or JDBC lookup, sender and receiver functions, adapter-specific attributes in a mapping | Not supported or not carried over | Headers and properties set by a Content Modifier or script; lookups as scripts, XSLT or a separate call |
| Fault messages | Not available | An Exception Subprocess that reproduces the error behavior |
| Exactly Once In Order | Adapter migrated, ordering not preserved | A JMS queue with access type Exclusive |
| Schema validation | Not migrated | An XML Validator step |
| File content conversion | XSDs not migrated; fixed-length fields not supported | Upload the XSD and configure the converter; fixed-length files need another design |
| REST receiver with path variables | Becomes an HTTP adapter that fails | Build the URL from a property or the CamelHttpUri header |
| JDBC sender that selects and updates in one transaction | Not supported | Redesign at the database, for example stored procedures with status flags |
Condensed from SAP Help's Known Limitations of Migration Tooling. Recheck the page before each wave; the list changes as SAP extends the tool.
Receiver determination has its own entries. Extended receiver determination with several operations migrates only partly; with receiver wildcards and agreements it isn't supported. A receiver agreement with a wildcard, where an XPath expression decides the receiver, isn't migrated. For "Maintain Order at Runtime", single-receiver scenarios migrate but XPath interface conditions are skipped and must be added by hand.
- Is every component on SAP's supported list?Yes → tool, then the post-migration checks · No → continue
- Is the gap a documented manual fix (EOIO, fault message, schema validation, timer)?Yes → tool plus a listed adjustment · No → continue
- Is the gap custom code (adapter module, multi-class Java mapping, custom adapter)?Yes → move by hand, re-implement as script or flow steps · No → continue
- Is the gap a process design (BPM, N:1, sync-async bridge)?Yes → rebuild with a new design, tested against new expectations
Java mappings and the Integration Content Migration Agent
Cloud Integration can't run PO Java mappings directly. In the wizard's Java Mapping from ESR step, the Integration Content Migration Agent can generate Groovy equivalents. SAP Help sets clear limits. It handles a Java mapping with a single entry class that extends AbstractTransformation, including lookup service calls. It does not handle several classes, external library dependencies, or custom adapter modules. It produces editable Groovy scripts for the Groovy 4.x runtime inside a script collection artifact, plus a lookup integration flow, called through the ProcessDirect adapter, for mappings that make lookups. Java mappings the agent can't convert but that only use functions available in Cloud Integration can be carried over with a Groovy script wrapper.
Status matters here. SAP Help states that the AI features are available only with the Premium and Enhanced editions, are offered as a free promotion until the January 2027 software release, and must be switched on by a tenant administrator in the Artificial Intelligence settings. The Import Method is Create with AI for a first import or Reuse for a script generated earlier. SAP says to verify the AI-generated scripts before you use them, and that is a testing job, not a formality.
Adapter modules, BPM and custom adapters
Adapter modules are the most common reason for a move. A standard module, such as one that changes a payload's encoding, usually becomes a converter, encoder or script step. A custom module is Java code someone wrote for one partner; its logic has to be read, specified and rebuilt as script or flow steps. SAP's roadmap lists an AI agent that converts adapter modules to Groovy as a later 2026 item; as of October 2026 it isn't delivered, so plan module work as manual and check the SAP Road Map Explorer before each wave. Migration Assessment won't help with sizing: it identifies custom modules and custom adapters but doesn't analyze them, so estimate them from the source code. BPM and ccBPM processes get a name at most from the assessment; their logic needs a design session, not a converter.
What would you do?
The agent converted a Java mapping for Lakeside's order response into Groovy. A developer simulated one sample message, saw plausible output, and wants to deploy to CMC_TEST and close the task. What should Priya ask for first?
- Known Limitations of Migration Tooling is your work list; recheck it before every wave.
- Adapter modules, BPM, sync-async bridges and N:1 mappings are built by hand or redesigned.
- The Integration Content Migration Agent converts single-class Java mappings to Groovy; AI output must be reviewed and regression-tested.
- Migration Assessment identifies custom code but doesn't size it; estimate from source.
Check your understanding · not graded
Lesson check
1. What does the migration tool do with a custom adapter module?
2. Which Java mapping can the Integration Content Migration Agent convert?
3. A PO interface uses Exactly Once In Order. What must you add after migration?
4. Why can't Migration Assessment size Contoso's three custom adapter modules?