Implementing a Global HRIS in 120 Days: Data Audit, Integrations and Go-Live
A 120-day global HRIS implementation plan: clean data across entities and EORs, wire up payroll and benefits, configure GDPR and DPDP controls, and run parallel tests before the old system goes dark.
What a 120-Day Global HRIS Implementation Has to Deliver
The contract is signed, the vendor has sent its kickoff deck, and leadership wants the regional tools and spreadsheets gone by next quarter. In a global HRIS implementation, the configuration screens are rarely what goes wrong. The trouble starts when you merge employee data spread across three entity payrolls, two EOR portals and a contractor platform. Then you have to connect that data to payroll without breaking a pay run, while meeting privacy rules that differ in Frankfurt, Bengaluru and São Paulo.
120 days is a realistic target for a company with roughly 100 to 1,500 people in 5 to 20 countries on a mid-market platform such as HiBob, Personio, Rippling, Deel HR or Dayforce. Enterprise suites like Workday, SAP SuccessFactors or Oracle HCM commonly take six to twelve months because they need heavier configuration and a systems integrator. Under 100 people, a well-run project can often finish in six to ten weeks. If you fall outside these bands, adjust the plan before you promise a date.
The plan runs overlapping workstreams, not one long waterfall:
| Phase | Days | Key outputs | Primary owner |
|---|---|---|---|
| Scope and governance | 1–10 | Frozen scope, country data owners, payroll calendar map | Project lead, CFO sponsor |
| Data audit and cleanup | 1–40 | Field dictionary, cleansed master file, contractor split | People ops, country HR |
| Privacy and configuration | 15–60 | DPIA, role-based access, retention rules, works council sign-off | Legal/DPO, HRIS admin |
| Integrations | 31–75 | Payroll, benefits, EOR and identity feeds tested | HRIS admin, IT, payroll |
| Parallel testing and UAT | 60–105 | Reconciled payroll cycles, sign-offs | Payroll, finance |
| Cutover and hypercare | 106–120 | Go-live, old system read-only, issue log closed | Project lead |
Get three things in place before day one. Each country needs one named data owner who can actually make decisions. Scope should be frozen at core HR, org structure, time off and the payroll integration, with performance, ATS and compensation planning pushed to phase two. And you need a single calendar of every payroll cutoff in every country. Teams without one end up scheduling go-live mid-cycle.
Budget for more than the subscription. Typical 2026 market ranges are roughly $8–$30 per employee per month for mid-market platforms, $10,000–$80,000 in one-time implementation fees, and $10,000–$50,000 a year for integration middleware if you need it. These vary widely by contract, headcount and region, so get line-item quotes from vendors.
Days 1–40: Auditing Employee Data Across Entities, EORs and Contractors
HRIS data migration fails quietly. The import runs, the dashboards fill up, and three months later someone finds that German notice periods came over blank or that Indian leave balances skipped the carry-forward. A disciplined audit at the start prevents most of this.
Build a field dictionary before you touch a spreadsheet
List every field the new system will hold. For each, record the definition, format, whether it's mandatory, who owns it in each country, and which downstream system uses it. Watch for fields that mean different things in different places. "Start date" might be the contract date in one entity and the first payroll date in another. "Salary" might be annual in the UK, monthly in Brazil, and annual including statutory 13th-month pay in the Philippines. Settle each definition once and write it down.
Separate the three populations
- Direct employees of your own entities. The HRIS becomes the system of record for these people.
- EOR employees. The EOR is the legal employer and runs payroll. Your HRIS holds the operational record (manager, role, team), while contract terms and payslips stay with the provider. Decide which side owns each field.
- Contractors. Keep them in a separate worker type with no employee fields such as probation, benefits eligibility or leave accrual. Employee templates for contractors create a paper trail that can work against you in a misclassification dispute.
Cleanup checklist
- Give every worker one global ID that survives entity changes, EOR moves and rehires.
- Store legal names in local script as well as Latin characters wherever payroll or government filings need them, for example in Japan, China, Greece or the Gulf states.
- Collect only the national identifiers each country's payroll actually needs. Don't import scanned ID documents by default.
- Confirm currencies, pay frequencies and FTE percentages against the latest payslip, not the offer letter.
- Recalculate leave balances under local statutory rules and get each country owner to sign off.
- Close out leavers. Archive them under retention rules instead of migrating them as active records.
Hypothetically, say a 400-person company has entities in the UK, Germany and India plus 60 EOR employees across eight countries. Clean the three entity populations first, because they feed payroll directly. Then reconcile the EOR roster against each provider's export, and leave contractors for last.
Days 31–75: Payroll, Benefits and EOR Integrations
Payroll integration carries the most risk in the project. A broken org chart is embarrassing. A broken payroll feed means people are paid wrongly. Choose an integration pattern country by country, because a single global connector rarely covers everything.
| Pattern | Best for | Trade-offs |
|---|---|---|
| Native connector (same vendor or certified partner) | Countries where the HRIS vendor runs payroll or has a certified partner | Fastest to set up; mapping limited to what the vendor supports |
| API via middleware (e.g., Workato, Merge, Kombo) | Several payroll providers, frequent changes | Flexible and monitored; adds a subscription and needs a maintainer |
| Scheduled flat file over SFTP | Local in-country payroll bureaus, smaller markets | Cheap and dependable; one-way and batch, so errors surface late |
| Manual change report | Countries with only a handful of people | Nothing to build; relies on people and doesn't scale |
For most companies in the 100-to-1,500 range, a mix is the right answer. Use native or API feeds for the three or four largest countries and flat files or change reports for the long tail. Putting every country on live APIs within 120 days is the most common reason these projects slip.
What to specify for each feed
- Direction and ownership. Decide which system wins each field. Normally the HRIS owns job and pay data and payroll owns tax and net pay.
- Effective dating. A raise approved on the 20th that takes effect on the 1st has to land in the right period.
- Cutoff alignment. Changes made after a country's payroll cutoff should queue for the next cycle, not overwrite the current one.
- Error handling. Name the person who receives failed-record alerts and set the response time.
Benefits integrations vary even more by country. Statutory schemes such as Brazil's FGTS, India's EPF or European social security usually run through payroll and don't need their own feed. Supplemental benefits like private medical, pensions or meal vouchers often go to brokers or local providers who accept little more than monthly spreadsheets. Agree the format early.
For EOR employees, ask each provider what it can send and receive. Most offer a roster export or an API. Fewer accept inbound changes. If yours won't, changes to EOR workers still go through the provider's own workflow. Write that down so managers don't assume the HRIS updates the provider automatically.
Configuring Privacy Controls for GDPR, India's DPDP Act and Other Regimes
Privacy setup runs alongside configuration, roughly from day 15 to day 60, and should be finished before real employee data reaches production. Rules differ by jurisdiction, but the work follows the same pattern everywhere. This section describes how things generally work; have your data protection officer or outside counsel confirm decisions for each country.
The core regimes you'll likely touch
- GDPR (EU/EEA) and UK GDPR: You need a lawful basis for each category of data. A data protection impact assessment is usually expected for a new system processing employee data at scale. Transfers outside the EEA need a mechanism such as an adequacy decision, an approved framework or standard contractual clauses.
- India's Digital Personal Data Protection Act, 2023: Its rules are being phased in, so confirm the current status with counsel. Expect obligations around notice, purpose limitation, security safeguards, breach notification and erasure once the purpose has ended. Also check limits on handling Aadhaar numbers, and avoid storing them unless payroll requires it.
- Others to map: Brazil's LGPD, South Africa's POPIA, Singapore's PDPA, the UAE's and Saudi Arabia's data protection laws, and China's PIPL, which has strict requirements for cross-border transfers.
Privacy configuration checklist
- Get the vendor's data processing agreement, sub-processor list and hosting regions. Choose EU or other regional hosting if your counsel recommends it.
- Finish a DPIA or equivalent risk assessment covering every data category and every integration.
- Set role-based access so managers see only their own reports, country HR sees its own country, and compensation and health-related fields are restricted further.
- Configure retention rules per country. Payroll and tax records often must be kept for years, while some candidate and leaver data should be deleted much sooner.
- Update employee privacy notices in local languages before migration.
- Test data subject access and erasure processes before go-live.
In Germany, France, the Netherlands and several other European countries, works councils or employee representatives may have consultation or co-determination rights over systems that can monitor employee behavior or performance. That can add weeks. Bring them in during the first month, not after configuration is done.
Days 60–120: Parallel Testing, Cutover and Switching Off the Old System
Parallel testing shows that the new system produces the same payroll inputs as the old one before anyone relies on it. Most countries pay monthly, so a 120-day plan leaves room for two parallel cycles at best. Schedule the first at the earliest month-end after integrations stabilize. Wait until day 100 and you get a single cycle with nothing to fall back on.
How to run a parallel cycle
- Run live payroll from the old sources as usual.
- Generate the same period's inputs from the new HRIS and send them to a test payroll or comparison file.
- Reconcile headcount, gross pay, new hires, leavers, changes and leave taken for each country.
- Give every variance a root cause. Fix data problems at the source, not in the comparison file.
Use a strict threshold: zero unexplained variances in headcount and gross pay inputs for every country. A $40 difference you can explain is fine. A $4 difference you can't explain is a red flag, because it usually points to a mapping or effective-date bug that will grow.
Go/no-go criteria
- Every country has passed at least one reconciled parallel cycle, and the largest have passed two.
- HR, payroll, finance and a sample of managers have signed off user acceptance testing.
- Privacy controls are confirmed: access roles, retention rules and published notices.
- A rollback plan is documented, with the old system still available.
- Go-live falls right after a payroll cutoff in your largest countries.
If readiness differs, cut over in waves. Go live first in countries that passed parallel testing and hold back any that didn't. A two-week delay in one country costs far less than a bad pay run there.
Decommissioning the old system
Don't delete it. Set it to read-only for at least one full quarter of hypercare, then export archives that satisfy each country's retention rules before the license ends. Keep the final reconciliation files with the archive, because auditors will ask for them.
Use this rule for your go-live checklist: if a country hasn't produced a clean, reconciled parallel cycle by day 105, it doesn't go live on day 120. Set the date by payroll cutoffs, not by the contract renewal date.
Common questions
Is 120 days realistic for a global HRIS implementation?
For a company of about 100 to 1,500 people in fewer than 20 countries on a mid-market platform, yes, provided scope is frozen at core HR and payroll integration. Enterprise suites, heavy customization, or works council consultation in several European countries can push the timeline to six months or longer. Smaller teams can often finish in six to ten weeks.
Should the HRIS or the payroll system be the system of record?
Usually the HRIS owns people data: job, manager, compensation, contract terms and time off. Payroll owns tax, deductions and net pay. Write down which system wins for each field and enforce it in the integration so the two don't overwrite each other.
How do EOR employees fit into a new HRIS?
The EOR stays the legal employer and keeps running payroll, contracts and statutory filings. Your HRIS holds the operational record (role, team, manager, performance) and pulls roster data from the provider via export or API. Check whether each EOR accepts inbound changes, because many still require changes through their own portal.
Do we need a data protection impact assessment before go-live?
If you employ people in the EU, EEA or UK, a DPIA is generally expected for a new system processing employee data at scale. Laws such as India's DPDP Act, Brazil's LGPD and South Africa's POPIA also call for documented risk assessment and safeguards in various forms. Ask your DPO or privacy counsel to confirm the requirements for each country you operate in.
What drives the total cost of implementing a global HRIS?
The main drivers are the subscription (roughly $8–$30 per employee per month for mid-market platforms in 2026), one-time implementation fees ($10,000–$80,000 is a common range), integration middleware, and internal time spent on data cleanup and testing. More countries, more payroll providers and more custom integrations push costs up. These are indicative ranges that vary by contract and region, so get itemized quotes.
Written by the Hire Team Plus editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.