The short answer

UKG is retiring Workforce Central (formerly Kronos Workforce Central) on a two stage timeline. Workforce Central hosted on the Kronos Private Cloud reached end of life on December 31, 2025. On premises Workforce Central reached end of engineering on the same date and reaches end of life on March 31, 2027. UKG announced the retirement in October 2022.

If you are reading this in Septemembe 2026 and you are still on on-premise Workforce Central, you have roughly seven months of vendor support left, and industry migration timelines for enterprise workforce management typically run six to nine months before testing, training, and rollout are counted. The window to make a considered decision, rather than a forced one, is closing now.

Milestone Deployment Date Status as of August 2026
End of life, Kronos Private Cloud (KPC) Cloud hosted December 31, 2025 Passed
End of engineering On premises December 31, 2025 Passed
End of life, on premises On premises March 31, 2027 About 7 months remaining
Retirement announced All October 2022 Passed
Kronos 4500 terminal retirement Hardware Alongside Workforce Central In effect

Sources: RSM US, Healthcare IT Leaders, UKG Support Policies and Services.

What "end of engineering" means versus "end of life"

These are two different things, and the difference is where most of the risk sits.

End of engineering means the product stops being developed. No service release updates, no feature enhancements, no patches for customer reported defects, no version updates to embedded third party components. For Workforce Central, this happened on December 31, 2025.

End of life means the product is no longer supported at all. For on premises Workforce Central, that is March 31, 2027. Between those two dates, UKG Global Support continues to provide technical support to on premises customers who hold a current maintenance agreement, and certain security patches remain available to those same customers.

The practical translation: since January 1, 2026, on premises Workforce Central customers have been running a frozen product. Support answers the phone. Engineering does not fix the underlying issue.

There is a third detail worth pulling out, because it is the one that reaches payroll. Under UKG's published support policy structure, legislative updates end the quarter prior to the end of engineering date. Statutory and regulatory changes that would normally arrive as an update to your system are no longer arriving. In a workforce management system, that is not a cosmetic gap. Minimum wage changes, overtime rule changes, statutory holiday pay changes, and provincial or state leave rule changes all have to be handled by configuration, by a workaround, or by a manual process.

What already changed for Kronos Private Cloud customers

If you were hosted on the Kronos Private Cloud, your deadline has passed. KPC was retired with the product on December 31, 2025. There is no on premises fallback for cloud hosted customers, because the hosting environment itself was decommissioned.

If your organization is somehow still operating in this state, this is an escalation, not a planning exercise. Talk to your account team and your auditors this week.

What happens to on premises Workforce Central on March 31, 2027

After March 31, 2027, on premises Workforce Central becomes unsupported software running your payroll inputs. Specifically:

  1. No security patches. A time and attendance system holds employee identifiers, punch history, biometric templates in many deployments, and often direct integration credentials into payroll. Unpatched, internet adjacent, and holding that data is a difficult combination to defend to an auditor, an insurer, or a works council.
  2. No defect fixes. Whatever breaks stays broken, and the workaround becomes permanent.
  3. No compliance updates. Every legislative change becomes a manual configuration project or a spreadsheet.
  4. No vendor escalation path. Third party specialists exist and can keep the lights on, but they cannot change the product code.
  5. Compounding integration drift. Your payroll system, your ERP, your HRIS, and your operating system estate all keep updating. Workforce Central does not. Certificate expiries, TLS deprecations, database version support, and browser changes are the usual failure points.

The risk profile is not "the system stops working on April 1, 2027." It is that the system keeps working while quietly becoming uninsurable, unauditable, and unfixable.

Is UKG Pro Workforce Management an upgrade from Workforce Central?

No. It is a reimplementation.

This is the single most important thing for a Workforce Central customer to understand, and it is the point that changes the entire economics of the decision. UKG's named successor is UKG Pro Workforce Management, formerly UKG Dimensions. Moving to it is not a version upgrade. Your pay rules, work rules, business structure, and integrations are rebuilt on a different data model.

Two specifics that implementation partners consistently flag:

  • Pay and work rules require net new configuration. The rule logic that took your team years to get right does not port. It is re-authored and then has to be proven to produce the same results.
  • Integrations are re-architected. Workforce Central integrations built in Workforce Integration Manager (WIM) do not carry over to Pro WFM, which uses a Boomi based integration framework. Every interface to payroll, ERP, and HR is rebuilt.

The implication is straightforward and it is the reason this article exists. If the vendor's own upgrade path is a net new implementation, then it is competing on the same terms as every other option on the market. You are not choosing between "upgrade" and "switch." You are choosing between several implementations, one of which happens to carry your incumbent's logo.

What the migration actually puts in scope

Whatever platform you choose, this is the work. Budget and schedule against the full list, not the demo.

