What can come over from Micros (Oracle)
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 | Rebuild by hand | Take what your administrator or dealer can export, then review and load it through Shift4 menu programming. |
| Modifiers (add-ons and choices) | Rebuild by hand | Modifier rules are captured and rebuilt, then 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 | 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
Rebuild by hand
Take what your administrator or dealer can export, then review and load it through Shift4 menu programming.
Modifiers (add-ons and choices)
Rebuild by hand
Modifier rules are captured and rebuilt, then 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
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
- Who administers your Micros system and holds its programming access
- Any hotel, property, or banquet integration and who depends on it
- Any group or corporate agreement that sets the POS
Typical timeline from Micros (Oracle) (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.
Integrated and multi-outlet setups take longer. Expect the longer end of each range, or more.
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
Another system may depend on your POS. Find those dependencies first, and plan the cutover with the people who own them.
Who this switch tends to suit, and who it does not
Business types that often fit: Full service, Bar, Multi-unit, Catering. This is a starting point, not a verdict. A statement review tells you more.
Often a good fit
- Independent restaurants and bars that own their contract and want to move off an older, dealer-dependent system.
- Operators with one or two outlets who can document workflows and plan a tested cutover.
- Owners comparing full monthly cost on a real statement before deciding.
Probably not a fit if
- A hotel, group, or franchise agreement requires Micros or another named system.
- Room-charge or property integrations have no tested replacement.
- You need a fast switch. Larger rebuilds need time for testing.
What needs to be compared before you leave Micros (Oracle)
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, order types, and revenue centers
- Employee roles, pay rates, and permissions
- Kitchen and bar routing, KDS, and printers
- Property, room-charge, or banquet workflows if you have them
- Reporting, accounting, and payroll connections
Export this before canceling Micros (Oracle)
- Menu and modifier exports from your Micros administrator or dealer
- Employee, job, and permission documentation
- Tax, discount, and revenue center rules
- Sales, labor, and settlement reports
- Integration documentation
- Service agreement and hardware documents
Watch-outs
Micros is often installed in hotels, groups, and larger venues where other systems depend on it.
Property or room-charge integrations may have no direct replacement.
Programming access often sits with a dealer or IT team.
Corporate or group agreements may decide the POS for you.
Conversion-path note
Micros 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 Micros (Oracle)
Can Shift4 convert my Micros data?
Micros was not named as a conversion source in the material we reviewed. Confirm with your Shift4 rep. If there is no supported path, plan a manual rebuild.
What if my Micros connects to a hotel system?
Treat that as a separate project. Ask Shift4 whether the connection is supported before you commit to a date.
Who gives me my menu export?
Ask your Micros administrator or dealer, in writing, before you give notice.
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.