An HRIS implementation moves your people data, documents and HR processes into a new system. It runs in six phases: scope, setup, data migration, payroll integration, adoption, and launch. Payroll stays the source of truth for pay, tax and super. The timeline depends mostly on your data and your team’s availability, so clean data early and phase the launch.

Key takeaways

• An HRIS implementation is a data, process and people project first, and a software project second.
• Australian employers must keep time and wages records for 7 years, according to the Fair Work Ombudsman, so migrated history has to stay complete and accessible.
• According to the ANAO, Defence’s PMKeyS project exceeded its $25.0 million budget by $38.4 million, or more than 150 per cent.
• Prosci found 88% of projects with excellent change management met or exceeded objectives, against 13% with poor change management.
• Keep payroll where it is, integrate the HRIS with it, and test the connection before a live pay run.

What does an HRIS implementation actually involve?

An HRIS implementation configures a new HR system around your organisation, loads your people data, connects payroll and other tools, and gets staff using it. Most of the effort sits in data, decisions and communication rather than in the software. Payroll usually stays where it is, with the HRIS integrated alongside it.

Suppose you run HR for 400 people across three sites, with records split between a payroll system, a shared drive and a filing cabinet. An implementation brings those records into one place, turns your paper forms into workflows, and gives managers and employees self-service access. It also decides who can see what, which is a bigger job than it sounds.

The scope question matters because an HRIS and payroll software are different systems of record. An HRIS holds the employee record, onboarding, documents, leave requests and performance, while payroll calculates pay, tax and super. If you are unsure where the line sits, the difference between HRIS and payroll is worth settling before you scope anything.

The fear at this stage is usually that the project will drag on for months, or that your team will end up configuring everything alone. Both are fair questions to put to a vendor, and the answers vary widely. So the rest of the process is about making those two risks visible early, rather than discovering them in week eight.

How long does an HRIS implementation take?

An HRIS implementation takes as long as its slowest dependency, which is rarely the software. Headcount, entities, payroll systems, data quality, modules in scope, and your own team’s time all set the timeline. Ask each vendor for a phased plan with dates tied to your size.

A single published duration is not much use, because two organisations of the same headcount can differ enormously. For example, one business of 300 staff has clean payroll data and one entity. Another has three entities, two payroll systems and contracts stored as scanned PDFs, so its data phase alone could take longer than the first business’s whole project.

Large public sector projects show what happens when scope and data are left loose. According to the Australian National Audit Office, Defence’s PMKeyS personnel system was due by June 2000. Instead, Phase 2 components rolled out between 75 and 158 weeks late. When the project closed in December 2002, major Phase 3 and 4 outcomes were still undelivered. A mid-market rollout is far smaller, yet it slips for similar reasons: unclear scope, poor records, and too many parties with no single owner.

What speeds an implementation up?

Three habits shorten most projects, and none of them needs extra budget. First, name one internal owner with time set aside, because a project that waits on replies moves at the speed of your inbox. Second, clean, map, and check the data before it moves rather than after. Third, phase the launch, so onboarding and the employee record go live first while performance reviews and extra integrations follow later.

What are the phases of an HRIS implementation?

Most HRIS implementations follow six phases: scope and kickoff, system setup, data migration, payroll and other integrations, adoption and training, and launch. Each phase has a clear completion test, such as people imported and spot-checked or onboarding tested end to end. Moving on only when that test passes keeps the project honest and the timeline real.

Phase 1: Scope and kickoff

Agree the modules in scope, the launch audience, the target go-live date and who owns each decision. Write down what is out of scope too, because an unwritten “later” tends to become “now” halfway through. A short kickoff with HR, payroll, and IT in the room settles most of these questions quickly.

Phase 2: System setup

Set admin roles and permissions, add locations and time zones, and import positions to build the org chart. Permissions deserve real care, since salaries, bank details and medical notes will soon sit in one system. For instance, decide early whether site managers see pay rates, rather than fixing it after someone notices.

Phase 3: Data and documents

Prepare the people import file, validate the required fields, then import and spot-check the records. Alongside this, upload contract templates, policies, and job descriptions so the system can track acknowledgements.

Phase 4: Integrations

Connect payroll first, then any rostering, recruitment or learning tools in scope. Test each connection with real records in a controlled way before anything touches a live pay run.

Phases 5 and 6: Adoption and launch

Train admins and managers, test the onboarding flow by hiring one real person through it, and run a pre-launch check of configuration, data, integrations and communications. Only then invite existing employees, so the first impression most staff get is a system that already works.

