webMethods to Workato Migration

A webMethods to Workato migration is the rebuild of webMethods integrations as Workato recipes, followed by the retirement of the webMethods estate. The migration replaces flow services, Java services, adapters and Universal Messaging destinations with Workato recipes, connectors and Event Streams.

webMethods components map to Workato equivalents. The table below shows the main mappings:

A migration is a redesign, not a line-by-line translation.

Co Valere migrates 5 webMethods products to Workato: Integration Server, Trading Networks, Universal Messaging, Broker and API Gateway.

The products migrate as follows:

• Integration Server. Flow services, triggers and scheduled tasks are rebuilt as recipes with recipe-level error handling and retries.
• Trading Networks. Partner exchange moves to Workato EDI, which is powered by Orderful and exchanges X12, JSON, XML and CSV files. Workato's EDI tools parse and generate X12, EDIFACT and HL7 inside recipes.
• Universal Messaging. Topics and queues move to Workato Event Streams topics.
• Broker. Broker has been deprecated since webMethods 10.2, according to Software AG documentation. Broker clients move straight to Event Streams, without an interim step through Universal Messaging.
• API Gateway. API definitions move to the Workato API Platform as API recipes, or as API proxies in front of APIs that stay where they are.

webMethods support depends on the version. The dates are:

• webMethods 10.11 standard support ended on 31 October 2024, according to IBM.
• webMethods 10.15 standard support ends on 31 October 2027, according to IBM. Initial extended support ends on 31 October 2028.
• webMethods 10.15 is the last release that supports AIX and z/Linux, according to Software AG.

Organisations on webMethods 10.15 or earlier face a choice between 2 options: upgrade to webMethods 11.1 or later, or migrate off webMethods. An upgrade keeps the webMethods licence and skills model in place. A migration to Workato retires both.

A webMethods to Workato migration takes 8 weeks to 18 months, depending on the number of services and trading partners in scope. Integration count drives duration more than any other factor.

The table below shows typical durations by estate size:

Three factors extend a webMethods migration. These are large Java service libraries, B2B trading partners that must re-test their connections and mainframe adapters. Workato EDI separates TEST and LIVE streams, so partners test on the new platform before production traffic moves. Assessment identifies all 3 factors before the rebuild plan is fixed.

A webMethods to Workato migration costs between £30,000 and £750,000 (about $38,000 to $950,000) in services, depending on estate size and complexity. Workato licences are additional.

The table below shows typical services cost ranges:

IBM webMethods Hybrid Integration uses transaction-based consumption pricing, according to IBM. Workato's billing combines a platform edition with usage measured in Workato credits. Retired webMethods licences and servers typically pay back the migration in 6 to 24 months.

A webMethods migration has 6 stages: assess, map, rebuild, test, cut over and decommission. The stages follow the 3 phases of Co Valere's ACT framework: Assess & Align, Construct & Coordinate and Transition & Transform.

The 6 stages run in this order:

1. Assess. Export the webMethods estate inventory: packages, services, triggers, adapters, Trading Networks partners, schedules, message volumes and owners.
2. Map. Map each package to a Workato design and give it 1 of 3 decisions: rebuild, consolidate or retire.
3. Rebuild. Build recipes, connections, EDI flows, API collections and Event Streams topics to agreed design standards.
4. Test. Compare webMethods and Workato outputs on the same inputs, then run performance tests at peak volumes.
5. Cut over. Move traffic in waves of 20 to 50 integrations, with parallel running and a rollback plan for critical flows.
6. Decommission. Shut down Integration Server, Universal Messaging and Trading Networks instances, then end webMethods licences.

Each main migration risk has a specific control. The table below pairs 4 risks with their controls:

Neither Workato nor webMethods is better for every organisation, because each platform is built for a different integration model. webMethods is built for hybrid integration that runs across on-premises, cloud and mainframe systems, with strong B2B capabilities. Workato is built for low-code integration and automation that integration teams and business technologists can build together.

The main facts about each platform are:

• IBM completed its acquisition of webMethods and StreamSets from Software AG on 1 July 2024, according to IBM. IBM paid about €2.13 billion for both businesses.
• IBM made webMethods Hybrid Integration generally available on 16 June 2025, according to IBM. It combines application integration, API management, B2B integration, managed file transfer and event endpoint management.
• Workato has been named a Leader in the Gartner Magic Quadrant for iPaaS for 8 consecutive years, according to Workato's March 2026 announcement.
• Workato connects to 17,000+ apps and builds AI agents in Agent Studio, according to Workato.

The table below compares webMethods and Workato on 5 criteria:

webMethods is the better fit in 4 situations:

• Established IBM B2B hubs. Organisations that run Trading Networks, ActiveTransfer and IBM Sterling keep partner management, file transfer and B2B in one IBM stack.
• Kafka event governance. Organisations that expose Kafka topics to many teams use the event endpoint management in webMethods Hybrid Integration.
• Mainframe integration. Organisations with core systems on IBM Z use webMethods mainframe adapters and IBM's mainframe access.
• Strict on-premises requirements. Organisations that must run all integration inside their own data centres use self-managed webMethods.

Workato is the better fit in 4 other situations:

• B2B on the integration platform. Workato EDI connects trading partners to the same recipes that run internal processes such as order-to-cash.
• SaaS-heavy application estates. Pre-built connectors for applications such as Salesforce, Workday, ServiceNow and NetSuite reduce build effort.
• Business process automation. Recipes automate processes across HR, finance and IT, such as employee onboarding, order-to-cash and IT access requests.
• AI agents on enterprise data. Agent Studio lets AI agents act in business systems through governed recipes. Workato's EDI Genie answers questions on EDI transactions and trading partner health.

Some organisations run both platforms, with webMethods handling mainframe traffic and Workato automating processes and B2B exchange. In Co Valere's view, the right choice follows the estate: the share of mainframe and IBM-hosted traffic against application integration, the skills in the team and the renewal dates of existing licences. An organisation that decides to stay on webMethods can keep it running under Co Valere support and managed services, with day-to-day running, version upgrades and new integrations.

Co Valere runs webMethods migrations with architecture-led assessment, wave-based delivery on Workato and governance from the first wave. Co Valere is Workato's EMEA Delivery Partner of the Year 2025.

Co Valere's integration delivery has produced 3 measurable outcomes:

• A FTSE 250 packaging manufacturer had over 400 undocumented point-to-point integrations across 12 countries. Co Valere reduced the active estate by 60% and now delivers new integrations 3 times faster.
• The same manufacturer eliminated integration-related production incidents in the first 6 months after go-live.
• An NHS Trust with over 8,000 employees automated 12 HR processes on Workato and removed more than 4,000 hours of manual processing per year.

Co Valere starts every webMethods migration with a fixed-scope assessment of 2 to 4 weeks. The assessment produces the inventory, the rebuild plan, the wave plan and a cost range. In Co Valere's view, the webMethods 10.15 end-of-support date in October 2027 is the most useful forcing event for a migration. That date fixes the business case and the deadline at the same time.