The reason most restaurants stay on a POS they hate is fear of the switch. That fear is rational — the horror stories are real. But they're preventable. A well-run POS migration, from contract signature to live service, takes three weeks and zero hours of downtime.
Here's the playbook we run on every migration we help with. Follow it and switching becomes a boring project, not a crisis.
Phase 1: Pre-flight (Week 1)
1. Audit what you have
Before you pick a new platform, document exactly what your current stack does. Include:
- Menu items and modifiers (export CSV from current POS)
- Current hardware (terminals, kiosks, KDS, printers, readers)
- Integration points (online ordering, loyalty, SMS, gift cards, third-party delivery)
- Guest database (names, emails, phones, visit history)
- Gift card liability (outstanding balance)
- Loyalty point balance (total points owed to members)
- Current processing contract (ETF? auto-renewal? expiration?)
2. Pick the right cutover window
The best cutover is during your weakest sales day of the week, ideally during a slow week. For most independents that's a Monday or Tuesday. Avoid weekends, holidays, and event weeks.
3. Get buy-in from the whole team
Staff resistance is the most common cause of migration failure. Get your GM, chef, and lead servers involved in the evaluation. If they feel ownership, training goes 5x faster.
Phase 2: Data migration (Week 2)
Menu import
Export your full menu from the old POS. Most platforms can import via CSV; some (Labrador included) can auto-parse your online menu. Key checks:
- All modifiers imported with correct pricing
- Tax categories correct
- Kitchen routing rules correct
- Daypart pricing (happy hour, lunch specials) correct
Test by ringing up 20 representative orders. Fix any discrepancies before go-live.
Guest database migration
Export guest data from old POS. Import to new. Verify:
- Names match
- Phone numbers formatted consistently
- Email opt-ins preserved (important for compliance)
- SMS opt-ins preserved (if you're keeping the same subscriber base)
Gift card liability transfer
This is the most-missed step. Your old POS has a total gift card balance outstanding; your new system needs to know those balances. Two paths:
- Full import: export gift card codes + balances from old POS, import to new. Old cards work at new system. Best guest experience.
- Lookup table: old cards still redeem via old system (read-only), new cards issued by new system. Acceptable but adds friction.
Loyalty balance transfer
Same pattern. Export member list + point balances. Import to new platform. Communicate to members: "your points carried over, here's your new account."
Phase 3: Staff training (Week 2–3)
Manager training first
Your GM and assistant managers should be 100% proficient on the new system before any staff sees it. Two 3-hour sessions with the new platform's onboarding team is usually enough.
Staff training in two rounds
Round 1 (day before cutover): 1-hour group session. Every team member rings 5 practice orders.
Round 2 (morning of cutover): 30-minute floor huddle. Review hot keys, refunds, voids, and the escalation path for anything unexpected.
A cheat sheet on every terminal
Print a laminated one-page cheat sheet with the 10 most common functions (new order, add mod, comp item, void, split check, close check, pay, refund). Tape it next to each terminal for the first week.
Phase 4: Cutover day (Week 3)
Monday morning, 8 AM
- Both systems live: old system for closing out any pending tabs; new system for new orders.
- Menu printed, laminated, at every terminal.
- Owner or GM on the floor the entire shift.
- Vendor support team on standby (Slack or phone).
End of Monday
- Close out any remaining tabs on the old system.
- Reconcile day-end reports between old and new.
- Team debrief: what was hard, what was easy, what fixes for tomorrow.
Week 4: Stabilization
Issues will surface in week 4. Menu edge cases, modifier mistakes, report discrepancies. Log every one. Fix daily.
Common migration failures (and how to avoid them)
Failure: Menu imports with wrong modifier pricing
Prevention: ring 20 test orders before go-live. Flag any $0.00 modifier and fix.
Failure: Gift card holders feel ripped off
Prevention: email every gift card holder a week before cutover. "Your card still works. Here's what changes." Transparent communication prevents complaints.
Failure: Staff sabotage via "the old system was better"
Prevention: involve them in evaluation. Name who led the decision. Be honest that every system has tradeoffs.
Failure: Online ordering link broken on Google Business
Prevention: update your Google Business Profile ordering link the morning of cutover. Also update any Yelp, Instagram, and Apple Business Connect links.
ETF considerations
If your current POS has an early termination fee (common with Toast, SpotOn, Revel), calculate:
- Monthly savings from new platform × months remaining on contract
- vs. ETF cost
If savings > ETF, migrate now. If savings < ETF, wait until closer to renewal.
Bottom line
POS migration is a three-week project with a playbook. The horror stories happen when restaurants wing it. The boring migrations happen when someone runs the process. You can run the process.
Want help running it? Book a demo and we'll walk through a migration plan tailored to your current stack.