What needs to be compared before you leave Clover
A POS switch is a business-process migration. The safe sequence is source capture, field mapping, owner approval, target configuration, testing, cutover, and acceptance. Do not cancel the source system until the records and workflows you need have been accounted for.
- Restaurant menu, modifiers, taxes, discounts, and employee access
- Clover App Market tools the restaurant actually depends on
- Kitchen printers, KDS, handhelds, tables, and tip workflows
- Customer, loyalty, and gift-card programs
- Accounting, payroll, delivery, and online-ordering connections
Export this before canceling Clover
- Inventory / menu and modifier exports
- Customer export
- Transaction and settlement reports
- Current app list and app billing
- Gift-card and loyalty balances
- Hardware lease or financing documents
Watch-outs
Clover hardware leases or financing can survive a POS switch.
Third-party Clover apps may not have direct replacements.
Clover hardware should not be assumed compatible with SkyTab.
Tax and app settings may require manual reconfiguration even when core item data converts.
Conversion-path note
Norvet’s Shift4 onboarding material reviewed in 2026 references a Clover inventory export path. Treat that as a starting point, not a promise that every Clover object or third-party app transfers automatically.
