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.

WFC onAPIX

Flip the switch to see the same environment 30 days from now.

Legacy systems retired with APIX
Mayo ClinicWakeMedBroward HealthThe Christ HospitalCherokee NationTompkins County, NYBrooklyn Public LibraryChesapeake Public Schools

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.

Already happenedDec 31, 2025UKG ended engineering for Workforce Central: no more service releases, patches, or defect fixes. Kronos Private Cloud hosting ended the same day.
NextMar 31, 2027Support ends for on-premises Workforce Central customers. After that the application runs on your own: an unpatched Java stack on an aging Windows Server and database.
Does not expireYour retention dutyFederal wage-and-hour rules, state law, union contracts, and litigation holds all outlive the software. The obligation to produce a 2016 timecard does not end when UKG stops answering the phone.

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.

 
Keep a WFC server “just in case”
Export timecards to spreadsheets and PDFs
Archive to APIX
Annual cost
Hosting, database licensing, DBA time, DR, and a maintenance contract that no longer buys patches
Low — until someone has to find one nurse’s punches from a Tuesday in 2017
A flat subscription. Nothing to host.
Who can find a record
The one Kronos admin who remembers the pay rules
Nobody, without a DBA and a week
Any authorized HR or payroll user, same login, in seconds
Security posture
Unsupported Java, Windows Server, and database versions in scope for every pen test
Files on a share, no access control, no audit trail
SOC 2 Type 2, encrypted, read-only, in your AWS account
Wage-and-hour claim or DOL audit
Boot the server, hope the Kronos service starts
Reconstruct punches and edits by hand from flat files
Timecards with punches, pay codes, totals, and edit history on one screen
Schedules, accruals, attestations
Second module, second license, same aging stack
Lost, or disconnected from the timecards they explain
Included, with the relationships intact
Ongoing IT effort
Patching what can be patched, backups, renewals, forever
Someone owns a folder nobody wants
Zero. Serverless. Nothing to patch.

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.

3 yrsFederal FLSA minimum for payroll records, with two years for the timecards and schedules the pay was computed from. Most states and most employment counsel require longer.
LongerCollective bargaining agreements, state statutes of limitation, healthcare staffing rules, and public-records law commonly extend the window to five, seven, or ten years.
Open-endedA litigation hold freezes the clock entirely. The records under hold are usually the oldest ones, on the system nobody wants to maintain.
MinutesWhat a records request should take once the archive is in place: find the employee, open the pay period, export the timecard with its edit history.

“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

30days from kickoff to a decommissioned Workforce Central, on average
100%of timecards, schedules, accruals, and audit trail retained
$0ongoing maintenance — serverless, nothing to patch
SOC 2Type 2, audited annually by Sensiba LLP

Questions we hear every time

Straight answers

Which Kronos and UKG systems does APIX archive?
UKG Workforce Central (Kronos WFC) versions 6 through 8.1, hosted on-premises or formerly in Kronos Private Cloud, including Workforce Timekeeper, Scheduler, Accruals, Attendance, Leave, Activities, and Analytics. If your WFC environment also carries Workforce HR/Payroll history, that is archived in the same place. Moving to UKG Pro Workforce Management, UKG Ready, Workday, ADP, or Infor WFM does not change what we keep.
We are migrating to UKG Pro WFM. Doesn’t the history come with us?
Only part of it. A migration carries current employees, current balances, pay rules and a limited window of recent history. What stays behind is the bulk of the record: years of timecards and punch detail, schedule history, accrual transactions, historical corrections, terminated employees, and the audit trail of who edited what. That is exactly the material a wage-and-hour claim, a union grievance, or a Department of Labor audit asks for.
Where does the data live after Workforce Central is shut down?
In your own AWS account, encrypted with your keys, read-only, and audited under our SOC 2 Type 2 program. Nogalis never holds a copy on its own servers. If you prefer not to run an AWS account, Nogalis can host a dedicated single-tenant deployment for you.
Can HR and payroll staff actually use it, or is it a database dump?
They use it. Timecards open the way they did in Workforce Central: by employee, by pay period, with punches, pay codes, totals, and the edit history on the same screen. Schedules, accrual balances and leave cases are the same. Reports export to Excel. Users sign in with the single sign-on they already have; nobody gets a new password.
How long does it take, and what do you need from us?
Under 30 days for most environments. Nogalis runs the whole project: extraction from the WFC database, validation against your production system, deployment into AWS, single sign-on, and training. From your side we need a read-only database connection, one person who knows your pay rules, and about a quarter of one FTE for the duration.

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.

© 2026 Nogalis, Inc. All rights reserved. | Nogalis™ and APIX™ are trademarks of Nogalis, Inc.