‍

Work Item Why It Is Harder Than It Looks
Pay rules and work rules Rebuilt from scratch, then validated. Union premiums, pyramiding rules, shift differentials, and rounding conventions are where parity breaks.
Accrual balances and policies Carryover, earned to date, and taken to date must reconcile at the employee level as of cutover, not be sampled.
Business and org structure Labor levels, cost centers, and hierarchies rarely map one to one.
Integrations WIM interfaces are rebuilt. Every payroll and ERP touchpoint is retested.
Historical timecard data Decide early: migrate, archive, or retain read only access. Each option has a different cost and a different retention risk.
Time clock hardware The Kronos 4500 terminal is retired alongside Workforce Central. Pro WFM customers move to the InTouch DX terminal. This is a procurement lead time sitting inside your project plan.
Biometric templates and badges Enrollment data does not always transfer between clock families. Re-enrollment is a change management event on the shop floor.
Parallel payroll runs Two or three cycles minimum for a rule heavy operation. This is the line most projects underfund.
Manager and employee retraining Deskless and frontline populations need more than a webinar.
Reporting and analytics rebuild Custom reports are typically rewritten.

If you take one thing from this table, take the hardware line. Terminal procurement, staging, network provisioning, and physical installation across multiple sites is a lead time problem, and it does not compress just because your software deadline moved.

Why the deadline is a selection event, not an upgrade cycle

Here is the reframe that saves organizations money.

An upgrade is a technical project with a predetermined destination. A reimplementation is a purchasing decision. Because the move off Workforce Central is a reimplementation regardless of where you land, staying inside the incumbent's product family buys you very little in reduced effort. It buys familiarity with a vendor relationship, which has value, but it does not buy you a shortcut.

That means the correct behavior is to run a real evaluation. Score the incumbent's successor against the market using the same criteria, on the same scorecard, in the same timeframe. If it wins, you have a documented, defensible decision. If it does not, you have found that out before you spent the implementation budget.

Organizations that skip this step tend to discover, twelve months into a rebuild, that they paid enterprise pricing to recreate a system they were already unhappy with.

How to evaluate a Workforce Central replacement: nine criteria

Use these as a scorecard. For each one, the question in the right column is the one that separates a real answer from a demo answer.

Criterion The Question to Ask Every Vendor
1. Complex rule handling Model our actual collective agreement in the demo, not a generic overtime rule. Include our wage grid, step rates, and seniority logic.
2. Statutory and multi jurisdiction compliance How do statutory holiday rules, provincial and state leave rules, and mid pay period rate increases get maintained, and who maintains them?
3. Payroll export integrity Show us the export file into our payroll system, with our earning codes, from a real pay period.
4. Deskless and frontline access How does a worker with no company email and no smartphone punch, see a schedule, and request time off?
5. Time capture hardware What terminals do you support, what is the lead time, and what happens to our existing badges and biometric enrollments?
6. Implementation model and ownership Who configures our rules: your team, a reseller, or us? Name the people and their location.
7. Support model after go live Where is support located, what are the hours, and what is the escalation path when payroll is running tonight?
8. Contract to production timeline Given our employee count, site count, and number of pay rules, what is a realistic date for first parallel run?
9. Total cost over five years Licensing, implementation, integrations, hardware, and the annual cost of a rule change. All five.

Criteria one, four, and five are where Workforce Central customers most often get surprised, because Workforce Central was genuinely capable at complex rules. A replacement that is weaker on rules will not reveal that weakness in a scripted demo. It will reveal it in your first union grievance

Workforce Central alternatives: the current field

There is no single best replacement. The right target is the one that clears your specific requirements. Below is the honest shape of the market for a Workforce Central customer as of mid 2026.

Option Best Fit When What to Test Hardest
UKG Pro Workforce Management You want to stay inside the incumbent ecosystem and have budget for a full reimplementation Migration scope, integration rebuild, and whether the mid market account gets senior implementation resources
Synerion (Agile, Agile+, Enterprise) Complex union rules, wage grids, seniority, and multi location variation, in a 100 to 5,000 employee operation that wants best of breed workforce management alongside an existing payroll or HCM Rule modeling against your real collective agreement, payroll export format, and time clock migration path
Dayforce You want payroll and workforce management on a single continuous calculation engine Rule depth for your specific agreements, and total cost when payroll moves too
Workday You are already a Workday HCM shop and consolidation is the strategic driver Scheduling depth and complex rule handling, which are commonly thinner than purpose built workforce management
SAP SuccessFactors SAP is your system of record and suite gravity is the deciding factor Same as above: model the collective agreement, not the org chart
ADP Payroll is already with ADP and you want the time module attached to it Rule complexity ceiling and how scheduling handles your patterns
HCM suites (Rippling, Paylocity, Paycom) Salaried, straightforward workforce with light scheduling needs Whether the workforce management module can hold a union agreement at all

