How to switch from a fingerprint machine to phone-based attendance (2026)
By Sayed Zakrea · 25 June 2026 · Updated 26 October 2026
Moving from a wall-mounted fingerprint clock (ZKTeco or similar) to phone-based check-in is straightforward if you do it in the right order: export your history, set up the new system, enrol your team, run both in parallel for a week, then retire the device. Here is the playbook.
Can you connect a fingerprint machine to your phone?
Some fingerprint terminals come with the manufacturer's own software or cloud service that shows the device's records on a phone, so you can see the data remotely. But employees still have to walk to the device to punch, and the device still covers a single door.
Dawmly gives you two ways. You can let each employee's phone become the punch device, with the time and GPS location of every punch, no hardware to buy or repair, and branches and field staff on the same app: see the mobile attendance app. Or, from the Starter plan, you can keep the machine and import its attendance log (the attlog.dat file, or a ZKTime/ZKBioTime report) into Dawmly. Machines with the cloud server (ADMS) setting can also send punches live; for any other machine it is a file you upload.
Why switch at all?
A fingerprint terminal only covers one door. The moment you open a second branch, send staff to a client site, or hire a delivery or field worker, it stops reflecting reality. Phone-based check-in captures a GPS-verified location and timestamp from anywhere — every branch, every client site, every field visit — and exports straight to payroll, none of which a fixed device does. It includes optional selfie verification and offline punch queueing. For the full side-by-side, see Dawmly vs fingerprint machines.
Step 1 — Export your existing data
Before you change anything, pull the attendance history off the old device using its desktop software (usually a USB or network export to CSV/Excel). Keep that file as your historical archive — you will not migrate it into the new app, but you want it on hand for payroll and any open disputes.
Step 2 — Set up the new system
Create your workspace, add your branches/locations, and define working hours and shifts. With Dawmly this takes about five minutes, and it is free forever for up to 3 employees so you can set it up at no cost.
Have a ZKTeco machine?
Dawmly imports the machine's log or syncs with it live (Starter plan), so the machine and the phones can run side by side while you switch. Clocking in from the phone is free for up to 3 employees.
Start freeStep 3 — Enrol your team
Invite employees and have them install the app and complete one test check-in each. This is where Arabic-first UX pays off: a clear Arabic interface means staff get it on the first try, instead of needing to be re-trained. Confirm the GPS location is captured on that first punch (with optional selfie verification).
Step 4 — Run both in parallel for a week
For one week, let employees clock in on both the old device and the new app. Compare the two records at the end of the week: they should match. On the Starter plan you can make the comparison easy by importing the machine's log for that week into Dawmly: sessions already recorded from the app are skipped, and anything the app missed shows up. This builds trust, surfaces any stragglers who have not enrolled, and gives you a clean cut-over date.
Step 5 — Retire the device
Once the parallel week matches, announce the cut-over and switch the fingerprint machine off. Keep the exported history archived. From here, attendance follows your team wherever they work, and month-end payroll comes from a one-click export.
Handling reluctance
In practice, once staff see that mobile check-in takes just two seconds with no waiting lines or shared hardware to touch, resistance fades quickly — especially with a clear Arabic-first interface and a lightweight, fast app.