Every vendor selling a GloriaFood migration says "we move everything". Nobody moves everything, because GloriaFood does not export everything. Here is the full list, line by line, including the parts that do not come across — ours or anyone else's.
| Part of your setup | In GloriaFood | Moving to Ontabee |
|---|---|---|
| Categories | In the Fetch Menu payload | Imported automatically Names and ordering come across intact. |
| Items, descriptions, prices | In the Fetch Menu payload | Imported automatically The bulk of the menu, and the slowest thing to retype. |
| Sizes | In the Fetch Menu payload | Imported automatically Each with its own price and default flag. |
| Option groups | In the Fetch Menu payload | Imported automatically Including required, allow_quantity, force_min and force_max — the rules that stop a customer ordering a pizza with no base. |
| Options and price deltas | In the Fetch Menu payload | Imported automatically Defaults preserved. |
| Size-level option groups | A Size carries its own groups array | Imported automatically Kept per-dish, so 9" and 14" can offer different toppings. This is where flattening tools lose data. |
| Availability windows | Day/time fields on categories and items | Imported automatically Breakfast menus and late-night items keep their schedule. |
| Currency | On the menu object | Imported automatically Checked against your location on import; a mismatch is flagged before anything is written. |
| Item photos | NOT in the payload — GloriaFood documents this explicitly | Rebuilt with you Pulled across only where your account exposes a picture URL. Otherwise saved from the Menu Editor one at a time and re-uploaded. Budget an hour or two for 80+ items. |
| Delivery zones | No documented export | Rebuilt with you Rebuilt with you. Ontabee also prices by actual driving distance, which is a different model — worth setting up deliberately rather than copying. |
| Opening hours & prep times | No documented export | Rebuilt with you Screenshot these in GloriaFood before you start. Fiddly rather than hard. |
| Delivery fees & minimums | No documented export | Rebuilt with you Re-entered per zone. |
| Tax settings | No documented export | Rebuilt with you Set per location, since rates are jurisdictional. |
| Payment configuration | No documented export | Rebuilt with you You connect your own gateway account, so this is new setup rather than a copy — the money settles directly to you. |
| Promotions & vouchers | No documented export | Rebuilt with you Rebuilt. A reasonable moment to drop the ones that never worked. |
| Customers & order history | CSV export in the GloriaFood admin | Rebuilt with you Under Marketing → Customers → Export. Pull it while the platform is still up — it is not covered by the menu API. |
| Your GloriaFood website | Not exportable | Does not move Ontabee gives you a new ordering site on your own domain. The old one is not migrated. |
| Reviews on GloriaFood | Not exportable | Does not move These do not move anywhere, on any platform. |
What GloriaFood does and does not return is from its own Fetch Menu integration documentation, checked August 2026. GloriaFood documents no export endpoint other than the menu one, which is why everything outside the menu is listed as rebuilt. If GloriaFood publishes a broader export before the shutdown, this page will be wrong — check the docs before relying on it either way.
The menu is the big one — every category, item, price, size and option group, with the min/max rules intact. On a large menu that is days of retyping avoided, and it is the part most likely to be entered wrongly by hand under deadline pressure.
An hour or two on photos if you want your existing ones, and a sitting to re-enter delivery zones, hours, fees, tax and payments. This is the same work wherever you go, because no platform can import what GloriaFood does not export.
Generate your Fetch Menu key, export your customer CSV, and screenshot every settings page. Those three things are useful wherever you land — including if you never talk to us.
Everything in GloriaFood’s documented Fetch Menu payload: categories, items, descriptions, prices, sizes, option groups with their required/min/max rules, options and their price deltas, tags, and the availability windows on categories and items. You hand over one API key and it comes across without retyping.
Item photos, delivery zones, opening hours, prep times, delivery fees, tax settings, payment configuration, promotions, and your customer and order lists. GloriaFood’s documented API covers the menu and nothing else, so everything outside the menu is rebuilt rather than imported. Customers and orders you export yourself as CSV from the GloriaFood admin.
GloriaFood’s own integration documentation states that item photos are not included in the menu payload. Where an account happens to expose a picture URL we pull it across with the item, but that is best-effort rather than something the API promises. Photos that only exist inside the Menu Editor have to be saved and re-uploaded by hand.
Yes. In GloriaFood a Size carries its own groups array — which is how a 9-inch pizza offers different toppings than a 14-inch one. Ontabee preserves that per-dish, so the group is revealed by the size that triggers it rather than shown on everything. Tools that flatten sizes and items into one list lose this distinction.
The menu import itself takes seconds once you have the key. The rebuild — delivery zones, hours, fees, tax, payments — is the part that takes time, and it is the same work wherever you move. Most single-location restaurants are live the same day.
We show you a preview of exactly what we found in your menu — counts, warnings and all — before anything is written. Most single locations are live the same day.