Switching your POS without losing a shift
The system is rarely what fails during a switch. What fails is a menu somebody typed in wrong and nobody in the building on the night it goes live. This page is the whole playbook: the order of operations, the data to extract before you give notice, the physical prep the building needs, and the commitments to get from your new vendor in writing. Work it top to bottom and the switch is a project; skip around and it is a gamble.
Judd Alsup and the Equip Payment Solutions team, who install and support restaurant POS systems nationwide and sell Shift4 Dine and Clover.Updated August 9, 2026. Sources and dates cited on every figure.
The short answer
Switching POS without losing a shift, in order:
- Read the contract first notice window, termination fee, and the separate hardware lease that outlives most agreements.
- Export everything while access is friendly menu, sales history, customers, gift card balances signed off in writing.
- The menu build is the long pole built by the vendor, reviewed on a screen share, kitchen tickets checked on your hardest items.
- Go live on a slow night vendor physically present, old terminal still on the counter until a full service has run.
The rest of this page is the case for each line, with sources.
The order that works
Read the contract before you shop
Notice period, termination fee, and whether the hardware is a separate lease with its own end date. This decides whether you are switching now or in eight months.
Get your data out first
Menu, sales history, customer records, gift card balances. Confirm export formats before you give notice.
Menu build is the long pole
Every item, modifier, combo and tax group, then tested. It should be done by your vendor and reviewed by you on a screen share. If a vendor hands you a spreadsheet, that is the whole warning.
Pick the night deliberately
A slow night, with your vendor physically present, and the old system still on the counter until the new one has taken a full service.
The data to take with you, item by item
The menu, in a structured export
Items, prices, modifiers, combos and tax groups, ideally as a spreadsheet rather than a PDF. Even when the new vendor rebuilds from scratch, the export is the authoritative reference that keeps the rebuild honest, and it is dramatically easier to obtain before you give notice.
Sales history, as deep as the system allows
Two years if you can get it. Daypart curves, seasonal patterns and item performance drive scheduling and purchasing on the new system, and they are the first thing you lose when the old account closes. Export to CSV and keep it somewhere boring and safe.
Customer records and marketing lists
Names, contact details, order history and any consent records for marketing. Ask specifically what format the export takes and whether consent status survives it, because a marketing list without consent history is a liability, not an asset.
Gift card and loyalty liabilities, as a signed-off number
Get the outstanding balance report the day you switch, in writing, and reconcile it against what the new system loads. This is real money owed to real customers, and the switch is the only moment it can silently shrink without anyone noticing.
House accounts and standing arrangements
The catering client on net 30, the church group's standing Tuesday order, the neighboring office's tab. These live in nobody's export and everybody's memory. Write them down before go live, because the new system only knows what someone tells it.
Gift cards are the thing people forget
Outstanding gift card balances are a real liability and they do not always migrate. Ask specifically how balances transfer, whether old cards keep working, and who eats the difference if they do not.
The same goes for loyalty balances and any house account arrangements. Sort these before the switch, not during.
The week by week shape of a clean switch
Weeks one and two: paperwork and data
Read the old contract, calendar the notice window, give notice if the math says go, and pull every export while you still have friendly access: menu, sales history, customer list, gift card liabilities. Access to a system you are leaving has a way of getting slower after notice.
Weeks two and three: the menu build
Every item, modifier, combo, price and tax group, built by the new vendor and reviewed by you on a screen share, section by section. Insist on seeing the kitchen ticket for your five most complicated items, because that is where builds fail: the food is right on the register and wrong on the pass.
Week three: training by shift, not by memo
Every shift gets hands on time before go live, on the real menu, including the closers who will meet the system at its worst. The manager functions, comps, voids, splits and refunds, get rehearsed until they are boring. A laminated cheat sheet by the register beats a PDF nobody opens, and the person who wrote it learns the system best of anyone in the building, which is worth choosing deliberately.
Go live: a slow night, staffed like it matters
Tuesday, not Friday. Your vendor physically in the room, the old terminal still on the counter, a fallback plan written down. Run the whole service on the new system, reconcile the close against expectations, and only then let the old system leave the building.
The week after: read the reports against reality
Ticket times, voids, tax totals, tip distributions. The first week's reports are where quiet build errors surface, a wrong tax group or a mispriced modifier, and they are cheap to fix now and expensive to fix at quarter end.
The physical layer, which nobody budgets and everybody hits
Count your drops before the install date
Every terminal, printer and kitchen screen needs power and, for most, a network drop. Old buildings hide their shortages until install day, and an electrician booked in a panic costs double. Walk the room with the new vendor's hardware map two weeks out.
The network is part of the POS now
A cloud system is only as reliable as the router feeding it. A dedicated router for the POS network, separate from the guest wifi, is the single cheapest reliability upgrade in the building, and several vendors, ours included, ship one in the standard kit.
Old hardware has an afterlife problem
Locked devices brick, leased devices go back, and owned devices from the old system rarely work on the new one. Confirm what must be returned, in what condition, by when, because equipment return clauses carry fees the size of the termination fee.
Do not schedule the switch against the building
Not during the patio buildout, not the week the hood gets replaced, not while the parking lot is torn up. A POS go live consumes the whole building's attention for a night; give it a night when nothing else wants that attention.
What the vendor owes you during a switch, in writing
A switch is the moment of maximum vendor motivation, which makes it the moment to get commitments in writing: who builds the menu and by when, who is present on go live night, what training is included, how gift card balances transfer and who absorbs shortfalls, and what the support response looks like in week one. Every one of those is a promise a motivated salesperson will make verbally; the ones that survive being written down are the ones that were real.
Our own answers, for the record: we build and test the menu, we are in the room on go live night, training across every shift is included, and none of it is a line item. That standard is not heroic, it is what the purchase should include, and any vendor's reluctance to match it in writing is the most useful demo you will get.
The deeper reason to insist on all of this: a switch is the one moment you meet a vendor's real operations instead of its sales operation. How the menu build is handled, whether the install crew shows up configured, how week one's support tickets get answered: this is the relationship you are actually buying, previewed in miniature. A vendor who fumbles the courtship was never going to improve after the wedding, and a vendor who runs a clean switch has told you something no comparison table can.
Questions owners ask
How long does the whole thing take?
Typically a few weeks, and the driver is menu complexity rather than hardware. A large menu with deep modifiers takes longer to build and test properly.
Can I run both systems at once?
For a night, yes, and we usually recommend keeping the old terminal on the counter until the new one has run a full service.
When is the best time of year to switch?
Your slowest season, with your renewal notice window as the constraint that overrides preference. A January switch beats a December one for almost every room in America, and missing the notice window can cost you a full auto renewed term, which makes the calendar date the first thing to find, not the last.
What is the biggest switching mistake you see?
Letting the outgoing processor's hardware lease outlive the relationship. The POS agreement ends, the separate equipment lease does not, and the owner pays monthly for a bricked terminal in a closet. Read the hardware paper as carefully as the software paper, every time.
Should staff know about the switch in advance?
Yes, early and specifically, because staff resistance sinks more go lives than technology does. Tell them what changes for their job: how they clock in, how tips declare, how splits work, and put the fastest skeptic on the training schedule first. A crew that helped test the menu build defends the new system on night one; a crew that met it at five p.m. on go live day blames it for everything including the weather.
What should I do in the last hour before go live?
Ring a full test order of your five most complex items and void it, run one real card for a dollar and refund it, print to every kitchen printer, confirm the tip flow, and check the tax total on the test check against a hand calculation. Twenty minutes of ritual that catches the five most common day one surprises while they are still free.
Have your own numbers checked
Send last month's statement. We read it with you, free, and tell you straight whether we are the ones to fix it.
Send your numbers
About a minute. It goes straight to the Equip team.
It reaches the Equip team. A person calls you back, and if we do not have a crew near you, the team routes it to whoever serves you best. We never ask for card or bank details on this site.