How to replace disconnected HR, time and payroll systems
Map every place your team re-keys data between the systems first. Then move the employee record into one system, cut over time and payroll in phases, and run at least one parallel pay run before you trust the new numbers.
Pick the switch date from your pay calendar, not from a vendor's go-live slot. Name one person inside your organization who owns the project. Keep your old payroll records until the retention clock runs out.
That's the whole method. The rest of this post is where it goes wrong, and how to keep it from going wrong for you. The cutover worksheet at the end pulls it into one page, and the HR software implementation guide and connected HRIS guide cover the vendor side.
How do you know it's time?
You already know. You just haven't named it.
The sign isn't an old system. It's a person. Somebody on your team exports a time report, reformats it, and types it into payroll every pay period. Somebody else updates a new hire in the HR tool, then again in the payroll tool, then again for benefits. When those two entries disagree, nobody can say which one is right.
Four signs usually show up together:
- The same employee detail lives in more than one place, and each copy drifts.
- Someone re-keys or reformats time data before every pay run.
- Reports need a manual join across exports, and the answer is "close enough."
- Only one person knows how the whole chain fits together.
That last one matters most. If your payroll lead is away for a week and the process stops, you don't have a software problem alone. You have a single point of failure that software happens to sit on.
What should you map before you shop?
Map the handoffs, not the features.
Draw a simple page. List every system down the left side. The HR tool, the time clock or timesheet, the schedule, payroll, benefits, the general ledger. Then draw a line for every time data moves between two of them, and write down three things on each line. What moves? Who moves it? How often?
You'll find lines nobody remembered. A leave balance copied by hand each month. A pay rate change that lives in an email until payroll hears about it. A paper timesheet that a supervisor signs and someone else keys in.
Then mark each line as one of three things. Remove it, because one system will own that data. Keep it, because it's a real approval step. Or automate it, because it's just typing.
Take that page into every vendor conversation, including ours. Ask each vendor to show you your handoffs, not their demo data. A system that looks great on its own data can still leave you re-keying the third line down.
Write down your rules too. How you round time, how you pay overtime, which pay codes you use, who approves what. A new system will ask for them, and finding out you don't have them written down during setup is slower than finding out now.
Do you replace everything at once or in phases?
Phase it, unless your old systems force your hand.
A single big switch sounds clean. In practice it stacks every risk on one pay day: new data, new time rules, new approvals, new people learning the screens. If one thing breaks, you can't tell which.
A sequence that tends to work for employers in this range looks like this.
- Move the employee record first. People data is the foundation, and everything else reads from it.
- Add time and scheduling next, once the record is clean.
- Move payroll last, so it draws on records and time data you've already checked.
You can reorder these. A payroll provider's contract ending may force payroll earlier. But keep the principle: each step should leave you with fewer places to enter data, not more.
One more choice belongs here, and it's yours. A mid-year payroll switch means the new system needs the year-to-date totals so that year-end slips come out right. The T4 is the Canada Revenue Agency (CRA) slip that shows what you paid each employee for the calendar year, and it should cover the whole year, not only the months after you switched. Many employers prefer to cut payroll over at a year start for that reason. That's my preference as an adviser, not a rule. If you must switch mid-year, plan for the year-to-date load from day one.
How do you move the data?
Start with a clean export of your people data.
Your employee records, org structure, pay codes and leave balances usually come out of the old system as a spreadsheet. The quality of that spreadsheet decides how fast everything else goes. Fix duplicates, missing fields and inconsistent job titles before you hand it over, not after.
Three rules help.
Move people data, not every transaction. Employee records come across. A decade of old pay stubs doesn't need to. Ask each vendor where your pay history will live after the switch, and get the answer in writing.
Load year-to-date totals if you switch mid-year. That means one running total per employee per pay code, taken from your old system. Ask any vendor you're considering how they handle it.
Keep the old records. The CRA generally asks you to keep records for six years from the end of the last tax year they relate to. Before you cancel the old provider, export or archive what you'll need for that period. Records must be kept in Canada unless the CRA gives written permission otherwise, and remote access from Canada to records stored elsewhere doesn't count as keeping them in Canada. If you're a municipality or a registered charity, that permission isn't available to you at all.
Whoever loads your data, you check it. Spot-check a sample of employees against the source. Look for the ones with the most exceptions: long-term leaves, multiple pay rates, recent changes.
How do you run a parallel payroll?
A parallel payroll means running the same pay period in both the old and new systems, and comparing the results before anyone is paid from the new one.
Your old system stays the system of record. The new one runs beside it with the same inputs. Then you compare, employee by employee, gross pay, deductions and net pay.
Here is an illustrative example, not a client story. Say a new system shows net pay a little lower for one employee. You check the inputs. The old system applied a benefit deduction on the first pay of the month. The new system's rule applies it to every pay. Neither number is a bug. They're two different rules, and you've found out which one your policy actually says before the employee does.
That's what a parallel run is for. It finds the rules that live in somebody's head.
Some practical points:
- Run at least one full pay period. If you have monthly, semi-monthly and weekly groups, test each one.
- Include the ugly cases on purpose: a new hire, a termination, a leave, retroactive pay, overtime.
- Decide in advance what counts as a match. Cents, or exact to the dollar? Write it down.
- Don't switch until the differences are explained, not just small.
Terminations deserve a special note. When an employee leaves, the employer must issue a record of employment (ROE) to Service Canada. For a weekly, biweekly or semi-monthly payroll sent electronically, Service Canada's guide gives you up to five calendar days after the end of the pay period in which the interruption of earnings occurs. A cutover week is a bad time to learn that nobody owns ROEs. Put that task on the cutover checklist with a name next to it.
Who needs to own it internally?
One person, with time set aside to do it.
That person doesn't need to be technical. They need to know your business and be able to decide. Usually that's an HR or payroll lead, or a finance manager with HR responsibility. They make the calls on rules, approve the data, and decide when you're ready to switch.
Around them, a small group:
- A payroll lead who can say what the right answer looks like.
- An HR lead who knows the exceptions in the employee records.
- A finance contact who owns the general ledger side.
- A supervisor or manager or two who will use time approval every day.
- Someone from IT if you use single sign-on or need to connect other systems.
The vendor helps you learn the product. It shouldn't run your project for you. You'll know your own rules, your own calendar and your own people better than anyone outside, and the project goes faster when you set the priorities. Record the working sessions so you have the detail later, because the person who joined in month two won't have been in the room.
Give the owner real hours in their week. A project that depends on someone's spare time takes months longer than it should. And write down who covers payroll if that person is away. The chain you're replacing probably had the same problem.
Cutover readiness worksheet
Record the answer for each row before you set a switch date. Anything you cannot fill in is the next thing to settle.
| Area | What to confirm before you switch |
|---|---|
| Handoff map | One page listing every system and every line where data moves, with what moves, who moves it and how often. |
| Pay rules | Pay codes, rounding, overtime and approval steps written down and configured the way your policy says. |
| People data | Employee export cleaned of duplicates, missing fields and inconsistent job titles before it is loaded. |
| Year-to-date totals | One running total per employee per pay code loaded if you switch mid-year, so year-end slips cover the whole year. |
| Parallel run | At least one full pay period run in both systems, with every difference explained, not only small. |
| Record of employment | A named person who owns record of employment filing for anyone who leaves during cutover. |
| Old records | Old payroll records exported or archived for the CRA retention period before the old provider is cancelled. |
| Project owner | One internal owner with weekly hours set aside, and a named cover when that person is away. |
What to do this week
You don't need to choose a vendor to make progress. Do these three things.
- Draw the handoff map. One page, every system, every line where data moves.
- Write down your pay rules, pay codes and approval steps.
- Decide who owns the project and how many hours a week they have.
Then you'll know what you're asking a vendor to replace, and you can tell a good answer from a good demo.
If you'd like to see this against your own setup, Workzoom is built for exactly this shape of employer, with HR, time and payroll on one employee record. The Ktunaxa Nation Council, an Indigenous government in British Columbia, replaced a patchwork of disconnected tools, paper forms and spreadsheets in 2023, and moved onto the platform in a sequence rather than one big switchover. Bring your handoff map to a walkthrough and we'll work through how those lines would look in one system. Pricing is published at $4 per employee per month per suite, with implementation, data migration, training and support included. Payroll runs in Canada, the United States and the Bahamas. Details are on the pricing and Payroll pages.
You can have the map drawn before your next pay run.
How useful was this page?
What should we improve?
Questions about replacing HR, time and payroll systems
Workzoom handles HR, payroll, workforce, and talent on one employee record. Book a Walkthrough.
Get started
Built around your org. See it run live.
Explore your suite options, pricing and fit in a 15 to 60 minute working session. For organizations with 50 or more employees. See our minimums.












