Australian Utility Provider Achieves Seamless Migration from SAP BPA to RunMyJobs
Meet the Authors
Key Takeaways
The migration from SAP BPA to RunMyJobs was executed successfully without service disruptions, ensuring 100% SLA maintenance and highlighting the importance of workload automation in critical revenue operations.
As SAP transitions away from legacy tools, organizations must proactively assess their workload automation platforms to ensure they support future cloud-native architectures, especially in light of imminent support end dates.
When selecting workload automation solutions, it's crucial to consider long-term architectural consistency and compatibility with future SAP innovations, while balancing the costs of switching vendors against the value of existing operational knowledge.
One of Australia’s largest energy providers successfully migrated its critical workload automation system from SAP BPA by Redwood to RunMyJobs, maintaining full service level agreement performance throughout the transition. The utility company, serving over 1 million customers, completed the migration ahead of SAP’s end of SAP BPA support at the close of 2024.
The organization depended on BPA to coordinate its SAP meter-to-cash (MC2) process, a vital revenue operation that guarantees continuous billing and regulatory adherence. In addition to M2C, the company automated tasks across HR, materials management, business intelligence, purchase orders, dunning, and billing using its SAP ECC, SAP S/4HANA, SAP IS-U, and SAP FI-CA systems.
“It was a business-critical system. We ran all our daily jobs through it, and we knew that if it went wrong, it would go very wrong,” explained the SAP Technical Analyst responsible for the company’s SAP process integration and security.
Explore related questions
Choosing Continuity Over Disruption
When SAP announced the end of SAP BPA by Redwood support, the IT team faced a crucial decision. After nearly ten years of stable BPA operations and plans to migrate to the cloud through RISE with SAP and SAP S/4HANA Cloud, the team considered several workload automation options.
The analyst, who had worked with Redwood since 2015, led a comparative analysis that ultimately favored staying within the Redwood ecosystem. “BPA has been good to us. It’s been a very stable platform,” the analyst noted. “We did a comparative analysis with a few other products, but we stuck with Redwood because BPA has run every night for the last nine years — We saw no reason to jump ship.”
According to Redwood Software, the migration to RunMyJobs went smoothly without delays, following a clearly defined implementation plan with a scheduled go-live date. The technical team appreciated that RunMyJobs’ architecture removed the need to learn new skills, as the platform’s strong features matched their existing BPA expertise while preparing them for future SAP innovations and hybrid cloud deployments.
Expanding Automation Capabilities
The successful migration reinforced the team’s confidence in RunMyJobs as their strategic workload automation platform. Going forward, the organization plans to use RunMyJobs’ promotion management features to better synchronize environments and eliminate manual updates across systems.
The team is also examining RunMyJobs’ out-of-the-box connectors for SAP Business Technology Platform (BTP) solutions, including Datasphere and Integration Suite, to modernize data management pipelines. Additional integration targets include cloud platforms like Salesforce and Databricks, supporting the company’s broader digital transformation goals.
What This Means for SAPinsiders
Workload automation has become essential for revenue operations. Organizations handling high-volume transactions through SAP IS-U and SAP FI-CA modules face significant revenue risks if workload automation fails during billing cycles. The 100% SLA maintenance achieved during the Australian utility’s migration demonstrates that well-executed platform transitions can maintain business continuity while upgrading infrastructure.
SAP’s move to the cloud is prompting infrastructure decisions throughout the ecosystem. As SAP phases out support for legacy tools like SAP BPA by Redwood and steers customers toward RISE with SAP and SAP S/4HANA Cloud, technology leaders must assess whether their current automation platforms support hybrid and cloud-native architectures. Due to the tight timeline, companies should evaluate their automation platforms now rather than waiting until they are in the middle of an ERP migration.
Platform evaluations should emphasize the migration path and architectural consistency. When choosing workload automation solutions, technology leaders should evaluate not only current features but also how well they align with future SAP roadmaps, including SAP BTP services. Important evaluation factors include native SAP certification, support for both on-premises and cloud setups, and pre-built connectors for widely used enterprise applications beyond SAP. Organizations with long-standing vendor relationships should consider the risks of switching platforms versus the costs of maintaining institutional knowledge and operational stability.
Premium
