What needs to be compared before you leave Heartland
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.
- Menu groups, items, modifiers, revenue classes, and tax classes
- Employees, jobs, pay rates, permissions, and report access
- Rooms, tables, sections, printers, and KDS routing
- Discounts, gratuities, cash handling, tips, refunds, and closeout
- Online ordering, delivery, payroll, accounting, loyalty, and gift cards
Export this before canceling Heartland
- Every available Heartland export
- Screenshots of settings that do not export cleanly
- Employee / job / permission records
- Menu, modifier, tax, and pricing records
- Table / room layout and printer-routing references
- Historical financial and settlement reports
Watch-outs
Do not assume Heartland fields map one-for-one into Shift4 objects.
Room-level tax flags do not by themselves document the actual tax rules to rebuild.
Employee roles should not be translated into broad admin access without owner approval.
Migration counts should reconcile source → canonical data → target configuration before go-live.
Conversion-path note
Current Norvet procedure is manual extraction + reconciliation unless Shift4 provides written confirmation of a supported Heartland conversion for the merchant.
