What can come over from HungerRush
Every restaurant is different, so treat this as a planning map, not a promise. Where a row says “Confirm with your rep,” we could not verify it on a primary Shift4 source.
| What | How it usually moves | Notes |
|---|---|---|
| Menu items and prices | Export, then import | Export from the old system, review it, and load it through Shift4 menu programming. Expect a review pass. |
| Modifiers (add-ons and choices) | Rebuild by hand | Build-your-own and half-and-half rules are rebuilt and tested item by item. |
| Employees, jobs, and permissions | Rebuild by hand | Jobs, pay rates, and permissions are entered from your records. PINs move through a secure method. Nobody gets broader access than you approve. |
| Customer records | Confirm with your rep | Delivery address history is useful. Move it only with consent and a scope you approve. Ask your rep what can be loaded. |
| Gift card balances | Confirm with your rep | Balances are money you still owe customers. Export the balance report and ask your rep whether and how they carry over. |
| Loyalty points | Confirm with your rep | Points programs rarely map one for one. Decide how existing points are honored and confirm what can move. |
| Reporting history | Export and keep a copy | Past sales and tax reports stay with the old system. Export the ones you need for taxes and audits. |
Menu items and prices
Export, then import
Export from the old system, review it, and load it through Shift4 menu programming. Expect a review pass.
Modifiers (add-ons and choices)
Rebuild by hand
Build-your-own and half-and-half rules are rebuilt and tested item by item.
Employees, jobs, and permissions
Rebuild by hand
Jobs, pay rates, and permissions are entered from your records. PINs move through a secure method. Nobody gets broader access than you approve.
Customer records
Confirm with your rep
Delivery address history is useful. Move it only with consent and a scope you approve. Ask your rep what can be loaded.
Gift card balances
Confirm with your rep
Balances are money you still owe customers. Export the balance report and ask your rep whether and how they carry over.
Loyalty points
Confirm with your rep
Points programs rarely map one for one. Decide how existing points are honored and confirm what can move.
Reporting history
Export and keep a copy
Past sales and tax reports stay with the old system. Export the ones you need for taxes and audits.
What to gather before you switch
- Your contract end date and any early termination fee in the current agreement
- A recent processing statement (the monthly bill from your card processor)
- Who owns the hardware: bought outright, leased, or financed, and what happens to it if you leave
- Every integration in use: accounting, payroll, reservations, delivery apps, and loyalty
- Your online ordering setup and the web addresses customers use today
- Gift card liability: the total balance customers still hold, and how it is tracked
- A written description of how delivery, driver, and phone orders work today
- Every third-party delivery and online ordering connection
Typical timeline from HungerRush (planning estimate, varies by setup)
Step 1. Gather your records: About 1 week
Exports, screenshots, statements, and contract dates. Varies with how organized they are.
Step 2. Map and approve: 1 to 2 weeks
Match old settings to the new system and approve taxes, pay rates, permissions, and prices. Varies with menu size.
Step 3. Configure and test: 1 to 2 weeks
Shift4 programs the system, then you run test tickets, payments, printers, and reports. Varies with Shift4 scheduling and hardware delivery.
Step 4. Parallel run: A few days to 1 week
Run slower shifts on the new system while the old one stays available. Varies.
Step 5. Cutover day: 1 day
Pick a slow day, freeze changes in the old system, and switch. Plan for hiccups.
Step 6. First weeks live: 2 to 4 weeks
Watch reports, tips, and payouts against the old system and fix gaps. Varies.
Delivery workflows need their own test pass. Leave extra time in the configure and parallel run steps.
These ranges are Norvet planning estimates, not Shift4 commitments. Your timeline depends on Shift4 scheduling, hardware delivery, your menu size, and how quickly decisions get made.
Risks and how to reduce them
Something does not work on the first busy night
Run a parallel period on slow shifts, keep the old system available until the new one is accepted, and write down who to call.
Cutover day goes badly
Pick a slow day, freeze menu changes the day before, and have the old system export ready as a fallback.
Staff are not ready
Train the people who use the register on their real jobs, such as server, bartender, and manager, before the cutover date.
Gift card and card-on-file balances get stranded
Get the balance reports first, decide how each balance is honored, and confirm with Shift4 what can move before you cancel anything.
Specific to this switch
A delivery night is the worst time to find a gap. Test dispatch and phone orders on a slow shift first.
Who this switch tends to suit, and who it does not
Business types that often fit: Quick service (QSR), Counter service, Catering. This is a starting point, not a verdict. A statement review tells you more.
Often a good fit
- Counter-service and quick-service restaurants that mostly handle pickup and online orders, where the delivery workflow is simple and testable.
- Owners whose current agreement is ending and who want the full monthly cost compared.
- Shops that can test delivery on slow shifts before cutover.
Probably not a fit if
- You run heavy driver dispatch that you have not matched on SkyTab.
- Phone-order caller lookup is central and untested.
- A franchise or brand agreement sets your POS.
What needs to be compared before you leave HungerRush
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.
- Delivery, driver, and dispatch workflows
- Phone order entry and caller lookup
- Online ordering and third-party delivery apps
- Menu, modifiers, and pizza or build-your-own options
- Loyalty, coupons, and customer records
Export this before canceling HungerRush
- Menu and modifier exports
- Customer and delivery address data you are permitted to retain
- Coupon and discount rules
- Sales, tax, and settlement reports
- Driver and employee records
- Gift card and loyalty balances
Watch-outs
Delivery and dispatch are the hardest workflows to match. Test them first.
Customer address history is valuable. Confirm consent and scope before moving it.
Complex pizza modifiers need careful rebuilding and testing.
Third-party delivery connections must be set up and tested again.
Conversion-path note
HungerRush was not listed as a supported conversion source in the Shift4 material Norvet reviewed. Confirm any conversion path with your Shift4 rep.
Questions owners ask about leaving HungerRush
Does SkyTab handle delivery like HungerRush?
Do not assume it does. List what you use daily, such as dispatch and driver tracking, and ask Shift4 to show each one in a demo.
Can I move my customer list?
Only the data you are permitted to keep, with a scope you approve. Ask your rep what can be loaded.
How do I move complex pizza modifiers?
Plan to rebuild and test them item by item. Menu exports help, but build-your-own rules often need hand entry.
Is there a trial period if I switch to SkyTab?
Trial periods and agreement lengths can vary by offer and by partner. Ask your rep to confirm the trial period and the agreement length in writing before you sign, and ask what it costs to leave early.
Who does what
Norvet is a Trident Merchant Solutions partner. Trident partners with Shift4 (the parent company of SkyTab). Shift4 provides SkyTab and the card processing, and Shift4 programs and installs the system. Norvet helps gather and check your information and coordinates with the partner team.
Also useful: the restaurant processing cost calculator and the POS lock-in test.
Sources
- Norvet POS Migration Extraction Playbook, reviewed 2026-09-13 (Shift4 onboarding form conversion sources)
- Norvet research on Shift4 Dine, 2026-10-07 (pages on shift4.com were not machine-readable that day, so unconfirmed items are marked)
Last reviewed 2026-10-11.