GloriaFood Migration Checklist: Move Your Restaurant Ordering Before the 2027 Shutdown

GloriaFood is being retired by Oracle on 30 April 2027. If your restaurant takes online orders through it today, that is a hard date on your calendar — the ordering button on your website and your Google profile will stop working, and every link you have printed, posted, or embedded points at a service that will go dark.

The good news: a migration is not an emergency if you plan it. You are not rebuilding a restaurant — you are moving a menu and a set of links from one system to another. This checklist walks the move in order, from exporting what you have today to switching your links on the new platform, so nothing gets lost and no customer ever hits a dead ordering page.

Why Start Now Instead of Next Spring

The deadline sounds far away, but the parts you cannot rush are the parts that matter. Rebuilding a menu is fast; getting your Google Business Profile ordering link updated and re-crawled, retraining staff, and reprinting QR codes and flyers takes real calendar time. Do it under pressure the week before shutdown and something will slip.

There is also a quieter reason. A migration is the one moment you get to reset your ordering setup for free — better menu photos, cleaner categories, delivery zones that actually match where you deliver, a second language for tourists. If you rush, you copy your old setup, warts and all. If you plan, you come out the other side better than you went in.

The Migration Checklist

Work through these seven steps in order. Each one unblocks the next, and you can pause between any of them without losing progress:

• •1. Export or record your current menu. Capture every category, item, price, description, and photo exactly as it is now. Screenshot your live menu, save the images at full resolution, and put the prices in a simple spreadsheet. This is your source of truth for the rebuild — do it while the old system is still up.
• •2. Save your customer contact list where you can. Export any email or phone list your current setup lets you download. If export is limited, at minimum record the totals and any repeat customers you know by name, so you can invite them to order again once the new page is live.
• •3. Pick a replacement that fits your channels. List how customers actually reach you — QR dine-in, delivery, pickup, reservations — and match a platform to that. Check for the essentials you rely on: multi-language menus, EU data residency, and an API if you connect other tools. Do not pay for channels you will never use.
• •4. Rebuild the menu in the new system. Recreate categories, items, prices, and descriptions from your step-1 record, then upload the photos. Some platforms import from a menu URL or a CSV so you do not retype everything — check whether yours does before you start typing item by item.
• •5. Place the new ordering widget or link everywhere the old one lives. Your website, your Google Business Profile, your Instagram bio, any flyers or table signs. Make a list of every place the old GloriaFood link appears so none get missed.
• •6. Test a real order end to end. Order from a customer phone, pay if you take payment, and confirm it lands in your kitchen or admin the way you expect. Fix anything broken now, while nobody is watching.
• •7. Go live and switch links before the deadline. Flip your public links to the new system well ahead of 30 April 2027, but keep the old ordering path reachable until you are confident the new one handles a normal service without surprises.

Rule of thumb: switch your links at least a month before the shutdown, not the week of it. That buffer lets Google re-crawl your ordering link and gives you one real weekend of service on the new system while the old one is still there as a safety net.

How to Do the Hard Parts Well

Rebuild the menu without retyping it all

The menu is the biggest chunk of work, and it is where a good platform saves you hours. Before you start typing a hundred items by hand, check whether your new system can import from a menu URL or a CSV file — many can, and it turns an afternoon of data entry into a few minutes of review. If you serve tourists or a mixed neighbourhood, add a second language while you are in there; doing it during the rebuild is far easier than bolting it on later. See the Multi-language feature page for how one menu can serve several languages at once.

Match the platform to how people actually order

Do not choose on price alone. If most of your orders come from diners at the table, QR dine-in ordering is the feature that pays for itself — see the QR Code Menus feature page for what that looks like in practice. If you run your own drivers, you want delivery zones and driver tools, not just a checkout. And if you connect a POS or a kitchen display, confirm the new system talks to it — the POS Integrations feature page lists what connects out of the box. Owning your ordering page also means you keep your margin and your customer data instead of handing a marketplace its 15–30% typical cut on every order.

Test before you trust it

The single step people skip is the one that catches everything: place a real order yourself before you announce anything. Use a phone that is not logged into your admin, add a couple of items, apply a discount code if you use them, and pay the way a customer would. Watch the order arrive, check the receipt, and confirm the kitchen sees it. Ten minutes here saves a chaotic first Friday night.

A Realistic Timeline Back From 30 April 2027

You do not need months, but you do need a buffer. Working back from the 30 April 2027 shutdown, a comfortable plan is roughly this: give yourself the whole of March to export your menu and pick a replacement, the first week of April to rebuild and test, and switch your public links by mid-April — leaving two clear weeks with both systems reachable before the old one closes. If you would rather not cut it that fine, everything after "pick a replacement" can be done in a single focused week, so even a late start is recoverable as long as you do not wait for the final days.

When you are ready to compare options, our companion posts walk the decision through: read "GloriaFood is closing — what restaurants should do" for the plain overview, and "what to look for in an online ordering replacement" for the feature-by-feature checklist. If you want a quick read on where your current setup stands, the AI Restaurant Grader scores your online ordering and menu presence in a couple of minutes and points at the gaps worth fixing during the move. Ordering.Tools covers QR dine-in, delivery, pickup, multi-language menus, and POS connections in one place — a natural landing spot for a menu leaving a retiring system, with time to spare before the deadline.