Restaurant POS Switch Center
Figure out whether switching POS systems is actually safe and worth it.
A POS migration is moving your menu, staff, and settings from the point-of-sale system you use today (the software and hardware that takes orders and payments) onto a new one, without losing the records you need. A kitchen display screen (KDS) is the screen that shows orders to the kitchen. Start with the system you use today. We map what to export, what can change, what needs verification, and whether the current Shift4 Dine switch path is worth a closer review.
Check my restaurant
Switching your POS to Shift4 SkyTab: a guide by current system
Pick the system you use today. Each guide covers what can come over, what to gather, a realistic timeline, the risks, and who the switch tends to suit. No guide promises savings, data portability, or a fixed date. Effort ratings are Norvet's planning view, not a Shift4 statement.
Compare by current system
| Your current POS | Conversion path | Typical effort | Watch out for |
|---|---|---|---|
| Toast | Supported conversion source | Lighter. Shift4 lists Toast as a supported conversion source. Ask what converts for your account. | Toast-only tools, hardware you do not own, and the remaining contract term. |
| Clover | Inventory export supported; rest exported or rebuilt | Moderate. Shift4 lists a Clover inventory export. Apps, taxes, and settings are re-entered. | Hardware leases and the Clover apps that run ordering, loyalty, or payroll. |
| Square | Confirm with your rep | Moderate. Square is not on the supported list we reviewed, so plan an export and a hand review. | Square gift cards and loyalty, plus anything tied to Square-only hardware. |
| Heartland | Mostly manual rebuild | Heavier. Heartland is not a named conversion source, so most settings are captured and rebuilt. | Tax rules, pay rates, and permissions have to be documented, not just exported. |
| SpotOn | Confirm with your rep | Moderate. No named conversion path, so plan an export, a review, and hand-entered settings. | Contract timing, hardware return obligations, and loyalty or reservation history. |
| TouchBistro | Confirm with your rep | Moderate. No named conversion path. Table layouts and menus are reviewed and entered. | Table layouts, reservations, and tablet hardware compatibility. |
| Aloha (NCR) | Mostly manual rebuild | Heavier. Highly configured systems mean more settings to document and rebuild. | Dealer-held access, franchise rules, and custom reporting feeds. |
| Micros (Oracle) | Mostly manual rebuild | Heavier. Larger, integrated setups mean more to document, rebuild, and test. | Property or room-charge links, dealer-held access, and group agreements. |
| Lightspeed | Confirm with your rep | Moderate. No named conversion path. Exports are reviewed and loaded, settings are entered by hand. | Inventory data, hardware compatibility, and connected accounting tools. |
| Revel | Shift4-owned system | Varies. Depends on the path Shift4 offers your account. Confirm before planning. | Terms, timing, and hardware are set by Shift4, so ask what changes. |
| HungerRush | Confirm with your rep | Moderate. Menus and modifiers can be heavy, and delivery workflows need testing. | Delivery and dispatch workflows, and complex modifier trees. |
| FuturePOS | Supported conversion source | Lighter. Shift4 lists FuturePOS as a supported conversion source. Ask what converts for your account. | Older hardware and settings that still need owner approval. |
| POSitouch | Supported conversion source | Lighter. Shift4 lists POSitouch as a supported conversion source. Long-running setups need a documentation pass. | Undocumented customizations and back-office feeds. |
| Hospitality POS | Supported conversion source | Lighter. Shift4 lists Hospitality POS as a supported conversion source. Ask what converts for your account. | Settings that still need owner approval, and hardware reuse. |
| Another POS | Confirm with your rep | Varies. Depends on your system and how well it exports. | Unknown export quality. Ask before planning around a date. |
- Toast
- Conversion path:
- Supported conversion source
- Typical effort:
- Lighter. Shift4 lists Toast as a supported conversion source. Ask what converts for your account.
- Watch out for:
- Toast-only tools, hardware you do not own, and the remaining contract term.
- Clover
- Conversion path:
- Inventory export supported; rest exported or rebuilt
- Typical effort:
- Moderate. Shift4 lists a Clover inventory export. Apps, taxes, and settings are re-entered.
- Watch out for:
- Hardware leases and the Clover apps that run ordering, loyalty, or payroll.
- Square
- Conversion path:
- Confirm with your rep
- Typical effort:
- Moderate. Square is not on the supported list we reviewed, so plan an export and a hand review.
- Watch out for:
- Square gift cards and loyalty, plus anything tied to Square-only hardware.
- Heartland
- Conversion path:
- Mostly manual rebuild
- Typical effort:
- Heavier. Heartland is not a named conversion source, so most settings are captured and rebuilt.
- Watch out for:
- Tax rules, pay rates, and permissions have to be documented, not just exported.
- SpotOn
- Conversion path:
- Confirm with your rep
- Typical effort:
- Moderate. No named conversion path, so plan an export, a review, and hand-entered settings.
- Watch out for:
- Contract timing, hardware return obligations, and loyalty or reservation history.
- TouchBistro
- Conversion path:
- Confirm with your rep
- Typical effort:
- Moderate. No named conversion path. Table layouts and menus are reviewed and entered.
- Watch out for:
- Table layouts, reservations, and tablet hardware compatibility.
- Aloha (NCR)
- Conversion path:
- Mostly manual rebuild
- Typical effort:
- Heavier. Highly configured systems mean more settings to document and rebuild.
- Watch out for:
- Dealer-held access, franchise rules, and custom reporting feeds.
- Micros (Oracle)
- Conversion path:
- Mostly manual rebuild
- Typical effort:
- Heavier. Larger, integrated setups mean more to document, rebuild, and test.
- Watch out for:
- Property or room-charge links, dealer-held access, and group agreements.
- Lightspeed
- Conversion path:
- Confirm with your rep
- Typical effort:
- Moderate. No named conversion path. Exports are reviewed and loaded, settings are entered by hand.
- Watch out for:
- Inventory data, hardware compatibility, and connected accounting tools.
- Revel
- Conversion path:
- Shift4-owned system
- Typical effort:
- Varies. Depends on the path Shift4 offers your account. Confirm before planning.
- Watch out for:
- Terms, timing, and hardware are set by Shift4, so ask what changes.
- HungerRush
- Conversion path:
- Confirm with your rep
- Typical effort:
- Moderate. Menus and modifiers can be heavy, and delivery workflows need testing.
- Watch out for:
- Delivery and dispatch workflows, and complex modifier trees.
- FuturePOS
- Conversion path:
- Supported conversion source
- Typical effort:
- Lighter. Shift4 lists FuturePOS as a supported conversion source. Ask what converts for your account.
- Watch out for:
- Older hardware and settings that still need owner approval.
- POSitouch
- Conversion path:
- Supported conversion source
- Typical effort:
- Lighter. Shift4 lists POSitouch as a supported conversion source. Long-running setups need a documentation pass.
- Watch out for:
- Undocumented customizations and back-office feeds.
- Hospitality POS
- Conversion path:
- Supported conversion source
- Typical effort:
- Lighter. Shift4 lists Hospitality POS as a supported conversion source. Ask what converts for your account.
- Watch out for:
- Settings that still need owner approval, and hardware reuse.
- Another POS
- Conversion path:
- Confirm with your rep
- Typical effort:
- Varies. Depends on your system and how well it exports.
- Watch out for:
- Unknown export quality. Ask before planning around a date.
I am leaving…
These guides are organized by source system because the features, data, hardware, contracts, and migration risks you are leaving behind matter as much as the new POS.
Switch guide
Toast → SkyTab
A plain-language guide to moving a restaurant from Toast to Shift4 SkyTab: what can come over, what to gather first, a realistic timeline, the risks, and who the switch tends to suit.
See what changesSwitch guide
Clover → SkyTab
What restaurant owners should review before moving from Clover to Shift4 SkyTab: contracts, hardware, apps, menu export, gift cards, timeline, risks, and who the switch tends to suit.
See what changesSwitch guide
Square → SkyTab
A Square-to-SkyTab restaurant switch guide: menu exports, customers, gift cards, Square apps, hardware, a realistic timeline, risks, and who the switch tends to suit.
See what changesSwitch guide
Heartland → SkyTab
Heartland-to-Shift4 restaurant migration planning: what moves, what must be rebuilt by hand, menu, taxes, employees, kitchen routing, gift cards, timeline, and who the switch tends to suit.
See what changesSwitch guide
SpotOn → SkyTab
A restaurant-focused SpotOn-to-SkyTab guide: contracts, menu data, employees, loyalty, reservations, hardware, a realistic timeline, risks, and who the switch tends to suit.
See what changesSwitch guide
TouchBistro → SkyTab
A practical TouchBistro-to-SkyTab guide for tables, menus, staff, reservations, loyalty, hardware, a realistic timeline, risks, and who the switch tends to suit.
See what changesSwitch guide
Aloha (NCR) → SkyTab
Moving a restaurant off Aloha (NCR) to Shift4 SkyTab: what to export, what to rebuild, how franchise or dealer contracts affect the timing, a realistic timeline, and who the switch tends to suit.
See what changesSwitch guide
Micros (Oracle) → SkyTab
Moving a restaurant from Oracle Micros to Shift4 SkyTab: what to export and rebuild, who holds access, a realistic timeline, the risks, and who the switch tends to suit.
See what changesSwitch guide
Lightspeed → SkyTab
A guide to moving a restaurant from Lightspeed to Shift4 SkyTab: menu export, employees, gift cards, hardware, a realistic timeline, risks, and who the switch tends to suit.
See what changesSwitch guide
Revel → SkyTab
Revel is now part of Shift4. What that means for a Revel restaurant looking at SkyTab: questions to ask, what to export, a realistic timeline, risks, and who the move tends to suit.
See what changesSwitch guide
HungerRush → SkyTab
Moving a pizza or delivery-heavy restaurant from HungerRush to Shift4 SkyTab: delivery and online ordering, menu export, hardware, a realistic timeline, risks, and who the switch tends to suit.
See what changesSwitch guide
FuturePOS → SkyTab
A guide to moving a restaurant from FuturePOS to Shift4 SkyTab: a named conversion source, what to confirm, what to gather, a realistic timeline, risks, and who the switch tends to suit.
See what changesSwitch guide
POSitouch → SkyTab
Moving a restaurant from POSitouch to Shift4 SkyTab: a named conversion source, what to confirm, what to gather, a realistic timeline, risks, and who the switch tends to suit.
See what changesSwitch guide
Hospitality POS → SkyTab
Moving a restaurant from Hospitality POS to Shift4 SkyTab: a named conversion source, what to confirm, what to gather, a realistic timeline, risks, and who the switch tends to suit.
See what changesSwitch guide
Another POS → SkyTab
Not sure whether your POS is on the list? A general guide to moving a restaurant to Shift4 SkyTab from any other system: what to gather, what can come over, a realistic timeline, and who the switch tends to suit.
See what changesWho the switch tends to suit
Fit depends on your menu, your contract, and your statement, not only your business type. These are starting points, and a switch review tells you more.
Counter service
Simple menus and short lines tend to be the easiest to move. Check your handheld, kiosk, and online ordering needs.
Full service
Tables, courses, and kitchen routing need the most testing. Ask for a demo built around your busiest shift.
Bar
Tabs, happy-hour pricing, and bar printer routing should be tested on the new system before cutover.
Multi-unit
Ask Shift4 how multi-location menus, reporting, and rollout order work. Moving one location first is a common way to lower risk.
Quick service (QSR)
Speed and online order flow matter most. Test orders that come in from delivery apps before you go live.
Catering
Check how large advance orders, deposits, and invoices are handled. Confirm with your rep before assuming it matches today.
Honest not-a-fit cases
- Heavy custom integrations that have no tested replacement
- A contract with a large early termination fee that outweighs the benefit of moving now
- A franchisor or corporate office that requires a specific POS
- A current setup whose cost and workflow already work for you after a real statement review
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.
Questions restaurant owners ask
Get the answer before you talk to sales
Is SkyTab better than Toast for a restaurant?
It depends on the restaurant. SkyTab is a restaurant-first POS with integrated payments, online ordering, reservations, loyalty, gift cards, mobile ordering, and 24/7 support. Toast is also restaurant-focused, so the decision usually comes down to your current workflow, contract, hardware, integrations, processing economics, and the cost of changing systems, not a generic feature checklist.
Should a restaurant move from Clover to SkyTab?
It can make sense when the restaurant needs a more restaurant-specific operating system, but the right answer depends heavily on the Clover apps, hardware commitments, processing agreement, gift-card obligations, and workflows already in use.
Is SkyTab a better fit than Square for a restaurant?
SkyTab is purpose-built for restaurants, while Square spans restaurants, retail, appointments, and other business types. For an established restaurant, the decision should focus on the exact Square products in use, restaurant workflow depth, integrations, hardware, and total processing economics.
How does the $5,000 Shift4 Dine restaurant switch offer work?
Shift4’s published conversion terms describe a $5,000 signing bonus for qualifying new Shift4 Dine restaurant merchants that switch from another POS and average at least $30,000 in live transaction volume in each of their first two calendar months. The published PDF also says an “established” restaurant must have operated continuously for at least 12 months and includes prior-relationship and other eligibility restrictions.
How much does SkyTab POS cost?
SkyTab’s current public checkout shows a Table Service Bundle at $29.99/month under standard pricing, with $0 due today. Its checkout also shows standard processing at 2.75% + $0.15 per transaction, an Advantage Program option, and a custom-quote option. Your real cost can differ based on hardware, devices, processing structure, add-ons, and merchant-specific terms.
What happens to existing gift cards when a restaurant changes POS systems?
Existing gift-card obligations do not disappear because the POS changes. Before cutover, export the outstanding balances and card identifiers your current provider makes available, determine whether balances can be imported into the new platform, and create a documented plan for honoring any cards that cannot be migrated automatically.
What data can be moved when switching restaurant POS systems?
Menu items, modifiers, categories, customers, employees, and some inventory data are often exportable, but migration depth depends on the source and destination systems. Taxes, permissions, tables, printer routing, KDS rules, loyalty, gift cards, integrations, and historical reports often need separate validation or manual rebuild.
What internet and Wi-Fi setup does a modern restaurant POS need?
A restaurant POS should not depend on a single fragile Wi-Fi path. The right design usually separates wired fixed devices from mobile devices, provides strong managed Wi-Fi coverage, protects payment traffic, and includes a backup connectivity plan for the moments when the primary ISP fails.
Quick decision check
Should I switch POS systems?
This is deliberately not a sales score. It checks whether you have a reason to switch and whether the restaurant is ready to migrate without creating a new problem.
Is the current POS causing a real problem?
Examples: cost, outages, support, missing restaurant features, or staff friction.
Do you know your contract / cancellation position?
A good switch starts with knowing what it costs to leave.
Can you export the records you need before canceling?
Menu, customers, employees, reports, gift cards, loyalty, and anything needed for tax/accounting.
Have you listed every integration the restaurant depends on?
Delivery, reservations, payroll, accounting, loyalty, gift cards, online ordering, and scheduling.
Can you schedule training and a controlled cutover?
The best POS still fails if the team first sees it during a Friday-night rush.
Is the restaurant network ready for the replacement POS?
Internet, backup connection, Wi-Fi coverage, printers, KDS, switches, and power.
Quick switch check
See if your restaurant is worth a Shift4 switch review
We screen the basics before asking for a call. No EIN, bank information, statement upload, or long application.
What POS do you use today?
How Norvet approaches a POS migration
- Step 1
Capture the source
Exports, screenshots, integrations, network, hardware, and real workflows.
- Step 2
Normalize the data
Map source records into a vendor-neutral migration model instead of guessing field-for-field.
- Step 3
Approve what changes
Owner approves taxes, pricing, permissions, cash handling, and any feature-loss decision.
- Step 4
Configure and test
Test tickets, payments, printers, KDS, employees, taxes, integrations, and closeout before acceptance.