- Nothing broke on July 1. Support for patches and bug fixes has ended, but your existing integrations will most likely keep running as-is.
- The next milestone is September, when Workday releases 2026 R2. Platform updates at that point could affect the connection points Pentaho integrations depend on, though not every customer will be affected.
- Moving proactively lets you set your own timeline. Waiting means responding to changes after they happen instead of ahead of them.
- We’re glad to help. We can review your ETL process and help identify the right path forward. The right option depends on your setup.
On June 30, 2026, Workday Adaptive Planning ended support for integrations built on Pentaho (Kettle), following Pentaho’s own decision to retire version 9.3. If your actuals, HR data, or operational data flow into Adaptive through a scripted data source or scripted loader, this affects you. If they don’t, no action is needed.
End of support does not mean your integrations stopped running on July 1. The pipelines you have in place will most likely keep functioning normally for now.
Here’s the part worth understanding. With Workday 2026 R2 expected in September, platform updates could affect the connection points your Pentaho integration depends on. This may not create an issue for every customer, but unsupported integrations aren’t guaranteed to keep working once the underlying platform changes. Moving now means you control the timeline for migration rather than reacting to it later.
Your integration has probably been running quietly
Most Pentaho setups became a standard part of operations over the years. They were built to feed actuals, HR data, and operational data into Workday Adaptive Planning, and they’ve kept working since. As people moved on and new processes were layered on top, the original logic often became something a team inherited rather than something a team built firsthand. That’s typical for infrastructure that works reliably. It stops getting attention.
This is a natural point to take a closer look.
There’s a clear path forward
Adaptive supports several modern integration paths, and the right one depends on your specific setup. After a conversation about what your ETL process looks like today, we can help identify the best route. The transition isn’t always simple, especially when data originates in a layered ERP or HRIS environment with years of business logic built in. That’s the kind of complexity worth working through carefully.
This is what we do
Workday Adaptive Planning implementation is what we do. We’ve spent years both implementing it and moving integration workflows off older architecture onto modern, supported foundations. Our team audits your existing Pentaho-based data loads, maps each one to your preferred integration path, and manages the transition with you.
We also prioritize knowledge transfer as part of the work. When we’re done, your team understands what each pipeline does, why it does it, and how to maintain it going forward, rather than relying on institutional memory.
Rather than rebuilding what’s there line for line, we look at the whole picture and identify opportunities to simplify: rationalizing data flows and removing redundant steps where it makes sense. The goal is for you to end up with fewer things to maintain and more reliability than before.
How to see what you’ve got
A few minutes will tell you where you stand. In Adaptive, go to Integrations, then Design Integrations, and check your Component Library for any Scripted Data Sources or Scripted Loaders. Then check Run Tasks, open Execution History, and filter by those sources to see what’s actually been running. That’s your list of what needs a new integration path.
Once you know what you’ve got, we can talk about next steps. We’ll review your ETL process, audit your current loads, and help design a migration path that fits your environment, well ahead of any changes from the 2026 R2 release.
Reach out whenever you’re ready. We’ll take it from there.