Skip to content
GloriaFood migration

How to Get Your Data Out of GloriaFood

Six things to capture before 31 March 2027, in order of how irrecoverable each one is — and an honest note about which parts of this we could verify and which we could not.

Oracle has announced no export-and-move path out of GloriaFood, and full end of service is 31 March 2027. What that means in practice is that getting your data out is a job you do by hand, and the order you do it in matters more than the tools you use.

This page is ordered by how irrecoverable each item is, which is not the order these things usually get done in. Most migration checklists start with the menu because the menu is the visible thing. The menu is the item you can rebuild from a photograph. Start with the one you cannot rebuild from anything.

One thing we will not tell you, because we cannot check it. Several migration pages state that the GloriaFood dashboard lets you export menu items and a basic customer list. That requires an account we do not have, and Oracle has announced nothing. So this page describes what to capture and in what order — advice that holds whether or not a given export button exists — rather than walking you through a screen we have not seen. Where a competitor's page sounds more certain than this one, that is the difference.

In this order

Six things to capture, hardest to replace first

  1. 1. Your customer list

    Irrecoverable

    Names, phone numbers, email addresses and marketing consent. This is the only item on the page that cannot be reconstructed from anywhere else after the service ends — a menu can be retyped from a photograph and an order history can be lived without, but a customer list that goes dark is gone. Capture it first, before anything else on this list, and capture it again nearer the move.

    How: Take it from wherever your admin will give it to you — a report, a screen, a copy-paste into a spreadsheet. The format does not matter. Having it does.

  2. 2. Order history

    Irrecoverable

    Twelve months if you can get it, three at minimum. You want it for two unglamorous reasons: it is the evidence for what your delivery zones and prep times should be on the new platform, and it is what an accountant asks for. Nobody misses it until the first quarter-end after the switch.

    How: Export or copy whatever period the reporting will give you. Prioritise the most recent twelve months over completeness.

  3. 3. The menu, with modifiers and photos

    Recoverable, tediously

    Items, prices, categories, modifier groups and their prices, and the photographs. The photographs are the part people underestimate — reshooting a menu is a day with a camera and a cold plate of food. The structure can be rebuilt from your public ordering page if it has to be; the images cannot be pulled at usable resolution.

    How: Save the images at the largest size you can get. If your ordering page is still live, everything else is visible on it.

  4. 4. Delivery zones and fees

    Recoverable, from memory

    The shapes on the map, the minimum order per zone, and the fee per zone. Easy to rebuild and easy to rebuild WRONG, because the current shapes usually encode a couple of years of learning about which streets are worth driving to. Screenshot the map rather than trusting anyone to remember it.

    How: Screenshots of each zone, plus the fee and minimum written next to it.

  5. 5. Every link, QR code and printed thing pointing at GloriaFood

    Not data — a to-do list

    The ordering link on your website, the one in your Instagram bio, the Google Business Profile link, the QR codes on the tables, the sticker in the window, the flyer in the delivery bag. All of them stop working at the end of service. This is not something to export; it is something to write down now so that switching them over later is a list rather than an archaeology project.

    How: One list, one line each, with where it physically lives.

  6. 6. Settings you would not think to write down

    Recoverable, annoyingly

    Opening hours per service, prep-time defaults, tax rates and how they are applied, the minimum order value, service and packaging fees, and any promo codes still in circulation. None of it is hard to rebuild. All of it is hard to remember at 9pm on the day you go live.

    How: Screenshots of each settings page beat a transcription, because they capture the things you did not know were settings.

Timing

Why waiting costs more than it looks

The site is already being dismantled. Several gloriafood.com marketing pages that Google still has in its index now return a 404 — checked 3 September 2026. That is what the wind-down of a discontinued product looks like from the outside, and it is a reason to treat any working export as something to use this week rather than next quarter.

Your customers need weeks, not a day. Whatever you move to, your regulars have to start using something new. A restaurant that switches with months to spare converts them gradually, over orders they were placing anyway. A restaurant that switches in the last fortnight asks all of them at once, and loses the ones who do not get round to it.

And the deadline may be a month earlier than you have read. Most third-party pages say 30 April 2027, from an earlier in-product notice. Oracle's own statement says 31 March. Plan against the earlier one.

FAQ

Getting your data out, answered

Does GloriaFood have a data export tool?

Oracle has announced no export-and-move path. What the admin will and will not hand you today is not something we can state from the outside — it needs an account we do not have, and other migration pages that assert it confidently are doing so without a source. What is certain is the deadline: Oracle's own page says full end of service on 31 March 2027, checked 3 September 2026. Treat any export capability as something to use now rather than something that will still be there later.

Why do so many sites say 30 April 2027?

Because an earlier in-product notice gave that date and it was widely repeated. Oracle's own current statement says 31 March 2027, and we re-check it — most recently on 3 September 2026. A month is a long time when the thing at stake is your customer list, so plan against the earlier date. If Oracle moves it, moving early costs you nothing.

What is the single most important thing to save?

The customer list, by a distance. Everything else on this page can be rebuilt from a photograph, a screenshot or an afternoon of typing. A customer list cannot be rebuilt from anything. If you do one thing after reading this, do that one.

Can I keep taking orders while I move?

Yes, and you should. Running both in parallel is what turns a migration into a gradual switch: your new store goes live, you move links and QR codes across as you get to them, and your regulars install the new app over a few weeks of ordering from you anyway. The restaurants that struggle are the ones that ask every customer to change on the same day.

Do I have to move to Supaorder to use this?

No. The list above is what to capture, not who to capture it for, and it is the same list whichever platform you choose. We would rather publish something useful and be one of the options you consider than publish something that only works if you pick us.

Will you rebuild the menu for me?

Yes — send us a link to your live ordering page and we set up items, modifiers, photos and delivery zones. That is the part we can do for you. The customer list is the part only you can get, which is why it is first on the list and not last.

Sources

GloriaFood and Oracle are trademarks of their respective owners. This page is published by Supaorder and reflects our reading of publicly available statements; it is not endorsed by either.

← The full migration path Running GloriaFood for clients? →

Ready to Keep 100% of Your Revenue?

Get your own branded ordering platform. Live in as little as 48 hours — zero commission, no contracts.

Book a Free Demo Talk to Our Team

Book a live demo on a real store · Free setup for early customers