How do you migrate employee data into a new HRIS?

Migrating employee data means extracting records from payroll, spreadsheets, and files, then cleaning, mapping, and importing them in stages. Clean the data before you move it, never after. Keep historic records complete and accessible, because Australian record-keeping obligations do not pause for a system change.

According to the Fair Work Ombudsman, employers have to keep time and wages records for 7 years. Those records must stay readily accessible to a Fair Work Inspector, and they cannot be changed except to correct an error. So a migration that drops old leave history, or quietly edits it during the import, creates a compliance problem rather than a tidier database.

The cost of weak data shows up years later. According to the ANAO, the 2003-04 Defence financial statements carried a $1.23 billion audit limitation of scope on employee leave. The ANAO linked it to historical leave record deficiencies and PMKeyS data integrity failings. A new system did not fix old records; it carried them forward.

A practical migration sequence

• Extract employee details, positions, managers and employment history from every current source.
• Clean duplicates, missing start dates, inconsistent job titles and people who left years ago.
• Map each field to the new system, including custom fields for licences, visas or award coverage.
• Import a sample of 10 to 20 people first, check them against the source, then load the rest.
• Keep the originals in a secure archive, since the old system may be the only copy of some history.

Consider a single scenario: a manager’s name is spelt two ways across two spreadsheets. The import creates two managers, and half the team’s leave requests route to a person who does not exist. That is why the sample import comes first.

How do you connect a new HRIS to payroll without breaking it?

Connect the HRIS to your existing payroll rather than replacing payroll during the same project. Payroll stays the source of truth for pay, tax and super, while the HRIS feeds it new starters, changes and approved leave. Test the integration outside a live pay run, then check the first real pay run line by line.

Payroll carries your tax reporting, so it is the system you least want to disturb. According to the Australian Taxation Office, you can send Single Touch Payroll information directly from your payroll software after each pay run. Keeping payroll in place therefore keeps STP reporting where it already works, while the HRIS takes on the HR work around it.

The ANAO’s 2013 better practice guide on HR systems makes the same point from a controls angle. It recommends testing system changes before they reach production, including data exchanged with other applications. In practice, that means a test pay run or a parallel run before anyone relies on the new connection.

Questions to ask about the payroll connection

Start with which direction each field flows, what happens when the two systems disagree, and who fixes a failed sync. Then check how approved leave reaches payroll and whether balances come back. Find out too which payroll systems the vendor connects to directly, as opposed to through a third-party connector or an API someone has to build. Direct payroll integrations and connector-based links are different promises, so get the answer in writing.

How do you get staff and managers to actually use the new system?

Adoption comes from training, clear communication and making the new system the only way to do routine tasks. Managers need to understand what they now approve and why. Employees need a short, specific reason to log in, such as updating bank details or requesting leave, followed by support while the change is new.

The evidence for investing here is strong. Prosci’s Best Practices in Change Management research surveyed more than 2,600 change practitioners. According to Prosci, 88% of projects with excellent change management met or exceeded objectives. Only 13% with poor change management did the same, so excellent change management made a project roughly seven times more likely to meet its objectives.

The ANAO guide also names a quieter risk. Managers may see self-service as a transfer of admin onto them, and employees may resist changing a process that seemed to work. So the guide recommends training, a communication plan, user acceptance testing, and a kit for managers with support contacts.

A simple adoption plan

Brief managers a week before staff, so they can answer questions rather than ask them. Then launch with one or two high-value tasks, for example digital onboarding for new starters and leave requests, and retire the old paper form on the same day. Finally, track logins and outstanding tasks for the first month, and follow up with teams who have not started.

What should an HRIS implementation checklist include?

An HRIS implementation checklist should cover scope, setup, data, integrations, adoption and launch, with an owner and a completion test for each item. Used as a project plan template, it lists the tasks, assigns each one to a named person, and sets a date.

• Scope: modules in scope, launch audience, go-live date, decision owners, and what is out of scope.
• Setup: admin roles, permissions, locations, time zones and the org chart.
• Data: extraction, cleaning, field mapping, a sample import, and a full import checked against source.
• Documents: contract templates, policies, job descriptions and compliance paperwork uploaded and assigned.
• Integrations: payroll connected and tested outside a live pay run, then any other tools in scope.
• Onboarding: one real new starter taken through the full flow before launch.
• Adoption: manager briefing, staff communication, training materials and a support contact.
• Launch: pre-launch check passed, staff invited, old forms retired and first-month follow-up scheduled.

