Step 1 — Export everything you own before you touch hardware
Your item catalog, modifiers, tax rules, employee list and customer records are the parts of the old system that are genuinely yours. Pull them out as files while your old system is still running normally.
Item and menu export
Names, categories, prices, modifiers and any variant or size structure.
Tax and tip configuration
Tax rates by category, service charges, tip prompt behavior and any auto-gratuity rules.
Employees and permissions
Who can void, refund, discount, open the drawer and view reports.
Historical reports
Save the reporting you may need later for accounting and comparison. You may lose easy access to the old dashboard after you cancel.
Step 2 — Build the new system before it ships
The menu or catalog rebuild is the longest part of any migration, and it does not require the hardware to be at your counter. Get the catalog, taxes, tips and permissions configured and reviewed while the old system is still ringing sales.
Have one person who knows the menu best check it against the live one, item by item, including modifiers. Wrong modifiers cause more day-one pain than wrong hardware.
Step 3 — Stage the hardware in parallel, not in place
Set the new devices up next to the old ones and connect them to your network before cutover. Confirm printers, scanners, drawers and kitchen displays all respond, and run test transactions.
Check the physical details people forget: cable length to power and network, mounting, and whether the customer can actually reach and read the payment screen from their side of the counter.
Step 4 — Train staff on the new system before cutover day
Run your team through the ten things they do most: ring a normal sale, split a check or transaction, apply a discount, void, refund, take a tip adjustment, clock in, close out, reprint a receipt and handle a declined card.
If your staff can do those ten without help, cutover is uneventful. If they cannot, no amount of hardware readiness will save the first shift.
Step 5 — Cut over at your slowest point, and keep a fallback
Switch after close on your slowest night, not before a weekend rush. Keep the old system powered and reachable for a short overlap period so you can compare totals and pull anything you missed.
Reconcile the first few days deliberately: daily sales totals, tax collected, tips and deposits. Catching a misconfigured tax category on day two is a small fix. Catching it in a quarterly filing is not.
Step 6 — Close out the old account properly
Confirm the final deposits from your old processor have landed, then follow their written cancellation process and keep the confirmation. Check whether leased hardware has to be returned, and to whom.
BSV Solution sequences this with you and handles the catalog build, staging and training rather than shipping a box. Timelines depend on your setup and remain subject to underwriting approval and processor review.
Frequently asked questions
How long does switching POS systems take?
The catalog build and staff training take the most time and happen before cutover. The cutover itself is usually done between closing and opening. Actual timelines depend on your menu size and hardware, subject to underwriting and processor review.
Will I lose my sales history when I switch?
You generally keep access to exports you take before you cancel, but not always to the old dashboard afterward. Export your reporting before closing the old account.
Can I keep my existing hardware and change only processing?
Sometimes. It depends on the device, how it was registered and the processor. We check reuse options before recommending replacements.
What is the biggest cause of problems on cutover day?
An unverified catalog. Wrong modifiers, missing variants and misapplied tax categories cause more disruption than any hardware issue.
Want a second opinion on your setup?
Tell us how you take payments today and a BSV Solution specialist will walk through the options with you. Eligibility and processor selection are reviewed individually, subject to underwriting approval.