Kronos Workforce Central
Migrate from Kronos (UKG) Workforce Central to UKG Pro Workforce Management, Workday, ADP or any system: move people, time and accruals, then switch.
Book a demoMigrate from Kronos Workforce Central to the system you choose.
Kronos Workforce Central, now UKG Workforce Central, is at the end of its life: the cloud-hosted version ended on December 31, 2025, and on-premises support ends on March 31, 2027. engini moves you off Workforce Central to the system you choose, UKG Pro Workforce Management, Workday, ADP, Rippling or another: it reads people, pay rules, schedules, timecards, punches and accrual balances where Workforce Central runs, loads them into the new system, keeps payroll exports flowing during the parallel run, and lets AI agents check every step. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
Move off Workforce Central before support ends. With people, time and balances intact.
UKG ended the cloud-hosted Workforce Central on December 31, 2025, and on-premises support ends on March 31, 2027. engini connects to Workforce Central where it runs today and to the system you are moving to, so you can load the new system, run both side by side and switch when the numbers match. We help you with the move, working with your team or your implementation partner.
Connect Workforce Central as it is
The On-Prem Agent reaches the Workforce Central XML API and its database inside your network, with no inbound ports and nothing installed on the system.
Map and check
An AI agent proposes how employees, pay rules, schedules, timecards, punches and accrual balances map to the new system and lists the records that would not load: missing fields, closed accounts, duplicates. Your team corrects the mapping before anything is written.
Load in batches
People, schedules, accrual balances and the timecard history you choose move in batches. Every record is in History, so nothing is lost or loaded twice, and failed rows are retried.
Run side by side, then switch
During the parallel run, timecards and payroll totals keep flowing from Workforce Central to payroll and the new system, so nobody is paid wrong during the switch. Afterwards, agents can still answer questions from the Workforce Central history.
Source: UKG's announced end of life for Workforce Central (cloud-hosted December 31, 2025; on premises March 31, 2027). Check the dates with UKG for your contract.
Moving off Kronos Workforce Central? We help you do it.
Tell us what you run today and where you are moving. We help you plan the move, map and check the data, load it and run both systems side by side until you switch, working with your team or your implementation partner.
What your agent can do in Workforce Central. For the move, and until the day you switch.
The Kronos Workforce Central tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Read people with their pay rule, labor level and manager.
Read worked time by period and employee.
Read planned shifts.
Read time-off balances by type.
Read the hours and pay codes sent to payroll.
Extract people, rules, schedules, history and balances in batches, for the move.
Write
Record a punch for an employee.
Change an employee's labor level or schedule group.
Triggers
A pay period was signed off and totals are ready for payroll.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to Kronos Workforce Central. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Kronos Workforce Central connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Kronos Workforce Central tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Kronos Workforce Central and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Kronos Workforce Central tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Kronos Workforce Central through engini
{
"mcpServers": {
"engini-kronos-workforce-central": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Kronos Workforce Central connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Kronos Workforce Central tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams do with Workforce Central and engini. The move, and the months around it.
Workforce Central to UKG Pro, Workday or ADP
People, schedules and accrual balances load into the new system, checked by an agent, with every record logged.
Pay right through the switch
Payroll totals keep flowing from Workforce Central to ADP or the ERP every period until the new system takes over.
Labor cost history kept
Years of hours and labor costs move to Snowflake or Power BI, so comparisons survive the move.
Balances you can still ask about
After the switch, an agent in Teams answers questions from Workforce Central history. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Kronos Workforce Central and another system engini connects is available.
You decide what each agent may do in Kronos Workforce Central. engini enforces it on every call.
Only the tools you allow
A toolset lists the Kronos Workforce Central tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Kronos Workforce Central account and engini acts as that person, with their Kronos Workforce Central permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Workforce Central behind your firewall.
If Workforce Central runs in your own data center, install the engini On-Prem Agent on a server inside your network. It opens every connection itself: out to engini over HTTPS on port 443, and to Workforce Central while it runs a task. You open no inbound ports or firewall rules. Calls through it run on the same engine as MCP, the API and workflows, and each one is recorded in History.
On-Prem Agent guide →Connect Kronos Workforce Central in three steps. Then decide what each agent may do.
Sign in to Kronos Workforce Central
Install the engini On-Prem Agent on a server that can reach Workforce Central, create a Workforce Central user with access to the XML API and read access to the data you are moving, then connect the system you are moving to.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Kronos Workforce Central from Claude, ChatGPT, Cursor or your own code.
Kronos Workforce Central and engini. Straight answers.
Can an AI agent write to Kronos Workforce Central, or only read?
Both. engini has tools to add punches and update employees in Workforce Central. For the move itself, engini writes to the new system. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does engini help with the migration from Workforce Central?
Yes. We help you plan the move, map and check the data, load it and run the parallel period until you switch, working with your team or your implementation partner. Book a call and tell us what you run today and where you are moving.
Can we move from Workforce Central to a system other than UKG Pro Workforce Management?
Yes. engini connects to UKG Pro, Workday, ADP, Rippling, SuccessFactors and more, so you choose the system that fits the workforce.
Do we have to switch everything on one day?
No. Load the new system first, then keep Workforce Central and the new system in sync during a parallel run, area by area if you like, and switch when the numbers match.
What happens to our Workforce Central history?
Bring the history you need into the new system, or keep Workforce Central read-only and let agents answer questions from it, through the same connection, until you retire it.
Can our implementation partner use engini?
Yes. Partners use engini to load, check and sync data during the move, and the same connections keep running the integrations after go-live.
When does support for Workforce Central end?
UKG ended the cloud-hosted version on December 31, 2025, and on-premises support ends on March 31, 2027. Check the date in your own UKG contract.
Does the agent act as me in Kronos Workforce Central?
It acts as the Workforce Central user behind the connection, with that user's function access. Every run is recorded under the person who started it.
Can a change in Kronos Workforce Central start work?
Yes. A scheduled trigger checks for closed pay periods, so totals reach payroll on time during the parallel run. A workflow can include an AI agent step.