UKG Workforce Central · Kronos data archive
Workforce Central is still running. Here is what that costs you.
UKG stopped engineering Kronos WFC at the end of 2025. The servers are still on, still in scope, and nobody is watching them.
Nothing archived, nothing decommissioned, and the clock is running.
Flip the switch to see the same environment 30 days from now.








The Workforce Central clock
UKG set the dates. The only question is what happens to twelve years of timecards.
Kronos Workforce Central is the system of record for every hour your people worked, every schedule they were given, and every edit a supervisor made. UKG is retiring it. The history has to go somewhere.
What the migration leaves behind
Your new system takes the balances. It does not take the history.
Whether you are moving to UKG Pro Workforce Management, UKG Ready, Workday, or ADP, the migration is designed to start the new system clean. That is the right call for the new system. It is a problem for the old record.
What comes over
- ✓Active employees and their current assignments
- ✓Current accrual balances as of the cutover
- ✓Pay rules, work rules, and schedule patterns, rebuilt
- ✓A short window of recent timecards, if you pay for it
What stays on the old server
- ✗Every closed pay period of timecards and punch detail, back to go-live
- ✗The audit trail: who edited which punch, when, and what it said before
- ✗Schedule history, shift swaps, open-shift fills, attestations
- ✗Accrual transactions, leave cases, and attendance points over time
- ✗Terminated employees, who are the ones who file claims
- ✗Historical pay codes and rule versions needed to explain an old total
Your three options
There are three ways to get rid of Workforce Central. Two of them don’t work.
Every HRIS and IT leader we talk to has considered the first two. Here is why they end up on the third.
How it works
Three steps. Thirty days. Then you shut Kronos down.
We extract and validate everything
Every table in the Workforce Central database: timecards, punches, pay codes, schedules, accruals, leave, attendance, and the audit tables behind them. We run automated checks against your production system before anything is decommissioned. If a pay period total does not match, we find it, not your auditors.
Weeks 1–2
We deploy APIX into your AWS account
Serverless: S3, Lambda, Athena, OpenSearch, CloudFront. Hardened with a 30-point checklist, WAF, and an independent penetration test. It lives in your cloud, under your keys, fully managed by Nogalis.
Week 3
Your team logs in. Workforce Central goes dark.
Single sign-on with your Active Directory or Entra ID means nobody gets a new password. HR and payroll find timecards by employee and pay period, with punches and edit history, the way they always have. Then you shut the servers down — for good.
Week 4
Why the record matters
Time records are the evidence in every wage-and-hour dispute. Keep them where you can produce them.
“The question an auditor asks is never which server the timecard lives on. It is whether you can produce it, with the edit history, this afternoon.”
How we frame every Workforce Central retirement
Questions we hear every time
Straight answers
Which Kronos and UKG systems does APIX archive?
We are migrating to UKG Pro WFM. Doesn’t the history come with us?
Where does the data live after Workforce Central is shut down?
Can HR and payroll staff actually use it, or is it a database dump?
How long does it take, and what do you need from us?
Shut Workforce Central down before March 2027.
Thirty minutes with a Nogalis engineer. We look at your Workforce Central footprint, tell you exactly what the archive will contain, and set up a demo on data like yours. Pricing follows the demo.
