Simphony installs vary widely — some are cloud-based with EMC reporting access, others are on-premise with custom database structures, and many are managed by an Oracle reseller or your in-house IT team. This guide assumes some IT coordination, but our enterprise migration team handles the technical mapping.
Cloud POS systems like Foodics or Square have one tenant per account. Simphony is a configurable enterprise platform — your menu schema, revenue centers, and tax structures may have been customized when Oracle deployed it.
For a clean migration, our enterprise team works directly with whoever maintains your Simphony installation — usually your IT lead or your Oracle reseller. We've done this before with hotel groups and multi-property operators, so the playbook is well-established. The tradeoff for the extra coordination is a far cleaner migration: pricing tiers, multi-revenue-center setups, and complex modifier hierarchies all transfer correctly.
Start with the Shareabill onboarding form, choose "Oracle Simphony / Micros" as your current POS. You'll be assigned an enterprise migration specialist (different from the standard migration team — our enterprise specialists are familiar with EMC, MyMicros, and on-premise installs).
The first call (45 minutes) covers:
You'll receive a short authorization document — this is what we send to Oracle / your reseller / your IT team to confirm we have permission to receive your data. It typically also covers DIFC DPL acknowledgments around guest data transfer.
Sign electronically (we use DocuSign-equivalent) and we forward to whoever needs it.
Depending on your Simphony deployment, this happens one of three ways:
Your Oracle account team can export menu and configuration data via the Reports & Analytics module. We provide them a checklist of exactly which exports to run.
Your IT team or reseller runs database exports directly from the back-office server. We provide SQL queries for the relevant tables (menu_item_definition, menu_item_class, family_group, major_group, tax_class, etc).
We coordinate directly with your reseller — most have a standard data-extract process they run for outgoing customers. Expect 1–2 weeks of turnaround on their side.
Whoever runs the export uploads the files directly to your Shareabill secure portal (we provide a unique upload link for IT / the reseller, separate from yours). Files are encrypted in transit and at rest. Standard formats we accept: SQL dumps, CSV, Excel, XML config files.
This is the heaviest step — and it's all on us. Simphony's data model is rich but specific: menu_item_definitions live in classes, classes belong to family_groups, family_groups roll up to major_groups, modifiers have weight definitions, condiment sets have minimum/maximum constraints, etc.
Our enterprise team has a tested mapping playbook for each of these. Expect 5–10 business days for the first pass.
We send you a side-by-side report:
We resolve flagged items together, usually in a 30-minute call.
For Simphony customers we strongly recommend a phased cutover: enable Shareabill QR ordering at 1–2 tables first for a week, validate that everything reconciles correctly with your Simphony reports, then expand. This catches edge cases (combo items, banquet pricing, comped checks) before they affect your full operation.
No. Most enterprise customers continue using Simphony as their core POS for traditional service (servers ringing in orders, complex check splitting, kitchen routing). Shareabill adds the QR ordering layer and bill-splitting on top — guests who scan the QR get a Shareabill experience, while servers continue to use Simphony for everything else. Reconciliation between the two is part of our integration scope.
It happens. Our enterprise specialist will work with you to escalate, including drafting communications to Oracle directly if needed. Under most service agreements (and definitely under DIFC DPL), you have a right to your own configuration and customer data — Oracle and resellers know this and typically respond once the right channel is engaged.
Yes, but we recommend phasing. We migrate the data for all properties in parallel (saves time on the IT side), then go live property-by-property over a 2–4 week rollout. This isolates issues to one property at a time and lets your team build confidence.
Migration is included in your Shareabill onboarding regardless of POS complexity. The enterprise migration team is the same retainer-free white-glove service as our standard migration — it just takes longer because there's more to do.
Submit your onboarding form and an enterprise migration specialist will reach out within 24 hours to schedule the discovery call. Bring your IT lead if you can.