One pattern worth naming. Suite consolidation is chosen for strategic reasons, and often for good ones, but workforce management is where suites are typically shallowest. If your operation runs 9/80 schedules, 2-2-3 rotations, DuPont patterns, multiple collective agreements, or lunch and break rules that vary by site, test that before the contract, not after.

The alternative pattern is best of breed: keep your payroll and HR system of record, and run a purpose built workforce management platform alongside it. That is the model Synerion is built for, and it is why Synerion integrates with over 100 payroll, ERP, and HR systems including ADP, SAP SuccessFactors, Workday, Dayforce, BambooHR, Sage, Nethris, QuickBooks, and Dynamics 365.

Working backward from March 31, 2027

If you are starting in Q3 2026, this is a realistic sequence. Compress it at your own risk.

Phase Duration What Happens
Discovery and requirements 4 to 6 weeks Document every pay rule, every collective agreement, every integration, every clock, every custom report. This artifact is reusable across every vendor.
Vendor evaluation 6 to 8 weeks Scorecard, scripted demos using your real rules, reference calls with organizations of your size and complexity
Selection and contracting 4 weeks Legal, security review, data residency confirmation
Configuration and build 8 to 16 weeks Rules, structure, integrations, reports. Duration scales with rule complexity, not employee count.
Hardware procurement and install Parallel, 6 to 12 weeks Order early. This is the item most likely to gate your go live date.
Parallel testing 2 to 3 pay cycles Run old and new side by side. Compare calculated results, not summaries.
Training and rollout 3 to 6 weeks Managers first, then frontline, then supervisors on exception handling
Go live and hypercare 4 to 8 weeks Elevated support through at least two clean pay runs

Add it up and the honest range is six to nine months for a straightforward operation and nine to fourteen for a rule heavy, multi site, unionized one. From August 2026, that means the comfortable start date has passed for complex operations and is arriving now for everyone else.

Data to extract before you lose access

Do this regardless of where you land, and do it while the system is still supported. Retention obligations for payroll records commonly run three to seven years depending on jurisdiction, and they do not pause because your software was retired.

  • Timecard history for the full retention period required in each jurisdiction where you operate
  • Accrual balances and transaction history at the employee level, including carryover, earned, and taken
  • Pay rule and work rule configuration exports, as documentation of why an employee was paid what they were paid
  • Schedule history, particularly where predictive scheduling or premium pay rules apply
  • Punch level audit trails, including edits, who made them, and when
  • Attestation records, where meal and rest break attestation is in use
  • Device and clock configuration, including device groups and assigned employee populations
  • Custom report definitions and any WIM interface specifications, as the source documentation for rebuilding them

Two failure modes to avoid. First, extracting a summary rather than the underlying detail, which fails an audit. Second, extracting into a format that nobody can read in five years. Keep it queryable.

What about the time clocks?

This is the part of the project that Workforce Central customers most often price last and regret first.

The Kronos 4500 terminal is retired alongside Workforce Central, and UKG Pro WFM customers move to the InTouch DX terminal. If you have 40 clocks across eight plants, that is a hardware refresh, a network provisioning exercise, a physical install across multiple sites, and in many cases a biometric re-enrollment for every employee on the floor. It has a lead time, and that lead time does not care about your software timeline.

Since you are replacing terminals anyway, the reasonable move is to treat time capture as an open decision rather than an inherited one. Ask what your workforce actually needs:

  • Rugged wall mounted terminals for manufacturing and warehouse floors, with badge, PIN, finger biometric, or facial recognition
  • Facial recognition where gloves, moisture, or hygiene make finger biometrics impractical
  • Outdoor rated capture for construction, agriculture, yards, and logistics
  • Mobile punching with geofencing for field service, home care, and route based work
  • Tablet or kiosk punching where one shared device serves a shift

Synerion's time capture lineup covers this range: the Swift, Fusion, and Horizon clock families for fixed installations, the Sentinel outdoor rated rugged tablet with picture validation and job and labor transfers, and Synerion Mobile, a geofenced GPS punch app that is included at no additional cost. Biometrics on the terminals are the direct answer to buddy punching, which is often the original business case that justified the clocks in the first place.

One question to put to every vendor, including us: what happens to our existing employee badges? Badge reuse can remove a meaningful piece of change management from the project, and it is worth confirming in writing rather than assuming.

Where Synerion fits

We are a workforce management and time and attendance company, founded in 1983, with more than 40 years of operating history in North America. We are not an HCM suite and we do not run your payroll. We do one category of work, which is the category Workforce Central occupied.

