Buyer guides · November 2026 · 6 min read · By the OfficeHR team

How to Switch HR Software Without Losing a Month

The fear of switching keeps more UAE companies on software they dislike than the software itself does. It is a rational fear and it is also, for a company of twenty to forty people, mostly misplaced.

Done in the right order, a migration at this size is about a week of light work spread across a month. Done in the wrong order, it is genuinely a lost quarter. The difference is almost entirely about sequence, not effort.

Here is the sequence.

The short version

Export your data before you give notice on anything. Cut over at a month end, never mid month. Run one full payroll cycle in both systems at the same time and compare the SIF files line by line. Keep the old system until the new one has produced one payroll that your bank accepted.

That is the whole method. Everything below is detail.

Step 1: export everything, before you cancel anything

Do this first, before you sign with anyone new and well before you give notice on the current system.

Pull out your employee master list, salary history, leave balances, uploaded documents and the last twelve months of payslips. Get it in a format you can actually open, which usually means CSV or Excel rather than a PDF report.

Two reasons this goes first. Retrieving data from a subscription that has lapsed is a slow and occasionally expensive conversation. And the export itself tells you something useful: if it is awkward or needs a support ticket, you have learned how the relationship works at exactly the moment that knowledge is most useful.

Check the export actually contains leave balances as numbers. A surprising amount of HR software exports leave as a report rather than as data, and leave balances are the thing that causes arguments after a migration.

Step 2: pick a month end as your cut over

Not the 10th. Not "when we are ready". A month end.

Payroll, leave accrual and gratuity all run on monthly boundaries. Migrating mid month means splitting a pay period across two systems, which means hand calculating one month's proration, which is exactly the error prone manual work you are trying to escape.

Pick the month end, work backwards, and give yourself three weeks before it.

Step 3: load the data and reconcile three numbers

Get your people into the new system, then check three things against the old one before you go any further.

Headcount. Does the new system have exactly the same number of active employees? Leavers and people on unpaid leave are where the count drifts.

Total monthly salary. Add up the fixed and variable components in both systems. They should match to the fil.

Leave balances per person. Not in total, per person. This is the one that generates complaints three months later when somebody's balance is two days short and nobody can explain why.

If those three reconcile, your data is good. If they do not, fix it now, while you still have the old system to check against.

Step 4: run one full cycle in parallel

The month before you cut over, do payroll twice. Once properly in the old system, which is the one you actually submit. Once in the new system, which nobody sees.

Then compare the two SIF files.

Open both in a text editor side by side. Check the SCR line first: employer ID, bank routing code, salary month, record count, total. Then every EDR line: labour card number, routing code, IBAN, pay period dates, days in period, fixed and variable amounts.

They should be identical. If a line differs, you have found a real problem in a month where it costs you nothing, which is the entire point of the exercise. The free WPS file checker has a compare mode that lists every field that differs.

Pay particular attention to anyone who joined or left mid month, anyone on unpaid leave for part of the period, and anyone whose salary changed. Those three cases are where payroll systems quietly disagree with each other.

Step 5: tell your employees something short

They do not need a change management programme. They need three sentences and a link.

Tell them what is changing, when, and what they personally have to do, which is usually log in once and check their leave balance. Ask them to report anything that looks wrong within the first week, because the people who will catch an error in their own leave balance are the people whose balance it is.

Do this a week before the cut over, not the day of.

Step 6: cut over, and keep the old system one more month

Run the first real payroll in the new system. Submit it. Wait for the bank to accept it and for salaries to land.

Then, and only then, cancel the old subscription. Paying one extra month for a system you are not using is the cheapest insurance in this entire process, and it means a problem on payday is an inconvenience rather than a crisis.

The three mistakes that actually cost people a quarter

Cancelling the old system too early. Almost every migration horror story starts here. The data is gone, something is wrong, and there is nothing to check against.

Migrating mid month. Creates a split pay period that has to be calculated by hand, which defeats the purpose and introduces exactly the errors you were trying to eliminate.

Never testing the bank file until payday. Everybody says WPS compliant. The file either matches your bank's expectations with your specific employee data or it does not, and the 28th is a bad day to find out.

A checklist you can copy

Export employee list, salary history, leave balances, documents and twelve months of payslips
Confirm the export contains leave balances as data, not as a PDF report
Pick the month end cut over date and work back three weeks
Load employees into the new system
Reconcile headcount, total monthly salary and per person leave balances
Run the previous month in parallel in the new system
Compare both SIF files line by line, including SCR totals
Check the joiners, leavers, unpaid leave and salary change cases specifically
Tell employees a week ahead, in three sentences
Run the first live payroll and wait for the bank to accept it
Keep the old system for one more month
Cancel the old subscription

Common questions

How long does it take to switch HR software?

For a company of twenty to forty people, about a week of actual work spread over a month, with one payroll cycle run in parallel.

Will I lose my historical payroll data?

Not if you export before cancelling. Most systems will not let you back in once the subscription lapses, so the export has to come first.

What is the riskiest part?

The WPS file. Everything else is recoverable within a day or two. A rejected salary file on the 28th is not.

Can I switch mid year?

Yes. Gratuity accrual and leave are calculated from joining dates that travel with the employee record, so a mid year switch is fine. A mid month switch is the one to avoid.

Should I migrate historical data or start fresh?

Migrate employee records, joining dates and leave balances, because gratuity and leave both depend on them. Historical payslips can usually stay as an archived export rather than being loaded into the new system.

Keep reading

If you want a sanity check before you start, email three of your employment contracts, with employee names and ID numbers removed, to hello@officehr.ae and we will send back a short read on what they say against the Labour Law's default positions. Free, no call, and it works as a way of seeing how carefully somebody reads your documents before you trust them with your payroll.

Last checked October 2026. General operational guidance, not legal advice. Gratuity and end of service entitlements are set out in Federal Decree Law 33 of 2021, and WPS obligations should be confirmed with your WPS agent bank and MOHRE.

Try it on your own payroll.

AED 250 a month for up to 15 employees, billed yearly. Run last month's payroll in the free 30 day trial and compare the file against the one your bank accepted.

Start free trial Book a demo Talk to us