Storekit

Migration

How to export your GloriaFood data — and why this month beats next month

Your menu, guest list, and order history disappear with GloriaFood's servers on 30 April 2027. What to export, in what order, and what to check before you trust the copies.

Harry Soar10 June 20262 min read

Your guest list is the asset. Get it out first.

Everything your restaurant has built up inside GloriaFood — menu, guest database, order history, delivery zones, promotions — is exportable today and gone on 30 April 2027, when Oracle shuts the servers down entirely. Exporting takes an hour or two. Do it this month, even if you haven't picked a replacement platform yet: the export is useful on any platform, and it's worthless after the deadline.

What can you export from GloriaFood?

Oracle has confirmed that operators can export the following until the shutdown date:

  • Menu data — items, categories, modifiers, and pricing
  • Customer database — your guests' names, emails, and phone numbers
  • Order history — every order with full details
  • Delivery zone configurations — your zones, fees, and minimums
  • Promotional setups — active and past campaigns

The reporting screens in your admin panel are the place to start: the Customer Report and Order History Report carry the data with the most long-term value.

Which order should you export in?

If you only do one thing today, make it the guest database. Everything else can be rebuilt by hand if it has to be. Your guests' contact details can't.

  • First: guests. Names, emails, phone numbers. This is the asset that keeps earning after the move — it becomes your launch announcement list on whatever comes next.
  • Second: menu. Items, modifiers, and prices. Saves hours of retyping, and any decent importer can work from it.
  • Third: order history. Your trading record — who orders what, when, and how often. Useful for marketing on the next platform and for your accountant regardless.
  • Fourth: zones and promotions. Quick to export, fiddly to remember accurately later.

What should you check after exporting?

An export you haven't opened is a backup you don't have. Five minutes of checking:

  • Open every file and confirm it has rows in it — not headers and nothing else
  • Spot-check guest records against what you see in the admin panel
  • Confirm the menu export carries modifiers and prices, not just item names
  • Store copies in two places you control — not only the laptop behind the till

Where does the data go next?

Any serious alternative can work from your exports. If you move to Storekit, the importer takes care of it — menu, guests, zones, and promotions in one pass, with you approving everything before it goes live — and the week-by-week playbook shows how the whole move runs. But the export matters whatever you choose. Operators who'll have a calm spring next year are the ones holding their own copies this year.

Frequently asked questions

Can I export after 30 April 2027?

No. The servers shut down entirely on that date. Anything not exported beforehand is permanently inaccessible.

Will Oracle move my data to a new platform for me?

No. Oracle provides no migration programme and recommends no vendors. The export — and what happens to it next — is on you or your next provider.

Does exporting affect my live GloriaFood ordering?

No. Exporting copies your data; it changes nothing about your live storefront. There's no downside to doing it early.

The export costs you an hour. Skipping it costs you every guest relationship you've built. Start your migration whenever you're ready — but export this month.

More from the blog