Key Takeaways
- The Navajo Nation's payroll errors trace back to legacy employee records that did not convert correctly into Dayforce, which makes this government ERP implementation a useful case study in migration risk.
- Preliminary reviews estimated that withholding variances touched 10 to 15 percent of payroll records in the first affected pay period, and smaller issues have continued into late 2026.
- Most ERP data migration problems surface in the first live payroll run, yet organizations can catch them earlier by reconciling converted records against the legacy system before go-live.
- Visible leadership accountability and steady Council oversight have kept remediation moving, which offers a practical model for any organization working through a difficult go-live.
Employees judge a new payroll system by a simple standard, and that standard is whether their paycheck is right. Since December 2025, employees of the Navajo Nation have experienced withholding errors and incorrect leave balances that the Nation's own officials traced to ERP data migration from legacy systems into Dayforce, the cloud-based human capital management platform at the center of the Nation's broader modernization program.
Ten months later, the problems have narrowed but persist, and the Navajo Nation Council continues to review payroll accuracy in public oversight sessions. That public record makes the rollout one of the clearest recent illustrations of how ERP implementation failure risk often begins with data that looked ready on paper.
Today, we are exploring what this government ERP implementation reveals about data migration risk and how leaders can reduce that risk before their own go-live.
Contemplating litigation?
We have multiple software expert witnesses available for provision of reports, depositions, and testimonies.
What Happened During the Navajo Nation's Payroll Transition
Like many tribal governments modernizing their back-office operations, the Navajo Nation is replacing an aging Financial Management Information System that had become difficult to update and integrate. The new environment pairs Microsoft Dynamics 365 Finance for financial management with Dayforce for human resources and payroll, and the program carries an expected cost of about $31 million over five years.
Dayforce went live for payroll first, and errors appeared in the pay period ending December 26, 2025. According to the Navajo Times, Controller Sean McCabe explained that a large migration had moved employee records, including tax and withholding data, from older systems into Dayforce, and that some of that data did not come over correctly. Some employees saw non-tax deductions such as housing payments go unwithheld, while others were overpaid when holiday hours were doubled.
In a February 2026 report to the Council's Naabik'íyáti' Committee, human resources leaders acknowledged that problems emerged during live operations despite refinements made during testing, and they pointed to migrated personnel records and outdated W-4 information as primary sources of error. By October, the issues had narrowed, yet a report the Council accepted in a 16-0 vote still described delayed deposits and leave balance discrepancies. That report also noted that one initial payroll file had overstated payments by about $2 million before officials caught and corrected it prior to release, as Native News Online reported.
What stands out is how consistently leadership has owned the problem in public, from a written apology to employees in the first weeks to the Controller's commitment this fall to release payroll files earlier so that staff can verify them before deposits. Speaker Crystalyne Curley summarized the standard plainly when she said the transition "must not come at the expense of employees receiving their paychecks." Nothing in the public record suggests the Nation chose the wrong platform, which moves the conversation away from ERP selection and toward the quality of the data the platform received.
Why ERP Data Migration Breaks Down in Government Organizations
Public-sector payroll carries decades of policy exceptions and hand-adjusted leave accruals, and legacy systems often store those exceptions in places that no conversion map captures. The new platform then calculates faithfully from whatever it receives, which means any flaw in the source data becomes a flaw in someone's paycheck.
Four conditions appear repeatedly when we review troubled government projects:
- Legacy records that were never cleaned: Outdated tax forms and inactive deduction codes survive for years because the old system tolerated them, and the new system applies them exactly as written.
- Rules that live outside the data: Manual workarounds, such as hand-adjusted holiday hours, exist only in staff habits and never appear in a conversion file.
- Testing that stops at load validation: Conversion testing often confirms that records loaded successfully, while only a full parallel payroll confirms that each employee's net pay matches the legacy result.
- Fixed go-live dates: Calendar constraints compress reconciliation time, as when the Navajo Nation needed January payroll to run through Dayforce to start the new tax year correctly.
Case Study
Panorama's expert witness team was retained to provide a forensic analysis and written report to the court regarding the failed implementation of a major software developer's payroll system at a government entity with more than 100,000 employees. The implementation resulted in incorrect paycheck amounts and inaccurate vacation pay calculations for an unacceptable percentage of the entity's employees.
Our analysis found that the client's project management office cycled through four project managers in three years and that the organization ignored the recommendations of its independent verification and validation team throughout the project. Senior management also pressured PMO members to vote in favor of go-live despite their concerns over unresolved issues.
Bill Baumann, Director of Expert Witness Services, described the core problem as a new system installed with no process changes, which produced an expensive replication of the old system on a new platform. That pattern appears in many of the ERP failures our team examines in litigation.
Read the full government payroll implementation case study.
Data Migration Is an Organizational Responsibility
Many organizations treat data migration as a technical task that belongs to IT and the implementation partner. In reality, the people who know which records are wrong work in the payroll and human resources departments, and their involvement determines whether converted data reflects how the organization actually pays its employees.
The Navajo Nation's experience also shows how system design and change management intersect with data. Delegate Helena Nez Begay noted that some employees start work early and cannot wait until 8 a.m. to clock in, a timekeeping constraint that human resources leaders addressed by allowing supervisors to set flexible schedules. Each gap of this kind generates correction work that competes for the same staff who are trying to stabilize the system.
When errors persist across several payroll cycles, an independent ERP project recovery assessment can separate data problems from configuration problems and give leadership a sequenced plan for correcting both.
Expert Insight
Our expert witness team has found that data conversion errors rarely originate in the conversion itself, because they usually trace back to earlier project decisions that compressed reconciliation time or left data ownership undefined. When those decisions go unexamined, disputes over responsibility follow quickly, which is when organizations turn to a software failure expert for an objective root cause analysis.
How to Reduce ERP Data Migration Risk Before Go-Live
The following steps reflect how independent advisors approach payroll and human resources data conversion on public-sector projects.
1. Assign Business Ownership of Each Data Object
Name a department leader who is accountable for the accuracy of each major data object, such as pay rates or leave balances, and give that leader sign-off authority on converted results. Ownership belongs with the people who will answer to employees when a paycheck is wrong.
2. Scope Data Readiness Before Contracts Are Signed
Data cleansing takes longer than most project plans assume, so it should be estimated and funded during planning. An independent ERP selection consultant can assess legacy data quality alongside vendor evaluation so that the migration effort appears in the budget from the start.
3. Cleanse Legacy Records Before Conversion
Refresh employee tax forms and retire inactive deduction codes in the legacy system before the first mock conversion. Cleansing data at the source is far less disruptive than correcting it through paycheck adjustments after go-live.
4. Run Full Parallel Payroll Cycles
Compare net pay for every employee across at least two complete payroll cycles, including a cycle with holiday or special pay. The Navajo Nation's Controller began parallel testing against the former JD Edwards system after go-live, and the same comparison delivers the most value when it is completed before the first live run.
5. Tie Go-Live Approval to Measurable Accuracy
Define acceptable variance thresholds in advance and give the steering committee clear authority to delay go-live when those thresholds are missed. Objective criteria protect project teams from the schedule pressure that, as our case study shows, can override unresolved concerns.
Learn More About Government ERP Data Migration
The Navajo Nation's transition shows that a capable platform and committed leadership still depend on accurate data, and the cost of any gap appears directly in employees' paychecks. Organizations evaluating ERP consulting firms for a public-sector project should look for experience in data conversion governance alongside software implementation.
Panorama's government ERP consultants help agencies and tribal governments prepare their data and their teams for go-live. Contact us below to learn more.
