WLA Migration in 2026: Best Practices & Vendor Approaches
Organizations reconsider replacing their existing workload automation tools, with many actively exploring or transitioning to new solutions. The right workload automation solutions can provide immediate gains in scalability, reliability, and integration capabilities.
Explore workload automation (WLA) migration, best practices, what to pay attention to, and the differing approaches from different vendors.
What is WLA migration?
WLA (Workload Automation) migration is the process of moving an organization’s job scheduling and automation workflows from one workload automation solution or scheduler to another. Companies usually do this to replace legacy tools with modern platforms that can better support current business needs.
WLA migration also helps ensure 24/7 operations. Many businesses rely on schedulers to run complex, mission-critical processes, and moving to a more robust solution allows them to meet growing demands for automation and real-time processing.
WLA migration is not just a technical upgrade. It is a business enabler that aligns the automation infrastructure with both current needs and future growth, helping organizations operate efficiently, reliably, and at scale.
Why organizations migrate WLA tools?
Legacy job schedulers often struggle to orchestrate processes in modern IT environments. For example, older WLA systems may not run jobs seamlessly across both on-premises infrastructure and multiple cloud platforms, which makes managing hybrid IT workflows difficult.
Other common drivers for migration include:
- Digital transformation initiatives: Companies undergoing digital transformation often find that their existing automation tools lack the agility and integration capabilities needed for new projects.
- Cloud adoption and hybrid environments: Many older schedulers were not built for hybrid cloud orchestration, prompting a switch to tools that are cloud-ready. See hybrid cloud job schedulers.
- Scalability and performance: Businesses today handle larger volumes of data and processes. Modern workload automation tools are designed to scale horizontally and vertically to handle thousands of concurrent jobs, whereas a legacy scheduler might struggle or become a bottleneck.
- Maintenance costs and support risks: Legacy automation software can carry high licensing and maintenance costs. In some cases, vendors may have ended active development or support for older versions.
- Enhanced features and analytics: Newer WLA solutions often come with out-of-the-box features to provide better insights into operations, such as: visual workflow designers, centralized monitoring dashboards, granular auditing, and ML-based optimizations.
Migration approaches by leading WLA vendors
All of the top vendors share the same objective, which is to assist businesses in moving away from legacy job schedulers while lowering risk, despite their disparate strategies. There are three primary methods:
- Leverage automated conversion tools
- Depend on consultants with a focus on services
- Combine the two approaches.
Redwood RunMyJobs
RunMyJobs provides a fully guided migration service called a “migration factory.” Redwood has a team of experts and proprietary tools to migrate workloads from all major WLA platforms. They start by analyzing the existing job inventory in detail (migration assessment) and then migrate workloads in agile sprints, beginning with low-risk jobs.
Redwood’s RunMyJobs migration process often involves running the old and new systems in parallel and training the client’s team throughout the project. With over 100+ companies migrated to date, Redwood leverages ~30 years of experience to ensure a smooth transition with minimal downtime.
Figure 1. RunMyJobs Migration Steps 1
RunMyJobs migration strategy
1. Project launch
The migration begins with low-risk, simple jobs and gradually moves to more complex ones. It’s organized into agile sprints, grouping jobs by application, business unit, or job type to minimize disruption.
2. Installation and configuration
RunMyJobs environments are set up, user authentication is configured, and security protocols are defined. Integration with all systems and databases ensures smooth workflow execution across the enterprise.
3. Team training
Key stakeholders undergo training through Redwood University’s on-demand platform and instructor-led sessions, ensuring hands-on experience and continuous learning throughout the migration.
4. Agile migration sprint & hypercare
Migration happens in stages with both legacy and RunMyJobs systems running in parallel. After data conversion and testing, workflows are moved to production. Hypercare ensures the system is monitored and issues are resolved post-migration.
ActiveBatch
ActiveBatch offers a guided migration service to move organizations from legacy schedulers to its modern workload automation platform. The migration follows a phased and risk-aware approach. It starts with a detailed inventory of existing workflows and job objects, followed by a tailored migration strategy.
ActiveBatch also provides automated migration tools that convert legacy scheduler objects into ActiveBatch-compatible formats, simplifying the transition.
Training and testing are key parts of the migration. The client’s team is trained on ActiveBatch’s features, and parallel runs of the old and new systems are used to verify the migration before full deployment.
ActiveBatch has a specifically streamlined process for migration from these schedulers:
- BMC Control-M
- CA AutoSys
- CA Workload Manager
- IBM Tivoli
- Unix cron
- Windows Task Scheduler
- SQL Server Agent
For example, ActiveBatch can convert these schedulers’ jobs (including complex scheduling rules and alerts) into ActiveBatch workflows automatically. It similarly imports CA AutoSys job definitions by exporting the AutoSys JIL files and converting them into ActiveBatch objects.
These conversion tools retain job attributes as well as calendars, event triggers, resource allocations, and dependencies. The approach emphasizes reliable, script-free migration to minimize risk and downtime.
Stonebranch (Universal Automation Center)
Stonebranch’s Universal Automation Center (UAC) offers a structured migration service move organizations from legacy workload automation tools to its modern platform. The service combines automation tools with expert support and covers systems such as CA 7, SAP Job Scheduler, Tidal, Windows Task Scheduler, and cron.
Stonebranch offers the Xpress Conversion Tool (XCT) to convert legacy jobs into UAC-compatible formats automatically. For example, SAP background jobs can be imported and transformed with minimal manual effort. XCT preserves job definitions, triggers, dependencies, and resource mappings throughout the migration.
The migration follows a 7-step approach:
- Initiation: Define scope and set up the migration environment.
- Analysis: Inventory and assess the current job landscape.
- Pilot migration: Test conversion accuracy and gain approvals.
- Full transition: Automate the conversion of all workloads.
- Validation: Conduct quality checks and user reviews.
- Cut-over: Replace the legacy system with UAC in production.
- Closure: Finalize documentation and knowledge transfer.
Training, parallel runs, and go-live support ensure a smooth transition with minimal risk and disruption.
CA Workload Automation (Broadcom)
CA Workload Automation provides a structured, tool-driven migration service supported by dedicated experts. The migration is guided by CA’s proprietary tool, which automates up to 80% of the conversion from legacy schedulers such as Control-M, TWS, Tidal, and cron.
The migration includes parallel runs during testing to minimize disruptions. CA also provides operational support, training, and knowledge transfer to ensure the client’s team can manage the platform effectively. With decades of experience and a proven methodology, CA delivers efficient migrations with minimal downtime.
Migration tools support transitions from the following products:
- BMC: Control-M
- ASG: Zeke, Zena
- IBM® Tivoli®: TWS for z/OS, DJC, TWS for DS (formerly Maestro)
- Cisco: Tidal
- Native Schedulers: cron, Microsoft® SQL Server®, Windows Batch Scheduler
- Redwood: Cronacle
Figure 2. CA’s Migration Process 2
HONICO (BatchMan for SAP)
Specializes in SAP-focused workload automation and offers a tailored migration service for customers switching from other WLA providers to their BatchMan solution. Stonebranch acquired HONICO on Sept 10, 2025, integrating HONICO’s SAP tool BatchMan into its UAC platform for unified hybrid IT orchestration, while keeping BatchMan available as a standalone product.
HONICO’s approach begins with a thorough needs assessment and analysis of the customer’s current environment, followed by a proof-of-concept implementing a few critical processes in a test system. They then perform an automated bulk migration of job objects into a test environment for validation.
When it comes to cutover, HONICO is flexible: they can do a step-by-step side-by-side migration or a “Big Bang” switch, depending on what the tests indicate is safest. A HyperCare period is provided post-go-live, wherein HONICO’s team closely supports the customer’s operations to ensure stability. Their expertise in SAP scheduling means they focus on preserving SAP-specific job parameters and improving integration with SAP systems. Customers have reported significant improvements (e.g., reduced manual effort and better transparency in SAP batch processes) after migrating to HONICO’s WLA platform.
Real-life examples for WLA migration
SWM
SWM, a major municipal utility provider in Germany, migrated from BMC Control-M to RunMyJobs to streamline its workload automation and reduce operational overhead.
Challenges
SWM needed to move beyond BMC Control-M to support its expanding SAP-centric operations. The SAP Basis team sought a platform with deep SAP integration and the flexibility to manage diverse enterprise systems. A key requirement was automating the complex meter-to-cash process within SAP IS-U, which involved high-volume, multi-step job orchestration and required reliable execution across varied data sources.3
Results:
- Eliminated 1+ hour of manual effort per SAP process
- Reduced SAP HANA loads to 6–7 hours, calculations to 1.5–2 hours
- Enabled full nightly orchestration across systems
- Added auto-recovery: failed jobs restart in 30 minutes
- Improved billing accuracy and customer data availability
BSH Hausgeräte GmbH
BSH, one of the world’s leading home appliance manufacturers, replaced several outdated scheduling tools with RunMyJobs to harmonize automation across its global IT environment. The transition resulted in improved SAP job scheduling, consolidated monitoring, and significant gains in efficiency. Additionally, the unified platform helped BSH comply with internal governance standards.4
Challenges
BSH’s reliance on Broadcom AutoSys limited its ability to scale and automate complex financial and supply chain processes. The need for frequent custom development led to instability, high maintenance costs, and disruptions. With a sprawling IT environment, including five core SAP ERP systems, 30+ additional systems, and 2,000+ servers, BSH required a more reliable and scalable automation platform to support its global operations.
Results:
- Built resilience through exception handling and dynamic process flows
- Replaced AutoSys with real-time, event-driven orchestration
- Improved data accuracy and decision-making across the supply chain
- Gained full process visibility via dashboards and alerts
- Standardized supply chain automation and reduced manual work
Whitbread PLC
Whitbread, the UK’s largest hospitality company, adopted RunMyJobs to support its SAP landscape. The organization sought to minimize manual interventions and improve scheduling reliability across finance and retail operations. The migration enabled Whitbread to enhance system resilience and manage workload peaks more effectively, particularly during busy retail periods.5
Challenges
Whitbread faced the dual challenge of replacing two legacy systems, SAP RemoteWare for file transfers and Broadcom AutoSys for job scheduling, both managed by third parties. With RemoteWare nearing end-of-life, the team needed a phased, non-disruptive migration that complied with strict IT governance and security standards. Their goal was to consolidate operations under a single, reliable automation platform capable of handling complex, enterprise-wide workloads across retail and hospitality divisions.
Results:
- Migrated 1,900 jobs in 6 months with zero post-migration issues
- Consolidated 1,200 AutoSys jobs down to 100 using Redwood
- Gained full visibility into 800+ enterprise outlets
- Automated process documentation and improved cross-team alignment
- Integrated incident management with ServiceNow
UBS
Global financial services firm UBS transitioned to RunMyJobs to gain better control over its distributed batch job operations. The new system offered UBS a single, central view of job execution and enabled quicker responses to incidents. The bank benefited from enhanced compliance, reduced operational risk, and improved reporting across teams.6
Challenges
UBS struggled with a fragmented and labor-intensive financial reporting environment, relying on nearly 100 staff to manually coordinate disconnected systems. With 10 million postings per hour and the need to report on 500 million account balances, legacy tools couldn’t meet performance or compliance demands. Rising regulatory requirements (e.g., US GAAP, IAS) and a sprawling IT landscape were driving up TCO, with no single system capable of managing the scale, until Redwood was introduced.
Results:
- Replaced 16 legacy applications with a unified automation platform
- Improved total cost of ownership (TCO) by 30%
- Cut external reporting time from 9 days to 5 days post-close
- Automated processing of 15+ billion transactions in 9 months
- Centralized financial data for faster insights and risk response
- Gained a strategic 5-year advantage, according to UBS leadership
What to consider before & during WLA migration
Migrating critical automation workloads is a complex project with technical, operational, and business risks. Key considerations include:
Technical factors
- Compatibility and data migration: Job definitions, schedules, scripts, and dependencies need to be translated to the new system. Custom scripts or legacy API calls may require rewriting. Ensure all scheduling metadata is migrated or reconfigured correctly.
- Integration: Check all integrations with other systems. Address gaps to avoid disruptions.
- Automation tools: Many vendors provide automated migration tools that convert jobs and workflows, often covering 70–80% of the migration. Engineers should handle edge cases and test critical jobs thoroughly.
Operational considerations
- Downtime risk: Running critical batch jobs or data pipelines can be disrupted. Reduce risk by running old and new systems in parallel or migrating in phases.
- Workload validation: Verify that migrated jobs trigger and execute correctly. Compare run logs from old and new systems.
- Training and knowledge transfer: Ensure operations staff are trained on the new system to avoid misconfigurations and slow responses. Document processes and configure monitoring and alerts from day one.
Business considerations
- Stakeholder buy-in: Ensure leadership and end-users understand the purpose and expected benefits to secure cooperation.
- Cost and ROI: Migration includes licensing and project costs. Expected benefits such as reduced manual work or new capabilities should outweigh the migration effort.
- Timing: Avoid conflicts with critical business periods like quarter-ends or holiday seasons.
Best practices for WLA migration
Thorough preparation is essential for a smooth WLA migration. These steps help organizations plan, execute, and validate the transition with minimal risk and disruption.
1. Audit and assess workloads
Start with a full inventory of all jobs, workflows, and dependencies. Identify critical and complex jobs, as well as any redundant or obsolete tasks that could be removed. This assessment sets the migration scope and highlights areas that need extra attention.
2. Start planning early
Begin evaluating new WLA solutions well before your target go-live date, ideally six months in advance. Early planning allows time to compare vendors, run proofs-of-concept, and allocate budgets without being rushed.
3. Select the right vendor
Not all WLA platforms handle migration equally. Review each vendor’s features, integrations, and migration capabilities. Automated conversion tools or consultative services can significantly reduce manual effort and risk. Check references and customer feedback to confirm reliability.
4. Map processes and dependencies
Document how workflows operate today, including job schedules, triggers, dependencies, scripts, and error handling. Identify any workarounds or custom scripts that can be simplified in the new platform.
Modern WLA tools often allow built-in features that replace complex legacy scripts.
5. Engage stakeholders
Involve IT, operations, application owners, business users, and executives early. Explain the migration plan, timeline, and potential risks. Collect input from all groups to ensure critical jobs are accounted for and everyone understands the expected benefits.
6. Pilot the migration
Before full migration, test a subset of workloads. Choose jobs that cover various features of the scheduler but aren’t so critical that errors cause major disruptions. Pilot runs validate the migration tools, uncover issues, and allow the team to familiarize themselves with the new system.
7. Prepare for parallel runs
Run the old and new systems simultaneously for a period. During this phase, jobs execute on both platforms for verification. Parallel runs reduce risk, allow direct comparison of results, and build confidence before the full cutover.
8. Train your team
Ensure administrators and operators are trained on the new platform. Use vendor resources such as workshops, online courses, or certification programs. Involve your team in hands-on configuration and testing during the migration to accelerate learning and build confidence.
9. Validate workloads
Thoroughly test and verify that all jobs run correctly on the new system. Check schedules, dependencies, triggers, alerting, restart logic, time zones, and holiday calendars. Include end-users or downstream application owners in testing to confirm outputs match expectations. Only proceed to full cutover when results are validated and stakeholders approve.
10. Plan cutover and post-migration support
Schedule the final switch during low-impact hours. Maintain a rollback plan in case issues arise. Provide HyperCare support immediately after go-live, with extra staff or vendor engineers available to resolve issues quickly. Document the entire project, capture lessons learned, and finalize remaining tasks such as decommissioning old servers.
WLA Migration FAQ
FAQ
Reference Links
Cem's work has been cited by leading global publications including Business Insider, Forbes, Washington Post, global firms like Deloitte, HPE and NGOs like World Economic Forum and supranational organizations like European Commission. You can see more reputable companies and resources that referenced AIMultiple.
Throughout his career, Cem served as a tech consultant, tech buyer and tech entrepreneur. He advised enterprises on their technology decisions at McKinsey & Company and Altman Solon for more than a decade. He also published a McKinsey report on digitalization.
He led technology strategy and procurement of a telco while reporting to the CEO. He has also led commercial growth of deep tech company Hypatos that reached a 7 digit annual recurring revenue and a 9 digit valuation from 0 within 2 years. Cem's work in Hypatos was covered by leading technology publications like TechCrunch and Business Insider.
Cem regularly speaks at international technology conferences. He graduated from Bogazici University as a computer engineer and holds an MBA from Columbia Business School.
Be the first to comment
Your email address will not be published. All fields are required.