Consolidating Boomi integrations onto SAP Integration Suite.
Boomi is an active, independent platform with no end-of-life driver. The reason to move is consolidation: one SAP-native platform instead of two.
The dates that matter.
Last verified 1 November 2026. Dates change; we re-check them before every engagement. All SAP deadlines →
Why move now.
- Consolidating onto one SAP-native platform.
- Using SAP's prebuilt content for SAP-to-SAP and SAP-to-SaaS flows.
- Removing license overlap.
Where it lands on SAP Integration Suite.
Boomi processes and maps → Cloud Integration · SaaS connectors → Open Connectors
Complexity: Medium. For some landscapes, keeping Boomi for specific non-SAP flows makes sense. The assessment tells you which.
The BOND Method, for integration.
Blueprint
Inventory and a decision per interface: move as-is, redesign or retire.
Orchestrate
A pilot wave to prove mappings, security and monitoring.
Navigate
Waves with regression testing; the old platform keeps running in parallel.
Deliver
Cutover, decommission and handover.
A finished move, not a half-way house.
- A full interface inventory.
- A costed wave plan.
- Rebuilt and tested interfaces on Integration Suite.
- Documentation and runbooks.
- The option of managed operations afterwards.
Count your interfaces before you commit.
A fixed-price Integration Landscape Assessment gives you the inventory, the risks and a costed wave plan.