What that means for a Workforce Central customer specifically:

  • Rule depth is the product, not a module. Union agreements, wage grids, step rates, seniority tracking, statutory holiday rules, mid pay period rate increases, split pays, accruals, and lunch and break rules that vary by location. This is the same territory Workforce Central handled well, which is precisely why suite modules are a risky landing spot for a WFC customer.
  • Best of breed alongside your existing systems. Over 3,000 integrations across more than 100 payroll, ERP, and HR systems. You do not have to move payroll to replace time and attendance.
  • In house North American implementation and support. Toronto head office, plus Southlake, Texas and Fishers, Indiana. Our customers routinely describe implementation as the reason they stayed, including building custom import and export to fit an existing payroll rather than asking the customer to change payroll.
  • Data residency in Canada and the United States, in a SOC 1 and SOC 2 certified cloud environment.
  • A mid market account is a real account here. For a large incumbent, a 600 employee manufacturer is a rounding error. For us it is a named customer with a named implementation team.
  • SAI, our built in AI assistant, answers workforce questions in natural language ("who worked overtime last week") instead of requiring a report to be built and run.

We are not the right answer for everyone. If your driver is single vendor consolidation across payroll, HR, benefits, and time, a suite is a legitimate choice and you should evaluate one. If your driver is that your rules are complicated and your last system handled them, talk to us before you assume a suite module will.

Frequently asked questions

When is Kronos Workforce Central end of life?Workforce Central hosted on the Kronos Private Cloud reached end of life on December 31, 2025. On premises Workforce Central reaches end of life on March 31, 2027, with product engineering having ended on December 31, 2025. UKG announced the retirement in October 2022.

Is Workforce Central still supported in 2026?Partially. On premises customers with a current maintenance agreement continue to receive technical support from UKG Global Support until March 31, 2027, and certain security patches remain available to them. Product engineering ended December 31, 2025, so there are no new service releases, feature enhancements, or defect fixes. Cloud hosted (KPC) customers are past end of life.

What happens if we stay on Workforce Central after March 31, 2027?The software continues to run, but without security patches, defect fixes, compliance updates, or a vendor escalation path. The practical risks are audit exposure, unpatched systems holding employee and biometric data, and integration failures as surrounding systems continue to update.

Is UKG Pro WFM a simple upgrade from Workforce Central?No. Implementation partners consistently describe it as a reimplementation. Pay rules and work rules require net new configuration, and integrations are rebuilt on a different framework.

Do Workforce Central integrations carry over to UKG Pro WFM?No. Integrations built in Workforce Integration Manager (WIM) do not carry over to Pro WFM, which uses a Boomi based integration framework. Every interface is rebuilt and retested.

Will our Kronos 4500 time clocks still work?The Kronos 4500 terminal is retired alongside Workforce Central. UKG Pro WFM customers move to the InTouch DX terminal. If you are replacing terminals regardless, treat time capture as an open decision and evaluate options across vendors.

How long does it take to replace Workforce Central?Six to nine months is a common range for a straightforward operation, and nine to fourteen months is realistic for a rule heavy, multi site, unionized environment. That includes discovery, vendor selection, configuration, integration rebuild, hardware procurement, parallel payroll testing, training, and hypercare.

Can we keep our historical timecard data?Yes, but you have to plan for it. The three options are migrating history into the new platform, archiving it in a queryable format, or retaining read only access to the legacy system. Extract timecards, accrual balances, punch audit trails, and rule configuration before support ends, and match the retention period to the payroll record requirements in every jurisdiction where you operate.

Do we have to move to another UKG product?No. The move off Workforce Central is a reimplementation regardless of destination, so the incumbent's successor competes on the same terms as any other platform. Run a real evaluation and score every option, including UKG Pro WFM, against the same criteria.

What are the best Workforce Central alternatives in 2026?The realistic field includes UKG Pro Workforce Management, Synerion, Dayforce, Workday, SAP SuccessFactors, and ADP, plus HCM suites such as Rippling, Paylocity, and Paycom for simpler workforces. There is no universal best. Score each against complex rule handling, statutory compliance maintenance, payroll export integrity, deskless access, hardware path, implementation ownership, support model, timeline to first parallel run, and five year total cost.

Is it too late to start if we have not begun?No, but the comfortable window has closed for complex operations. From August 2026, roughly seven months remain before the March 31, 2027 on premises deadline. Start discovery now, run vendor evaluation in parallel rather than sequentially, and order time clock hardware as early in the process as your contract allows.

We are a mid market manufacturer with union agreements. Where do we start?Start with a written inventory of every pay rule, collective agreement provision, integration, custom report, and time clock in your environment. That document is the single most valuable artifact in the project, it is reusable across every vendor conversation, and it converts vague demos into real answers.