A clock refresh is an opportunity to improve employee experience and lifecycle economics, but it still requires disciplined planning across hardware, credentials, configuration, integration and cutover. For Workday customers, the practical question is not whether a clock can connect once; it is whether the complete collection environment can support accurate data, employee experience and long-term operations after go-live.
Inventory before choosing replacements
Document sites, current models, credentials, mounts, network/power, transaction types, labor workflows, custom interfaces and problem history.
Decide what should stay the same
A replacement does not require redesigning every workflow. Preserve stable processes and change only what delivers meaningful value.
Pilot representative environments
Test a standard office or facility plus the most difficult site: rugged, remote, high-volume, unusual credential, or complex labor workflow.
Plan phased cutover and support
Device provisioning, shipping, installation, decommissioning, spare strategy, employee communication and help-desk routing should be coordinated with the Workday timeline.
The old clock knows more about the site than the project plan does
Years of local decisions accumulate around a clock: wall placement, badge formats, network exceptions, shift-change habits, supervisor procedures and special populations. Replacing hardware without discovering those dependencies is how small migration surprises become go-live issues.
A site inventory should capture the operational history as well as the model number. That gives the replacement program a realistic basis for standardizing what should be standardized and preserving what is genuinely site-specific.
Options and when to use each approach
Big-bang replacement
Replace all clocks during a single cutover.
Fast standardization but highest operational risk; best only with strong readiness and manageable fleet size.
Phased site rollout
Replace by location or business unit.
Reduces risk and supports learning; requires temporary coexistence.
Parallel operation
Run legacy and new clocks during a controlled validation window.
Useful where cutover risk is high; carefully prevent duplicate/conflicting transactions.
Use-case-first migration
Move selected worker populations/workflows first.
Helps validate complex requirements before full rollout.
A practical decision framework
- Decide what must be true after go-live, not just what works in a demo: Inventory the dependencies behind the old clocks before selecting the migration sequence for the new ones.
- Resolve this design question early: Which sites are highest risk and should be piloted first?
- Agree on support and change-control responsibility for this decision before the design becomes harder to change.
Common design mistakes
- Assuming the new clock can use the old mount, power and credentials without validation.
- Replacing hardware before validating Workday data/integration behavior.
- Training employees only after the new clock appears on the wall.
Questions leaders should ask
- Can legacy and new clocks coexist without confusing employees or duplicating data?
- Which sites are highest risk and should be piloted first?
- Are mounts, power, network and credentials reusable?
- How will employee enrollment/credentials migrate?
- What is the fallback if a site cutover has an issue?
Migration Risk Lives in the Assumptions Around the Old Clock
A legacy terminal may encode years of operating decisions that are poorly documented: where employees are allowed to punch, which credentials work, how labor choices are presented, what happens during outages, which sites use special wiring and which supervisors depend on local workarounds. Replacing hardware without inventorying those assumptions can move old problems into a new platform—or accidentally remove a workflow employees rely on.
Use Migration to Simplify
Do not reproduce every legacy behavior automatically. Identify which rules still serve the business, which can move into Workday or the modern collection layer, and which workarounds should disappear. A phased rollout can then validate the new operating model before repeating it across the estate.
Use the Workday Move to Modernize the Collection Operating Model.
ZKTeco WFM approaches legacy replacement as more than a hardware swap. The discovery should inventory employee populations, credentials, labor workflows, site infrastructure, local exceptions, offline expectations and support ownership before the first replacement is shipped. Ultima provides the modern endpoint family, TimeTrack supports the employee experience and CirrusDCS provides the Workday-specific data collection and integration layer. That combination allows the project to preserve what still matters while simplifying legacy workarounds that no longer belong in the target architecture. ZKTeco WFM’s manufacturing and lifecycle capabilities also matter during a phased conversion because customers need consistent supply, spares and a clear successor path while old and new devices may temporarily coexist. The best migration leaves the organization with a cleaner Workday-connected operating model—not simply newer clocks attached to the same undocumented assumptions.
Legacy replacement is an operating-model migration, not a box swap. Inventory the assumptions around the old clock, preserve only what still serves the business, validate real sites and employees, and phase the rollout so the organization ends with a cleaner Workday-connected collection architecture.
Planning a Legacy Time-Clock Replacement for Workday?
Talk with ZKTeco WFM about site discovery, hardware fit, data migration, phased deployment and the CirrusDCS transition plan.
Talk to an Expert