ZKTeco BioTime vs ClockIt

Written for people already running BioTime on a PC in the office. Your ZKTeco terminals stay exactly where they are — this is a software change, not a hardware one.

Start free — no card

Switching takes one settings change on the terminal. No re-enrolment, no new hardware, no local server.

Your ZKTeco devices already work with ClockIt

BioTime talks to your terminals over ADMS — ZKTeco's push protocol. So does ClockIt. That means the switch is one field on the device: change the server address from your local install to ClockIt's, and punches start arriving in the cloud instead.

Nobody re-enrols a fingerprint or a face. Biometric templates live on the terminal, not in BioTime, and changing where it pushes does not touch them.

What BioTime is

BioTime is ZKTeco's own time and attendance software, sold alongside its terminals and now also branded ZKBio Time. You install it on a Windows PC or server on your own network, and it becomes the ADMS server your ZKTeco devices push their punches to. ZKTeco's own product material describes the current 9.5 release as on-premise software for organisations that want local deployment. It handles timetables, shifts, schedules and attendance reports, and on the larger licences it sits alongside ZKTeco's access-control modules.

This guide covers:

BioTime 8.0BioTime 8.5BioTime 9.5ZKBio TimeZKBioTime

Why teams move off BioTime

The server is a machine somebody has to keep alive

Because BioTime runs on your own hardware, the attendance system inherits every problem that PC has. If it is switched off, patched, moved, or simply fails, punches stop reaching it. Teams usually move after the first time payroll is held up by a server nobody had thought about in two years.

Getting at it from outside the office is a networking project

Reaching an on-premise install from home, from another branch or from a phone means exposing the server, running a VPN, or forwarding ports — and keeping that secure. Multi-site operators feel this first, because each site tends to end up with its own install and its own set of reports to merge by hand.

Only people who touch a terminal are in the system

BioTime is built around the clock on the wall. Field staff, drivers, remote workers and anyone between sites are not covered by it, so they end up on a spreadsheet that has to be merged with the device data every pay run.

Attendance stops where payroll starts

The software's job ends at attendance reporting. Leave balances, approval chains, timesheet sign-off and payroll-ready exports are typically handled elsewhere, which is where the manual re-keying — and the errors — come in.

BioTime and ClockIt side by side

Compared on structure — where the software runs, what it covers and how it is licensed. We do not quote ZKTeco prices or licence terms here, because those vary by reseller and edition and we cannot verify them for your account.

 BioTimeClockIt
Where it runsWindows PC or server on your own networkCloud — nothing to install or keep running
Your ZKTeco terminalsPush punches to your local install over ADMSPush punches to ClockIt over the same ADMS protocol
Re-enrolment on switchingNone — templates stay on the device
Access from outside the officeVPN, port forwarding or an exposed serverAny browser, plus iOS and Android apps
Static IP requiredTypically, to reach the server remotelyNo — the device opens the connection outward
Staff without a terminalNot covered by the device softwareMobile, GPS and web clock-in on the same account
Multi-siteCommonly one install per site, merged manuallyEvery site in one account
Shift schedulingTimetables and shift assignmentScheduling with publishing, swaps and coverage
Leave and time offHandled outside the attendance softwareBuilt in, with accruals and approvals
Timesheet approvalsHandled outside the attendance softwareBuilt in, with an audit trail
Job or cost codes on the punchKeyed at the terminal, costed to Projects and Tasks
Payroll exportsAttendance reports to re-keyPayroll-ready exports and API
Licence modelPurchased per install, with device and employee tiers$2.99 per employee per month, free plan available
Access control (doors)Available in the wider ZKTeco suiteNot offered — see below

What ClockIt does not replace

ClockIt is a workforce management product, not an access-control system. If your ZKTeco install is also controlling doors, turnstiles, anti-passback zones or visitor management, ClockIt does not take that over and is not trying to. Plenty of sites run both: the terminal keeps doing door control through ZKTeco's own software, and ClockIt takes the attendance side. Worth knowing before you plan a cutover, because the two halves are often licensed together and people assume they move together.

Your ZKTeco terminals stay

