What can come over from POSitouch
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 | Supported conversion | Shift4 lists this system as a supported conversion source. Which fields come across is confirmed per account. |
| Modifiers (add-ons and choices) | Supported conversion | Shift4 lists this system as a supported conversion source. Which fields come across is confirmed per account. |
| 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. |
Menu items and prices
Supported conversion
Shift4 lists this system as a supported conversion source. Which fields come across is confirmed per account.
Modifiers (add-ons and choices)
Supported conversion
Shift4 lists this system as a supported conversion source. Which fields come across is confirmed per account.
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
- A written list of customizations and workflows your managers rely on
- Back-office, accounting, and payroll feeds
Typical timeline from POSitouch (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.
Documenting a long-running setup adds time to the gather step.
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
An undocumented customization can vanish. Walk through a full shift with each manager.
Who this switch tends to suit, and who it does not
Business types that often fit: Full service, Bar, Counter service, Multi-unit. This is a starting point, not a verdict. A statement review tells you more.
Often a good fit
- Established independent restaurants on an older POSitouch setup who want a current platform and a named conversion path.
- Owners with a manager who can document how the system really runs.
- Operators who can plan a tested cutover.
Probably not a fit if
- You rely on a custom back-office feed with no tested replacement.
- Your agreement or hardware terms make now the wrong time.
- A group or franchise agreement sets your POS.
What needs to be compared before you leave POSitouch
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 pricing
- Employees, jobs, and permissions
- Rooms, tables, and kitchen routing
- Back-office reports and accounting exports
- Hardware, network, and the agreement that goes with it
Export this before canceling POSitouch
- Menu and modifier data
- Employee and permission references
- Back-office and accounting reports
- Sales, tax, and settlement reports
- Gift card and loyalty balances
- Hardware and agreement documents
Watch-outs
Long-running systems collect customizations nobody wrote down. Interview your managers.
Accounting and back-office feeds need a tested replacement.
Hardware is unlikely to be reused. Confirm in writing.
Taxes and permissions still need owner approval.
Conversion-path note
Norvet’s Shift4 onboarding material reviewed in 2026 lists POSitouch as a supported conversion source. The exact objects that convert need to be confirmed for each merchant.
Questions owners ask about leaving POSitouch
Does Shift4 convert POSitouch data?
Shift4 lists POSitouch as a supported conversion source. Ask which records convert for your restaurant and what you must enter by hand.
What about my back-office reports?
Export the ones you need to keep, and test any accounting feed on the new system before cutover.
Can I reuse my POSitouch hardware?
Do not assume so. Ask Shift4 in writing which devices work with SkyTab.
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.