Attendance 2.0 is the next generation of attendance tracking in Sloneek. To ensure a safe transition without unnecessary surprises, the old and new attendance systems will run in parallel for a period of time. This gives both administrators and employees enough space to adapt and verify that everything works as expected.
Below you’ll find an overview of what happens after the new attendance is enabled, what is migrated automatically, and the recommended transition approach.
Parallel run of old and new attendance
The old attendance and Attendance 2.0 will run side by side for at least several months.
Clients can use this period to:
test the new attendance,
verify data, reports, and processes,
prepare employees for the change.
The old attendance will be sunset (switched off) later. We will inform you about this step well in advance.
Recommended transition approach (best practice)
We strongly recommend a controlled transition, not a company-wide jump into the unknown:
Select one pilot team.
Enable Attendance 2.0 for this team and run it as a pilot for at least one month.
-
Verify:
that the numbers in reports match,
that employees understand the new interface,
that approvals and roles work as expected.
-
After a successful pilot:
roll out Attendance 2.0 to additional teams,
optionally switch off the old attendance.
This approach significantly reduces the risk of end-of-month chaos.
Terminals: transition to the new terminal
Once Attendance 2.0 is enabled:
-
The old terminal page (
app.sloneek.com/terminal) remains functional, but:a persistent notice about the new version appears on the locked screen and login screen,
a “Open new terminal” button is displayed in the footer, opening the new terminal in the same browser.
The new terminal supports the last 4 versions of modern browsers (so keep your browser up to date).
-
Terminal settings:
the terminal name and location are reused automatically,
new login PINs must be created again in the application interface (Settings / Terminals).
Hardware for terminals (card readers, cards, etc.) does not change. Hardware requirements and supported standards stay the same as outlined in this article: Attendance Terminal — Accessories and Standards (the existing card readers and access cards continue to work).
Admins don’t need to recreate terminals manually, only complete the security setup.
Migration of active events at switch time
When the HR admin switches off the old attendance:
-
all active events in the old attendance:
are automatically closed,
if needed, must be recreated in Attendance 2.0.
For this reason, we recommend scheduling the switch for the first day of the month to minimize administrative overhead.
-
Calendars and reports from the old attendance:
remain available,
display a notice that the company is using the new attendance,
contain historical data only from the old attendance.
Home page and attendance actions
The behavior of the home page depends on the module status:
New attendance disabled
Only the original attendance buttons are shown.
New attendance enabled
-
Both options are shown:
old attendance,
new attendance buttons and widgets.
Old attendance disabled
Only the new attendance is shown.
This allows a smooth transition without employees losing the ability to track attendance.
New role: Attendance timesheet approver
A new team role, Attendance timesheet approver, is introduced. It can be assigned to people responsible for approving attendance at the end of the month.
After enabling this feature:
team managers are automatically assigned to this role,
the HR admin is informed about this behavior.
Additional approvers can be:
added manually in team settings,
combined according to company needs.
The role is visible in the team overview and is fully auditable.
Migration of departure events
After enabling the new attendance, the following are migrated automatically:
departure types (lunch break, break, errands, end of shift, etc.),
their configurations and rules.
No manual action from the admin is required.
Reports: important notice
New reports contain only data from Attendance 2.0.
Old reports contain only data from the old attendance.
The data is not mixed.
This is especially important for:
payroll checks,
historical comparisons,
audits.
Summary
Attendance 2.0 and the old attendance will run temporarily in parallel.
We recommend a pilot rollout with one team.
Terminals, departure types, and roles are migrated automatically.
New PIN codes must be set for terminals.
Reports remain strictly separated by attendance type.
The goal is a controlled, calm transition without outages or surprises.
0 comments
Please sign in to leave a comment.