TAC HRTAC HR
From Excel to HR Software: A Two-Week Migration Plan
Running HR and choosing a system

From Excel to HR Software: A Two-Week Migration Plan

A 14-day work plan for moving from Excel sheets to HR software: cleaning data, importing employees, branches, Nitaqat, the app, and the first payroll.

5 min read

You can lay out a move from Excel to HR software in two weeks of work if your employee data is mostly complete: week one for data, branches and attendance setup, week two for the app, a parallel run and the first payroll. This is a suggested work plan, not a promised duration. The real timeline in your company depends on how clean your data is, how many branches you have, and how fast decisions get made.

Before you start: three conditions

  1. One person owns the migration, with authority to settle any dispute about the data.
  2. One Excel file is the reference, not three files that disagree.
  3. A written decision on the date the system becomes the only source of attendance, so attendance does not live on paper and in the system after the parallel period.

Without these, the plan will run long however good the software is.

Week one: data and setup

Days 1 and 2: audit and clean the employee file

Open the employee file and check the columns the system needs: name, ID or iqama number, nationality, start date, job title, department, branch, base salary and allowances, mobile number, and IBAN. Then clean up:

  • Duplicate or missing ID and iqama numbers.
  • Dates written in mixed formats; unify them.
  • Names spelled more than one way for the same person.
  • Incomplete Saudi IBANs, because the Wage Protection System (WPS) file validates them.

Record the expiry dates of IDs, iqamas, passports, contracts and medical insurance in their own columns. These become alerts.

Day 3: import

TAC HR imports employees from an xlsx or csv file and previews the errors on every row before saving. Start with a small batch of 10 employees to see the common errors in your file, then import the rest. Fix what the import rejects in Excel and run it again, rather than editing row by row in the system.

Day 4: branches, departments and permissions

Create the branches and departments and decide who sees what. Permissions are scoped by branch and department, so a branch manager sees only that branch. Also choose which request types to turn on and set the approval route for each, as described in approval routes.

Day 5: geofences and shifts

Set each branch's location and the punch perimeter around it, and set each employee's punch location: anywhere, one site, or several sites. Then define shifts, including two shifts in one day and shifts that cross midnight. The geofence attendance setup guide walks through the steps.

Also check your Saudization rate from the migrated file with the Nitaqat calculator. The nationality data you just cleaned is its input.

Week two: the app, the parallel run and payroll

Days 6 and 7: roll the app out to employees

An account is created for each employee, who installs the app (Arabic, English, Urdu or Hindi) and links it to their device. A new device is blocked until management approves the change request. Tell the team that punching requires an internet connection, and that a rejected attempt is visible to management, not to them. For field staff, switch on the field tracking flag in their file.

Days 8 to 10: the parallel run

Run the system and Excel together for at least three working days. At the end of each day, compare: who was late in Excel and who was late in the system? Each difference has a cause: a perimeter that is too tight, a wrong shift, or an employee who has not installed the app. Fix the setup, not the record. Then confirm the cut-over date and retire the spreadsheet.

Days 11 and 12: payroll components

In the system, review each employee's pay components: base salary and allowances, outstanding advances and their installments, the lateness and absence penalty table, and GOSI contributions under each employee's system. Reconcile a sample of 5 employees against last month's Excel payroll to confirm base pay did not change.

Days 13 and 14: the first payroll

Create the draft and review attendance and lateness first, using the steps in reviewing absence before payroll, then run the payroll review checklist. After approval, export the WPS file, check its readiness, and upload it to Mudad.

A 14-day split by activity

DaysActivityResult
1–2Clean the employee fileOne reference file
3ImportAll employees in the system
4Branches, permissions, requestsCompany structure
5Geofences and shiftsPunching ready
6–7The appEvery employee on their device
8–10Parallel runCut-over decision
11–12Payroll componentsSample reconciled
13–14First payrollApproved payroll and WPS file

What can stretch the plan?

  • Missing data: IBANs, IDs or expiry dates that were never recorded.
  • Several branches with different shift patterns: each pattern needs defining.
  • Employees without a modern phone: the company uses a compatible fingerprint device for them.
  • No decision maker: who settles a data dispute?

What to prepare before day one

  • A backup copy of the current Excel file, kept untouched.
  • A list of branches with their addresses and coordinates, because the geofence needs each branch's location.
  • The current shift pattern for each team, including split shifts and shifts that cross midnight.
  • The request types your employees submit today on paper or WhatsApp, and who approves each.
  • The current penalty table for lateness and absence, if the company has one.
  • Last month's payroll, which is the reference for the reconciliation on day 11.

Every missing item here shows up later as a delay on one of the fourteen days.

From Excel to TAC HR

TAC HR brings attendance, requests, payroll and archiving into one record. Start with the attendance system and then payroll; the payroll setup guide covers the components. To see the plan applied to your own data, request a demo.

FAQ

Can I move my old attendance records from Excel?

The import described here is for employees. The new record starts on the cut-over date, and your old Excel files stay with you for reference.

What if many rows fail to import?

The errors show row by row before anything is saved. Fix them in the file and import again.

Should I start with payroll or attendance?

Attendance first, because payroll reads its record. Add payroll once week one has settled.

Do I need a fingerprint device?

No. Phone punching inside the perimeter is enough for anyone with a phone, and TAC HR supports compatible fingerprint devices for those who need them.

What do I do with an employee who will not install the app?

Give them a punch location or a compatible device temporarily until the problem is solved, and do not leave their attendance in Excel.

Show us how you work, and we'll show you the difference.

In the demo we walk through a full day in your company: the morning punch, a request, the month's payroll, and the rep in the field, on data like yours.