# How to export your GloriaFood data before the shutdown

> A guide checked in the dashboard: customers and orders export with a button, the menu does not. Exact paths, the API that gets your menu out, and what has to be screenshotted.

Publié le August 17, 2026 · Mis à jour le August 17, 2026 · Delova

GloriaFood shuts down on 30 April 2027, and Oracle has announced no data retention. Anything you have not exported by then is gone.

This guide tells you **exactly what you can export yourself, what you cannot, and how to get the rest anyway**. The paths below were checked in a real GloriaFood dashboard, not copied from other sites: several guides doing the rounds describe a menu export that simply does not exist.

## In thirty seconds

| Data | Self-service export | Where |
|---|---|---|
| **Customers** | ✅ yes, `Export` button | Reports → Show list → Customers |
| **Orders** | ✅ yes, same place | Reports → Show list → Orders |
| **Menu** | ❌ **no export** | via the API only (below) |
| Delivery zones, hours, fees, VAT | ❌ no export | screenshots required |

The most valuable item, and the longest to retype, is precisely the one you cannot download in a click.

## 1. Customers and orders really do export

In the dashboard, the chart icon opens the **Reports** section. At the bottom of the left column is **Show list**, which expands into two entries: **Orders** and **Customers**.

On both pages, below the table, there is an **Export** button.

The direct address of the customer list, if you would rather paste it:

```
www.restaurantlogin.com/admin/restaurant/reports/listview/clients
```

Do this first. It is the file that is worth the most in the long run: your customers stay yours when you change systems, and no provider will hand them back if you lose them now.

## 2. The menu: here is the bad news

In the menu editor, the three-dot button at the top offers only three entries: **Montrez-moi** (a walkthrough), **Change theme picture** and **Ajuster les prix**. No export, in any form.

Checked directly in the interface. If you have read elsewhere that you just go to "Setup → Menu Editor → Export menu (CSV)", that menu entry does not exist. You are not looking badly: the button is not there.

Two routes remain.

**A. The manual copy.** Open the menu editor, expand every category and every option group, then print the page to PDF. Tedious, but within anyone's reach, and enough to lose nothing. On a menu of two hundred dishes with their variants, allow an hour or two.

Remember to expand the **Choix et Extensions** panel on the right as well: that is where your option, add-on and cooking groups live. They do not print alongside the dishes, and they are the bulk of the retyping work later.

**B. GloriaFood's API.** The dashboard exposes a dedicated integration:

```
Online ordering → Integrations → Your integrations
www.restaurantlogin.com/admin/restaurant/other/integrations/list/index
```

There you will find, or create with **Add integration**, an integration of type **Fetch Menu API**, protocol json version 2. The row shows an endpoint, a **restaurant key** and a **server key**.

Those keys let you retrieve the entire menu, **options and add-ons included**, in a structured format. It is the only complete route. It does require someone able to query an API: it cannot be done from the dashboard.

If a prospective provider promises you a "one-click import", this API is what they mean. Ask them to confirm it, and above all ask whether they carry over the option groups or only the dishes.

> **Worth noting:** both keys are displayed in plain text, readable by anyone with access to the account. If several people log in, keep that in mind.

## 3. What does not export at all

None of these settings has an export, anywhere:

- delivery zones and their boundaries
- delivery fees and minimum orders
- opening hours and preparation times
- VAT rates and payment configuration
- running promotions

For all of them: **one screenshot per screen**. It looks crude, but it is the only way, and reconstructing them from memory six months later does not work.

## 4. The order of operations, starting now

1. Export **customers** and **orders** from the dashboard.
2. Print the **full menu** to PDF, every option group expanded.
3. Take **screenshots** of zones, hours, fees and promotions.
4. Store all of it outside the dashboard.

Only then choose a replacement. The closer the date gets, the slower support becomes and the more erratic the exports get, exactly when you need them.

## Frequently asked questions

**How much time do I have?**
Until 30 April 2027. But the service already takes no new signups, and features degrade as a shutdown approaches. Do not wait until 2027.

**Will Oracle keep my data?**
No. No retention or archiving has been announced beyond the shutdown.

**What does the customer export look like?**
A file you download from the customer list. It contains the contact details gathered through your orders.

**Can I really not get my menu out without a technician?**
Not in structured form. The PDF makes sure you lose nothing; to load it automatically elsewhere, the API is the only way.

**What if I signed up through a reseller?**
GloriaFood is also distributed by partners who put the dashboard in their own branding. The paths and labels stay the same.

**The "Add integration" button is in English, is that right?**
Yes. Parts of the interface stay in English whatever your language. It does not mean you took a wrong turn.

## What next?

With your data safe, a replacement still has to be chosen. We compare the options in our [article on GloriaFood alternatives](/en/blog/alternative-gloriafood), and summarise the facts of the shutdown on [our page about it](/en/blog/gloriafood-fermeture).

We have already done this migration ourselves, options and add-ons included: if you like, [we will handle it](/en/demo).

*Paths checked in a GloriaFood dashboard on 18 August 2026. Source: [GloriaFood home page](https://www.gloriafood.com/).*