Every one of these connects to ClockIt over ADMS. Pick your model for the exact menu path, or see the full ZKTeco device list.

How to switch

  1. 1

    Export your punch history first

    Pull your attendance history out of the existing software as CSV or Excel before you change anything. The data lives in a database on your own PC or server, and the export is trivial while the system is running — much less so after a machine is retired or a licence lapses. Keep it regardless of whether you import it; payroll audits reach back years.

  2. 2

    Create your ClockIt account

    Free to start, no card. Add your employees, set your pay period, and rebuild your shift and overtime rules. If you are coming off a system that has been running for years, this is the moment to fix the rules that were always slightly wrong rather than port them across unchanged.

  3. 3

    Repoint the device at ClockIt

    On the terminal, go to Menu → Comm → ADMS / Cloud Server and change the server address to ClockIt's. That is the entire switch. You are changing which server the device pushes to — you are not reflashing, resetting or re-enrolling anything.

  4. 4

    Map device user IDs to ClockIt employees

    Each terminal already stores an enrolment number against every fingerprint or face. You match those IDs to your ClockIt employee records once. Biometric templates never leave the device, so nobody re-enrols.

  5. 5

    Reconcile one full pay period

    Run a complete pay period in ClockIt and reconcile it against the last period from your old system before you decommission the old server. Note that the terminal pushes to one server at a time, so this is a sequential check against your exported history rather than two systems running side by side.

Implementing ClockIt's biometric kiosks eliminated buddy punching overnight. The facial recognition is instant and works perfectly even in our warehouse environment. It's the most secure time tracking decision we've made.

James Wilson
Plant Manager, Apex Manufacturing

BioTime to ClockIt: common questions

Will my ZKTeco devices work with ClockIt, or do I need new hardware?
They work. ClockIt speaks ADMS — the same ZKTeco Push protocol BioTime uses — so any terminal with a Cloud Server or ADMS option in its menu can push to ClockIt instead. That covers the iClock, uFace, iFace, SpeedFace, ProFace, MB, UA and IN series. You are changing a server address, not buying hardware.
Do employees have to re-enrol their fingerprints or faces?
No. Biometric templates are stored on the terminal itself, not in BioTime, and switching the server address does not touch them. You map each device enrolment ID to a ClockIt employee once and every existing enrolment keeps working.
Can I run BioTime and ClockIt at the same time to compare them?
Not on the same terminal. An ADMS device pushes to one server address at a time, so pointing it at ClockIt means it stops pushing to BioTime. If you want a genuine parallel trial, point one terminal at ClockIt and leave the others on BioTime, or export your BioTime history and reconcile a full pay period against it after switching. We would rather tell you this than have you discover it mid-cutover.
What happens to the attendance history already in BioTime?
It stays in your BioTime database and is yours. Export it to CSV or Excel while the install is still running and keep it for your records — that is the one step people skip and later regret, because reaching an old local database after the machine is retired is genuinely difficult.
Do I still need the PC or server BioTime was running on?
Not for attendance. The terminal connects to ClockIt directly over your internet connection, so there is no local server in the path and nothing to keep patched or powered. If that machine is also running ZKTeco access control, keep it for that.
Do I need a static IP or port forwarding?
No. ADMS is push-based: the terminal opens the connection outward to ClockIt, so it works on ordinary broadband or 4G with no static IP, no port forwarding and no inbound firewall rules.
Is ZKBio Time the same thing as BioTime?
It is the same product line under ZKTeco's newer branding. Whether your install is labelled BioTime 8.0, 8.5, 9.5 or ZKBio Time, it is doing the same job — acting as the ADMS server your terminals push to — and the switch to ClockIt works the same way.
Can employees enter a job or cost code at the terminal?
Yes. ZKTeco terminals with a keypad can take a job, project or cost code as part of the punch. The code travels to ClockIt with the punch and resolves to the matching Project or Task, so hours are costed to the right job without a paper job sheet. No firmware change and no extra hardware — only a keypad on the terminal.

Running different software?

Keep the hardware. Lose the server.

Point one ZKTeco terminal at ClockIt and see a full day of punches arrive before you decide anything. Free to start, no card.

Start free — no card