When contractors think about what an ERP migration might put at risk, job cost history usually comes to mind first. Payroll rarely does, right up until someone needs three, five, or seven years of certified payroll detail and discovers it didn’t survive the move.
That’s the landmine. Not because payroll is complicated to migrate technically, but because almost nobody asks the payroll history question before the migration happens, and by the time it matters, it’s too late to go back and get the detail that didn’t come along.
It’s worth being specific about why this particular gap is so easy to miss. Payroll feels like a solved problem once current employees are being paid correctly in the new system. Nobody’s watching for a gap in three-year-old certified payroll records the way they’re watching for an error in this week’s paycheck. The risk is real, but it’s invisible on exactly the timeline most people are paying attention to.
Why payroll history keeps coming back to matter
A handful of recurring situations all require exactly the kind of payroll detail a balance-forward migration leaves behind.
Certified payroll audits. Public works and prevailing wage projects require certified payroll records, and those records don’t have a statute of limitations that conveniently expires the moment you switch accounting systems. A Department of Labor audit or a project owner’s compliance review can reach back years after a job closed out, asking for the same level of detail, by employee, by classification, by week, that was required when the work was performed.
Union reporting reconciliations. Union payroll comes with its own reporting cadence: hours, contributions, classifications, fringe benefit allocations, all tracked against agreements that get referenced and re-checked well after the fact. A local’s audit of contribution history doesn’t care which accounting system was in place when those hours were worked.
Prevailing wage compliance reviews. Similar story. Prevailing wage determinations and the payroll detail proving compliance with them are exactly the kind of records that get pulled during a dispute, a complaint investigation, or a routine compliance check, sometimes years after the project wrapped.
Workers’ comp lookbacks. Workers’ comp claims, especially long-tail claims involving repetitive stress or occupational exposure, can require payroll and classification history going back years to establish exposure, job classification, or wage basis at the time of injury. That history needs to be complete and accurate, not reconstructed from memory after the fact.
What actually happens in a balance-forward migration
A balance-forward migration moves current payroll setup: active employees, current classifications, current tax tables. It doesn’t move the detailed history underneath that setup, the week-by-week certified payroll records, the historical union contribution detail, the classification history tied to specific jobs and specific pay periods.
None of that shows up as a problem at go-live. Payroll runs fine in the new system. The gap is invisible until someone needs a specific record from three years before the migration and finds out the detail either didn’t move, or moved as a flattened summary that doesn’t satisfy what an auditor or a union actually needs to see.
A realistic scenario
Picture a mid-size contractor that migrated off Sage 300 CRE two years ago. The migration went smoothly by every measure anyone was tracking at the time: go-live happened on schedule, current payroll ran correctly from day one, nobody flagged an issue.
Then a prevailing wage compliance review lands, covering a public project completed four years ago, two years before the migration. The contractor needs certified payroll records for that project: hours, classifications, and wages by employee, by week. That data lived in the old system, and the migration only carried forward current balances and active employee setup, not the full historical payroll detail tied to closed-out jobs.
Now the company is trying to reconstruct records from an old system that may no longer be easily accessible, or worse, was decommissioned entirely once the new system was live. What should have been a routine records request becomes a scramble, and depending on what can and can’t be recovered, potentially a compliance problem that has nothing to do with whether the actual work was done correctly. It only has to do with whether the records proving it still exist.
That scenario isn’t rare. It’s the predictable outcome of treating payroll as “it just needs to run” during a migration instead of asking how far back the historical detail needs to reach, and whether the migration is actually built to carry it.
Why this specific gap gets missed so often
Job cost history tends to get more attention during migration planning because it shows up in conversations about WIP, bonding, and project profitability, topics that are already part of how contractors and their advisors think about risk. Payroll rarely gets the same scrutiny, for a fairly simple reason: as long as current employees are getting paid correctly, payroll looks like it’s working.
That’s true and also beside the point. Whether payroll runs correctly today says nothing about whether historical payroll detail from three or five years ago made the trip intact. The two are evaluated on completely different timelines. Current payroll gets checked every pay period. Historical payroll detail usually only gets checked when something outside the company’s control, an audit, a claim, a compliance review, forces the question. By then, the migration is long finished and any gap in what carried forward is no longer a design decision. It’s a fact that has to be dealt with.
The question worth asking before it’s your scenario
How many years of certified payroll, union reporting, and prevailing wage detail does your company actually need to have on hand, given your project mix and your compliance exposure? For most contractors doing any public works or prevailing wage work, the honest answer is longer than they’d assumed, often three to seven years depending on the specific compliance requirement and any active claims or disputes.
That’s not a question most migration conversations get to, because it’s not the question that shows up on a platform comparison or an implementation timeline. It’s a data question, and it deserves to be answered before the migration, not discovered afterward when an auditor asks for something that isn’t there anymore.
What to actually check before you migrate
A few concrete questions are worth answering before any migration timeline gets set, regardless of which platform you’re moving to.
How many active certified payroll or prevailing wage projects have closed out in the last seven years, and is the full weekly detail for each one still accessible in your current system? Not summarized, the actual employee-level detail an auditor would ask for.
If your company does union work, how far back does your contribution and classification history need to go to satisfy a local’s audit rights under your current agreements? This varies by union and by agreement, so it’s worth confirming rather than assuming a standard number applies.
Does your workers’ comp carrier or your legal counsel have a standard lookback period they’ve asked for in past claims? If so, that’s a real, specific number to plan around rather than a general sense that “a few years” should be enough.
Has your implementation partner’s proposed scope explicitly addressed historical payroll detail, or does it only cover current employee setup and go-forward payroll processing? This is worth asking directly, in writing, before a contract is signed, not assumed based on a general conversation about “migrating payroll.”
Answering these doesn’t require picking a platform first. It’s diagnostic work that should happen regardless of where you’re migrating to, because the risk lives in the data, not in the destination system.
Where Pre-Flight Analytics fits
TransformerIQ’s Pre-Flight Analytics assessment includes a payroll history risk scan as part of its free, no-commitment read on your data. Instead of assuming payroll history will just carry over because “it’s just payroll,” the assessment looks specifically at how much certified payroll, union, and prevailing wage detail exists in your current system and what a full-history migration would need to preserve to keep that record intact. It’s the same diagnostic step worth taking regardless of which platform you eventually choose, and it answers the payroll question on your own timeline instead of an auditor’s.
Start a free Pre-Flight Analytics assessment at app.transformeriq.com and find out whether your payroll history is actually migration-ready, before an audit is the one asking.