Which records should you migrate when moving tip pooling from spreadsheets to software?

Why the switch is a records risk

Most restaurants that run tip pooling on spreadsheets have a history that lives in a dozen files across two or three laptops, a shared drive, and a manager's email. When a new tool goes live, attention moves to the new system and the old files quietly stop being maintained, backed up, or even findable. Then a former employee files a wage claim eighteen months later, or a state auditor asks for tip records for a period that predates the switch, and the answer is a shrug. The switch itself is fine; losing the history is the problem. Related: What should restaurants understand about tip pooling rules before starting one?

The legal expectation is that records supporting wage calculations exist and can be produced. Federal rules require payroll records to be kept for at least three years and the underlying computation records for at least two, and several states require longer. Tip pool records are computation records: they show how each person's tip income was derived. A new tool will generate them going forward, but it will not recreate the past unless you bring the past with you or preserve it somewhere reliable. Related: When should pooled tips be paid out nightly in cash versus through payroll?

Keep reading: How do you set up a fair tip pool that the whole team trusts?, Should you split tips by hours worked or by role-based points instead?, Why should you keep transparent tip records for every single shift?. See how TipPoolr helps you tip pooling and fair gratuity distribution.

The records that must come with you

Start with the per-shift split records: for each shift, the pool total, the participants, their hours or points, any tip-outs applied, and each person's resulting share. This is the core evidence of how tips were distributed, and it is the first thing a claimant or auditor will ask for. Export it in a flat format (one row per person per shift, with the date, name, role, hours, and share) rather than as the original formula-laden spreadsheet, because a flat file is readable by any tool and does not depend on formulas that may break. Related: How do you set up a fair tip pool that the whole team trusts?

Next, the policy documents: the written tip pool policy in every version that applied, with the dates each version took effect, and any signed acknowledgments from staff. Then the reconciliation records: nightly card tip totals from the point-of-sale system, cash tip counts, and the payroll tip lines, so the split records can be tied back to money that actually moved. Finally, any dispute records, corrections, and the notes explaining them. If a share was adjusted after the fact, the reason should survive the migration alongside the number. Related: Why should you keep transparent tip records for every single shift?

What to keep in its original form

Do not throw away the original spreadsheets after exporting. Keep them as read-only archives, with the folder structure and file names intact, because the export may drop details (comments, cell notes, a highlighted row with a manager's explanation) that turn out to matter. Store the archive in at least two places, one of which is not a single person's laptop. A shared drive folder with restricted edit rights and a periodic backup is enough for most restaurants.

Keep the point-of-sale exports and payroll reports for the same periods in their original form too. The value of these records is in cross-checking: the split says a server earned a certain amount on a given night, the point-of-sale report shows the tip total that night, and payroll shows the tip line for that period. When all three exist independently and agree, you have a strong record. When only one exists, you have a claim. Write a one-page index that says where each type of record lives and which date ranges it covers, so anyone can find it without you.

Running the transition without a gap

Pick a clear cutover date, ideally the start of a pay period, and run both systems in parallel for at least one full pay cycle. Calculate the splits the old way and the new way, compare every person's share, and investigate any difference before trusting the new tool. Differences usually reveal an unstated rule in the spreadsheet (a rounding habit, a manual adjustment someone always made) that needs to become an explicit setting in the new system or be consciously dropped.

Once you are confident, freeze the old spreadsheets, load any historical data the new tool can import, and tell staff what changed and where they can see their shares now. If you are evaluating tools, ask specifically how they export your data in a plain format if you ever leave, because the same problem repeats in reverse; a tool that locks your history is a risk you are adding, not removing. That is a question we took seriously when building TipPoolr, and it is one we would tell you to ask any vendor.