FCC: Migration from webMethods to SAP Integration Suite

Florida Crystals Corporation (FCC) is a leading player in the U.S. sugar processing industry. Its integration estate had grown up around webMethods, a once-standard broker that had started to drift away from the company's cloud strategy and the vendor's own support roadmap.

The integration challenge: an ageing webMethods estate

The on-premise webMethods setup carried more than 450 active interfaces across the enterprise landscape. Two pressures forced the decision. Support standards for the legacy version were tightening, and there was no clean upgrade path from on-premise webMethods to webMethods Cloud. Continuing to invest in the platform would have meant rising maintenance costs without modernising the layer FCC depends on every day.

Migration objective: 450+ interfaces, no business disruption

The brief was specific. Move every active interface to a modern, cloud-native integration platform, keep business operations running through cutover, and align the new architecture with the long-term IT roadmap. Anything that required heavy manual rework or extended downtime was off the table.

The Tarento approach: assessment, platform selection and iVolve

Tarento opened with an in-depth assessment of the existing landscape, future needs and available technology options. After evaluating cloud integration options against FCC's SAP footprint and existing skills base, SAP Integration Suite was selected as the target platform.

The migration itself ran on iVolve, Tarento's proprietary framework for moving legacy integrations onto SAP IS. iVolve accelerates the transformation and applies consistent patterns across every migrated interface. That consistency is what made the volume manageable inside a fixed timeline.

Why SAP Integration Suite was the right fit

Three factors made SAP IS the strongest option. FCC already runs SAP at the core of its ERP estate, so native adapters cut connector complexity. The platform sits on SAP Business Technology Platform, giving the team one environment for integration, extensions and analytics. And SAP's published roadmap removes the support cliff that triggered the project in the first place.

Results: faster delivery, lower cost, full coverage

The programme delivered against every objective set at kick-off:

• 450+ webMethods interfaces migrated to SAP Integration Suite
• Around 30% of the build effort automated through the iVolve framework
• Material reduction in cost, effort and elapsed time compared with a manual rebuild
• A seamless, reliable transition to SAP Cloud Platform

Automation mattered most on the repetitive interface families. Automation took the repetitive work off the team, which let senior engineers focus on the flows that genuinely needed careful design.

Project snapshot

• Team size: 16
• Duration: 15 months
• Technology stack: SAP Integration Suite, ABAP, BASIS, SAP SD, webMethods

Outcome: a scalable integration foundation

FCC ended the programme with more than a like-for-like replacement. The business now runs on an integration layer that scales with cloud workloads, supports event-driven extensions, and aligns with the wider SAP investment. Future work, whether S/4HANA enhancements, analytics pipelines or partner onboarding, plugs into a platform built to grow.

Learn more about iVolve - Tarento’s SAP-certified integration modernization framework