Skip to main content
Norvet MSP

Restaurant POS migration guide

How to switch from Revel to Shift4 SkyTab

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. Revel is owned by Shift4, so a move to SkyTab is a conversation with Shift4 about your account rather than a switch between unrelated companies. Shift4 has said Revel merchants are expected to move to SkyTab over time. The timing, hardware, and pricing for your account are things to confirm with your rep.

Check my Revel setup
Stock photo: Restaurant team reviewing a POS switch from Revel
Stock photo by SpotOn POS on Pexels

What can come over from Revel

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.

  • Menu items and prices

    Confirm with your rep

    Because Shift4 owns Revel, a direct path may exist. We could not confirm it. Ask your rep.

  • Modifiers (add-ons and choices)

    Confirm with your rep

    Ask your rep which modifier data carries over.

  • 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

    Customer data moves only with your 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
  • Your Revel agreement, including term and any change-of-plan clauses
  • Any message from Shift4 about a planned move to SkyTab

Typical timeline from Revel (planning estimate, varies by setup)

  1. Step 1. Gather your records: About 1 week

    Exports, screenshots, statements, and contract dates. Varies with how organized they are.

  2. 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.

  3. 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.

  4. Step 4. Parallel run: A few days to 1 week

    Run slower shifts on the new system while the old one stays available. Varies.

  5. Step 5. Cutover day: 1 day

    Pick a slow day, freeze changes in the old system, and switch. Plan for hiccups.

  6. Step 6. First weeks live: 2 to 4 weeks

    Watch reports, tips, and payouts against the old system and fix gaps. Varies.

Timing may follow a Shift4 program rather than your own calendar. Ask for the schedule before planning around it.

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 same-owner move can feel automatic. Still keep your own exports and read what changes in writing.

Who this switch tends to suit, and who it does not

Business types that often fit: Counter service, Full service, Quick service (QSR), Multi-unit. This is a starting point, not a verdict. A statement review tells you more.

Often a good fit

  • Revel restaurants that Shift4 has contacted about moving, and want a second opinion before agreeing.
  • Owners who want to compare full monthly cost and terms for staying versus moving.
  • Restaurants that need features SkyTab offers and have confirmed them with a demo.

Probably not a fit if

  • You have not yet learned from Shift4 what moving changes in your agreement.
  • You depend on a Revel integration that SkyTab does not match.
  • You are happy with your current setup and no one is asking you to move.

What needs to be compared before you leave Revel

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, modifiers, taxes, and order types
  • Employee roles and permissions
  • Online ordering, loyalty, and gift cards
  • Kitchen routing, printers, and KDS
  • Your current agreement and what changes if you move

Export this before canceling Revel

  • Menu and modifier exports
  • Employee and permission references
  • Customer data you are permitted to retain
  • Sales, tax, and settlement reports
  • Gift card and loyalty balances
  • Your current agreement and hardware documents

Watch-outs

Do not assume terms carry over. Ask whether moving changes your agreement, pricing, or hardware.

Ask whether Shift4 is offering Revel merchants a planned path, and on what schedule.

Revel integrations may not all exist on SkyTab.

Keep your own exports even when the owner is the same company.

Conversion-path note

Shift4 acquired Revel Systems in 2024 and has said Revel merchants are expected to move to SkyTab. We could not confirm the current migration path, timing, or terms on a Shift4 page, so confirm with your rep.

Questions owners ask about leaving Revel

Is Revel owned by Shift4?

Shift4 announced its acquisition of Revel Systems in 2024, according to Shift4 financial filings and press coverage. Confirm what that means for your account with your rep.

Do Revel restaurants have to move to SkyTab?

Shift4 has said Revel merchants are expected to move over time. Whether and when it applies to you is something to confirm in writing.

Will my terms change if I move?

Possibly. Ask what changes in pricing, term, and hardware, and get the answer in writing.

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)
  • Shift4 annual report (Form 10-K for 2025) and QSR Magazine coverage of the Revel acquisition, as summarized in Norvet research dated 2026-10-07

Last reviewed 2026-10-11.

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.

Question 1 of 617%

What POS do you use today?

Compare another source POS

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.