Switching billing tools mid-project (without breaking your pay app history)
Nobody switches billing systems on a clean slate. The moment you realize the spreadsheet is a liability is always mid-project, application 7 of 14, retainage half-tracked, one formula quietly broken since spring. The good news: switching mid-project is completely doable if you respect one principle.
The principle: certified history is sacred
Your next pay application’s “previous applications” column must equal the certified totals of everything that came before, per line, to the penny. Whatever tool you move to must reproduce that history exactly, because the GC’s records will be checked against it. A migration that’s off by $12 doesn’t produce a $12 problem; it produces a rejected application and a credibility problem.
The mid-project migration, step by step
- Collect the certified record. Every prior application as certified (not as submitted). If the GC cut amounts, the cut figures are your truth. Missing certificates? Request copies, GCs have them.
- Rebuild the SOV as it stands today. Original lines plus every approved change order as its own line/adjustment.
- Backfill period by period. Enter each prior period’s certified line amounts in order, don’t just lump “previous = $312,450” into one bucket. Per-period history is what makes retainage, stored-material balances, and percent-complete audits work.
- Reconcile three totals against your last certified application: total completed & stored, retainage held, and balance to finish. All three tie, or you stop and find out why before billing.
- Run the next application from the new system, and keep the old spreadsheet frozen as an archive, not a parallel system. Two sources of truth is how the mess started.
What to look for in the destination tool
- A real backfill path (mid-project onboarding as a first-class feature, not “start a new project”)
- Certified-vs-applied tracking per period
- Retainage that recomputes correctly across the backfilled history
This is, candidly, the exact scenario Misthora is being built around, mid-project onboarding from Excel is our main path, not an edge case. Until it ships, our free template follows the same structure, so a mid-project move into it (and later, out of it) follows the five steps above.