What happens to your data when GloriaFood shuts down

Oracle is retiring GloriaFood on April 30, 2027. It’s already closed to new signups, so the platform is in wind-down, and Oracle has confirmed no data retention past that date. Whatever you haven’t pulled out yourself is simply gone when the service goes dark.

The catch is that there’s no single “download everything” button. GloriaFood does let you get some of your data out, but it’s piecemeal, and the parts that hurt most to rebuild are the ones that don’t export at all. Here’s where each piece stands.

Your menu structure: exportable via the official API

GloriaFood publishes a Fetch Menu API that returns your whole menu in one call. Categories, items, descriptions, prices, sizes, and modifier groups with their min-max rules.

• You generate a key per location in the Restaurant Admin Panel: the ”…” (Others) menu → 3rd party integrations → Enabled integrations → the “Fetch Menu” template.
• The endpoint is https://pos.globalfoodsoft.com/pos/menu, with the key in the Authorization header. It returns JSON, the full tree of everything a menu needs.
• Running a chain? The key is per location, so a nine-branch group means nine keys.

This is the hard part of any migration and it’s the part that does come out cleanly. A developer, or a migration tool like Ontabee, can pull it in seconds.

Your item photos: the real gap

Dish photos aren’t in the menu export and there’s no bulk download for them. GloriaFood’s own Menu Editor is the only place to save them, one at a time. Budget a couple of hours if you’ve got 80-plus items. Two things worth knowing:

• Restaurants that relaunch with placeholder images feel it in orders during the first week. The photos are worth the effort.
• A fair chunk of GloriaFood’s item images are their own stock photos anyway. You may not want to carry those across, which makes this a good moment to shoot your real dishes.

If you point a migration tool at your Fetch Menu key, any photo URL the API does expose gets pulled across with the item. The ones that only exist inside the Menu Editor still need saving by hand.

Your customers and orders: CSV export in the admin

Your client contacts and order history can be exported yourself, as CSV, from the admin under Marketing → Customers → Export. Pull these while the platform is still up. You’ll want them for reactivation and for your own records.

Your settings: screenshot and rebuild

None of your delivery zones, opening hours, prep times, fees, taxes, payment configuration or promotions export anywhere, and no import tool can invent them. That’s setting-by-setting reconstruction. It isn’t hard, but it’s fiddly and easy to get wrong under deadline pressure, which is exactly what spring 2027 will be.

Screenshot every settings page now, while you can still read them side by side with the new setup.

What you can do about it

You don’t need to wait, and you don’t need to lose anything. Two practical steps:

1. Get out what GloriaFood lets you, while the platform is up. Your Fetch Menu key, your customer and order CSVs, and every dish photo you can save.
2. Move to a platform that rebuilds the rest with you. Ontabee uses your Fetch Menu key to pull your menu across, including items, prices, modifiers, option groups and the availability windows on them, and each branch keeps its own menu. Your delivery areas, hours, fees and payment setup get rebuilt alongside you rather than imported, because nothing exports them. Most single-location restaurants are live again the same day.

The earlier you move, the calmer it is. No queue, no deadline pressure, and your GloriaFood page keeps working right up to the cutoff while you get set up.

Don’t wait for the deadline

The restaurants that struggle are the ones that wait until spring 2027, when everybody moves at once and support everywhere is jammed. Moving now costs you nothing extra and takes the risk off the table.

→ See exactly how migration works, or start free and send us your menu.