A checklist only helps when it stays current, so keep it somewhere HR, payroll and the vendor can all see, and review it at every weekly check-in.

How do you choose who runs your HRIS implementation?

Choose between running the implementation yourself, having the vendor run it, or hiring a consultant. The right choice depends on your capacity, the complexity of your data, and how much configuration you want to own. Whichever you choose, get the plan, the scope and the responsibilities in writing before you sign.

Running it yourself suits a team with a spare HR systems person and simple data. A consultant suits a large or multi-country rollout with many integrations, although it adds a third party to every decision. By contrast, a vendor-run project suits most mid-market teams without spare capacity, provided you know exactly what the vendor does and what stays with you.

So ask each vendor four direct questions before you sign. Who is my named implementation contact, and who extracts and loads the data? Which templates and workflows does the vendor build? Finally, what must my team supply, and by when?

If you want the setup done for you, Worknice’s implementation service suits mid-market Australian organisations keeping their existing payroll. Every customer gets a dedicated implementation manager, and the team extracts data from existing systems, builds contract and paperwork templates, and sets up workflows. However, an organisation that wants its HRIS to run payroll may prefer an all-in-one platform. Similarly, a multi-country enterprise rollout may suit a systems integrator better.

Frequently asked questions

How long does an HRIS implementation take?

It depends on headcount, the number of entities and payroll systems, the state of your data, the modules in scope and your own team’s availability. Data preparation is usually the longest phase. Ask each vendor for a phased plan with dates tied to your size, and treat any single figure without those variables as a guess.

What is the first step in an HRIS implementation?

The first step is agreeing scope: the modules going live, the launch audience, the target date and who owns each decision. Write down what is out of scope as well. A short kickoff with HR, payroll and IT together settles most of these questions and prevents scope growing quietly halfway through the project.

Do I need to change payroll when I implement an HRIS?

No. Most mid-market organisations keep their existing payroll and integrate the HRIS with it. Payroll stays the source of truth for pay, tax, super and Single Touch Payroll reporting, while the HRIS handles the employee record, onboarding, documents and leave requests. Test the integration outside a live pay run before relying on it.

What should an HRIS implementation checklist include?

It should cover scope, system setup, data migration, documents, integrations, onboarding, adoption and launch. Give every item a named owner, a date and a completion test, such as people imported and spot-checked against the source. Keep the checklist where HR, payroll and the vendor can all see it, and review it weekly.

Why do HRIS implementations fail?

Most fail on people and data rather than software. Common causes are unclear scope, poor source records, no single internal owner and weak change management. According to Prosci, only 13% of projects with poor change management met or exceeded objectives, against 88% of projects with excellent change management.

About the author

Graham Martin is Co-founder of Worknice, an Australian HRIS built for mid-to-large organisations. He has spent more than a decade working with Australian People and Culture teams on HR systems, compliance and payroll integration.

Related reading

• Why companies replace Employment Hero: what teams switching systems look for, and what pushes them to move.
• Choosing an HRIS for 100 to 500 staff: the selection questions to settle before implementation starts.
• What an HRIS is in Australia: the category explained, including where it stops and payroll begins.

Sources

1. Fair Work Ombudsman. “Record-keeping.” Retrieved 23 September 2026. https://www.fairwork.gov.au/pay-and-wages/paying-wages/record-keeping
2. Australian National Audit Office. “Management of the Personnel Management Key Solution (PMKeyS) Implementation Project.” Auditor-General Report No. 8 of 2005-06, published 26 August 2005. Retrieved 23 September 2026. https://www.anao.gov.au/work/performance-audit/management-the-personnel-management-key-solution-pmkeys-implementation-project
3. Australian National Audit Office. “Human Resource Management Information Systems: Risks and Controls.” Better Practice Guide, June 2013. Retrieved 23 September 2026. https://www.anao.gov.au/sites/default/files/2013_ANAO_BPG_HRMIS.pdf
4. Australian Taxation Office. “How to report Single Touch Payroll data.” Last updated 5 November 2023. Retrieved 23 September 2026. https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll/how-to-report-single-touch-payroll-data
5. Prosci. “The Correlation Between Change Management and Project Success.” Published 7 June 2023, updated 21 May 2026. Retrieved 23 September 2026. https://www.prosci.com/blog/the-correlation-between-change-management-and-project-success