A structured transition covers your contract, your data, your equipment, and the people who will use it. Here is the sequence we scope with your team.
Confirm the new setup can support the essential jobs your current system performs.
List the provider, contract term, notice dates, device ownership, apps, accessories, and integrations. Include seasonal constraints and a sensible changeover window. Keep current access while the transition is being planned.
Write down the transactions your team must complete: a normal sale, a discount, a refund, a split payment if needed, a receipt, and the end-of-day report. Include industry-specific workflows such as modifiers or inventory variants.
Review the complete equipment and subscription list, processing agreement, cancellation and renewal terms, data export access, support responsibility, and expected settlement arrangements. Approval and provisioning are provider dependent.
The best time to find a missing modifier or an incorrect permission is before the first live customer.
Export the records you are entitled to move. Clean product names, prices, variants, categories, and stock quantities. Customer information needs a lawful basis for transfer; gift-card balances and historical transactions may require a separate migration plan.
Set up approved products or menus, staff roles, receipts, taxes according to your instructions, tips where needed, and supported connections. Confirm who signs off financial and tax settings.
Walk through common sales and exceptions, daily opening and closing, refunds and voids, lost connectivity, and the correct support contacts. Keep short written instructions available at the checkout.
A transition ends after the operational checks, rather than when the terminal is delivered.
Use an agreed controlled transaction to check payment acceptance, receipt details, reporting, and the supported refund process. Confirm settlement once it is due under the provider’s timing.
Compare orders, payments, refunds, and deposits. Review inventory changes and any integration errors. Record issues with an owner and escalation route so the first operating period can be reviewed.
Cancel only through the required provider process once contractual obligations and outstanding activity have been reviewed. Retain required records, document equipment returns, and keep confirmation of closure.
Timing depends on provider approval, equipment availability, data preparation, integrations, and training. Your implementation plan specifies milestones; this site does not promise a fixed two-day switch.
Not necessarily. Export formats, platform limits, and data types vary. We confirm what can be imported, what remains in an archive, and how you can access it.
We plan to reduce disruption, but do not guarantee zero downtime. Your plan should include a fallback process and a suitable changeover window.
Compare handheld, countertop, and workstation formats.
Read more EXPLORE THE GUIDEUnderstand pricing models and compare your own numbers.
Read more EXPLORE THE GUIDEA nine-step path through preparation, training, and go-live.
Read more