Published information

Cutover

Before and after going live on a new system: live-day tests, migration samples, limited pilots, rollback, and cost and exit. Still choosing a system? Start with the selection guides.

• Test a real service day, not a demo

  Skip the showroom. Shift staff run open-to-close. Only passed, failed, or still unknown.

• Migration: fix the scope, then run a sample

  Fix the scope before cutover, then match counts and identifiers on a shop sample. Until that sample exists, “we can migrate” is not a plan.

• Limited pilot first: scope, dates, rollback

  Do not “install for two weeks and see”. Write pilot scope, end date, who can stop, and how to cut back.

• How to roll back: triggers, decision maker, cut-back steps

  When you must stop, who may decide, and how long the old system stays—write a rehearsable rollback sheet, not a verbal deal.

• What to cost for a POS switch: hardware, training, support, fees, exit

  Put five items on one sheet: model numbers, who trains whom, which hours are supported, how much it costs, and how data leaves with you.

• What to prepare before switching POS

  Before cutover, clear devices/network, menu prices, accounts/permissions, visible fiscal-ticket items and rollback mindset; separate from the opening-day checklist.