How to read this page — SLB runs Boomi (field operations, ~30 processes) and TIBCO (enterprise, ~22 processes) as integration middleware.
Both are being migrated to SAP BTP Integration Suite as part of the S/4HANA transformation.
Complexity determines migration approach: Simple = accelerator-assisted, Medium = template + tuning, Complex = bespoke iFlow build.
T-shirt size is the estimated development effort per process.
Hover over any icon for detail.
Integration Suite Assessment
52 integration processes analysed across 2 legacy platforms · Boomi (Field Ops) + TIBCO (Enterprise) · Target: SAP BTP Integration Suite
Total Integrations
—
Processes across Boomi + TIBCO
Complex (Manual)
—
Require custom iFlow build on BTP
Medium (Partial)
—
Template-based migration with tuning
Simple (Accelerated)
—
Accelerator-assisted automated migration
Total Effort
—
Estimated developer days to BTP iFlow
Complexity by Domain
Integration processes per business domain
Complexity Distribution
Boomi vs TIBCO breakdown
Level of Effort by T-shirt Size
Complex Integrations — BTP Custom Build Required
Bespoke iFlow development required — highest migration effort and risk
Complexity classification guide
Simple
Accelerator-assisted · S or M sizeStandard point-to-point mapping, no scripting. Sierra's migration accelerator handles these automatically.
Medium
Template-based · M or L sizeModerate transformation logic or routing. Pre-built BTP iFlow template used as a starting point with tuning.
Complex
Manual build · L or XL sizeCustom Groovy/Java scripting, multi-step orchestration, or business exception handling. Requires full iFlow development cycle.
Integration Processes — Detailed Assessment
Drill, field service, finance and supply chain integrations · BTP target iFlow mapping
| Process Name | Domain | Platform | Type | Complexity | T-Shirt | Effort (days) | Primary Connector | Scripting | Readiness |
|---|---|---|---|---|---|---|---|---|---|