The argument for leaving TheFork always ends the same way: “but if I go, I lose the customers who come through there.” It’s a legitimate fear. TheFork has a real presence in Spain and some of its users book directly from the app without searching for the restaurant by name. The real question isn’t whether you should leave — the numbers speak for themselves — but how to do it without cutting off booking flow before you’ve built the alternative.

This article lays out the concrete process, with real timeframes and actions per phase.

Before you start: understand where your bookings actually come from

The first mistake in the migration is not knowing how many bookings TheFork actually brings you. Restaurants tend to overestimate it because it’s what’s in front of them on screen. The direct channel — phone, WhatsApp, web form, Google — tends to be undercounted.

Before doing anything, spend three weeks logging the source of every booking:

Channel	How to identify it
TheFork	Shows up in the TheFork panel and in the confirmation email
Phone / WhatsApp	Manual log or incoming call record
Own website	Contact form, own booking widget
Google / Maps	”Book” directly from Google Business Profile
Instagram / social	DMs or bio link
Walk-in	No prior booking

When you finish the count, apply the 30% rule. If TheFork accounts for less than 30% of your total bookings, the migration is almost risk-free: you have a solid enough base of direct channels to absorb the transition. If it accounts for more than 50%, you need the full four-phase plan.

The four-phase plan

Phase 1 — Build the direct channel (weeks 1 to 6)

Don’t drop TheFork yet. Build the alternative first.

In this phase:

Set up your own booking system on your website. It needs to be visible from Google (it shows up on your Google Business Profile), easy to use on mobile and able to send email confirmations. If you don’t have your own website, this is the moment to build one — not the other way round. A website with bookings built in from day one is more efficient than bolting on the widget afterwards.

Update your Google Business Profile so the booking button points to your own system, not TheFork. The “Book” button on Maps generates between 15 and 40 bookings a month for a restaurant with 4+ stars in an urban area. That’s free traffic which right now may be going to TheFork.

Collect emails. Every time you confirm a booking from any channel, ask the customer if they’d like to hear about news or special menus. Not to sell to them: to have a direct channel before TheFork is the only thread connecting you to that customer.

Set up automatic WhatsApp replies with a link to your direct booking. Many restaurants get 20–30 WhatsApp conversations a month where someone asks “do you have a table on Friday?”, and the link to your own booking system turns that message into a booking without any manual intervention.

Phase 2 — Dual channel active (weeks 6 to 16)

In this phase you have both platforms running at the same time. The goal isn’t to balance them: it’s to grow the direct channel until the volume gap justifies the TheFork spend.

How do you know if the gap justifies it? With this simple calculation:

TheFork bookings/month × people/booking × commission/cover + visibility fee = real monthly cost

For a typical restaurant with 50 bookings/month at 2.5 people and €3.50/cover:

Item	Calculation	Total
Per-cover commission	50 × 2.5 × €3.50	€437.50
Visibility fee	fixed	€150.00
Real monthly cost		€587.50

If by that same week 16 your direct channel already generates 30 bookings a month and you know it will keep growing, you’re paying €587 for the 20 bookings that come from TheFork: €29 per booking. At that point it’s no longer worth it.

During this phase:

Don’t cut prices on TheFork. Activating Yums to offset a possible visibility drop gets expensive — we covered that in the 2026 TheFork cost breakdown.
Do tell your regular customers that they now have a direct booking option. A simple line when they call: “You can also book directly through our website, no need to go through TheFork.”
Track the direct/TheFork ratio weekly. The goal is for the direct channel to reach 60% of the total before moving to phase 3.

Phase 3 — Gradually scaling back TheFork (weeks 16 to 24)

Once the direct channel accounts for 60% or more of your bookings, it’s time to scale back TheFork — not cancel it outright.

Actions in this phase:

Switch off paid visibility. If you have an active Premium plan, drop it to the free tier. You’ll lose ranking within TheFork, but if your direct channel is already mature, the drop in TheFork volume will be modest — and the saving on the fixed fee is immediate.

Drop the Yums programme. Without automatic discounts, the bookings that do come through will be at full price. Less volume but better margin per cover.

Keep the TheFork profile active with basic information up to date (hours, menu, recent photos). It works as a shop window for anyone discovering the restaurant on the platform for the first time, who then books directly via Google or your website after seeing it. The profile has value as a presence even when you’re not paying commission.

Phase 4 — Closing or minimal upkeep (month 7 onward)

At this point you have two options depending on your situation:

The goal from month 7 onward is to eliminate marketplace dependency and consolidate all booking traffic on your own website, whether the restaurant is in an established local area or an international tourist zone.

Established local area. Closing the paid contract has no meaningful opportunity cost: customers already find you through Google, word of mouth or phone. Your own website with Bouzon Bookings takes on 100% of the flow.
Tourist zone (central Barcelona, Madrid’s Retiro/Sol, Seville’s old town, Marbella, Mallorca, the Canary Islands). Here the lever for attracting tourists isn’t the marketplace but your own website with a bilingual ES/EN menu + local SEO + an optimised Google Business listing, which appears in the searches tourists actually run on Google (“best paella Barcelona”, “restaurant near Sagrada Familia”) and doesn’t depend on paying commission per cover. Build up local SEO + Google Business before month 7 so closing the marketplace doesn’t leave a gap.

After 60–90 days with your own website working as the main channel, the accumulated saving versus the marketplace’s fee plus per-cover commission usually exceeds €5,000.

The data you can’t afford to lose before you leave

TheFork doesn’t export customer history or emails. Before scaling back the contract, do this:

Download all historical bookings that the panel lets you export (transaction CSV). It’s volume data, not customer data, but it gives you a picture of which months see the most TheFork demand.
Identify your repeat customers — those who’ve booked three or more times: you can see their names in the history even without an email. Next time you have direct contact — when they call or walk in — you can ask for their email for your list.
Screenshot your ratings and reviews. They aren’t portable, but they’re content you can use as a testimonial on your website or respond to publicly before closing the profile.
Download any photos you’ve uploaded to TheFork. They’re yours. You’ll need them for your Google profile and for your own website.

How long the full transition takes

Most restaurants complete the process in 5 to 7 months if they follow the plan. Those who do it cold-turkey — cancelling TheFork and switching on their own bookings the same day — see a 25–40% drop in bookings during the first two months and end up forced to go back.

The cost of doing the migration properly is time: four phases over roughly half a year. The return is eliminating a recurring expense of €4,000 to €25,000 a year depending on volume, and getting ownership of your customer data back.

An own booking system with an integrated website costs from €49.99/month with no per-cover commission. For the restaurant in the example above (€587/month on TheFork), the net saving from month 7 is €538 a month — €6,456 a year.

If you want to see how a booking system integrated into your own website works, try the live demo →

How to Migrate Your Reservations from TheFork to a Commission-Free System Without Losing Customers