Moving from TIBCO BusinessWorks to SAP Integration Suite.
TIBCO is now owned by Cloud Software Group. For SAP-centric landscapes, version retirements and licensing changes are a natural moment to consolidate onto one platform.
The dates that matter.
Last verified 1 November 2026. Dates change; we re-check them before every engagement. All SAP deadlines →
Why move now.
- The shift from perpetual to subscription licensing.
- Version-by-version upgrade pressure.
- A shrinking BusinessWorks 5 skills pool.
- The cost of running a second integration platform alongside SAP.
Where it lands on SAP Integration Suite.
BW processes and mappings → Cloud Integration · EMS/JMS messaging → Event Mesh / Advanced Event Mesh · BusinessConnect EDI → Trading Partner Management and Integration Advisor
Complexity: High. BW process definitions, XPath/XSLT mappings, adapters and messaging all need careful rebuilding and testing.
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.