From MyTourist to Channex: how to migrate your B&B without losing bookings

Since 2021 I've been running B&B Burgemeestershof — four rooms in a former rectory. Until recently, all channel management went through MyTourist (MT). It worked, but every month I felt the cracks: no WhatsApp inbox next to the booking, Airbnb only via an iCal workaround, and increasingly frequent manual price updates on channels MT didn't handle directly.

Over the past weeks I've been migrating to Channex via BedFlow. Not all at once — controlled, channel by channel, with monitoring and a rollback plan. Below is the approach that worked for me, along with the pitfalls I hit along the way.

Why migrate at all?

The honest question first: why not just stay on MT? For those who are happy, that's a fine choice. But these limitations were dealbreakers for me:

• No WhatsApp inbox next to the booking. At Burgemeestershof, 67% of guest replies come via WhatsApp. Switching between WA and MT's PMS cost me hours per week.
• No direct Channex connection. Airbnb syncs ran via an iCal workaround — 1-hour lag, no price updates.
• Older PMS layer. Reports, mobile app, shortcuts — everything felt ten years old.
• Per-property billing. Adding a second property would have required a separate login + subscription.

Channex isn't "better" because it's newer. It's better because it's one standardized channel to 200+ OTAs, with bidirectional sync, mature error handling, and an outbox pattern that does retries automatically. For anyone syncing more than Booking.com, that's a different universe.

The risks you really have to address

Before you touch anything: three things can derail the migration.

1. Double push

The worst-case scenario: both MT and Channex push prices and availability to the same channel. You get random updates — sometimes MT wins, sometimes Channex. Result: overbookings or wrong prices you only notice days later.

Rule: for each channel, at any moment, there must be exactly one source system. No overlap, no "let's keep both for safety".

2. Mapping differences

MT's room codes (KAMER1, KAMER2, ...) do not automatically match Channex's room types. OTAs have their own room IDs (Booking has room_id, Expedia has room_type_id). Wrong mapping means bookings land on the correct OTA room but get booked into the wrong room in your PMS.

Rule: for every channel, verify the mapping manually with a real test booking before moving on.

3. OTA-specific "1 channel manager per account" policies

Airbnb in particular is strict: you can only have one PMS integration at a time connected to an account. If MT still has an old OAuth authorization, it has to be revoked first before Channex can even connect.

Rule: before connecting via Channex, check the OTA's "Connected apps" page and revoke all old tokens.

The order: why you don't switch everything at once

The temptation is to flip everything in one go on a quiet Sunday. That's exactly what you shouldn't do. My approach:

1. Canary channel (lowest volume). In my case Natuurhuisje via OpenGDS — 3-5 bookings per month. If something goes wrong the impact is low.
2. Mid-volume. Expedia + Check24 — sample size big enough to spot problems, small enough not to ruin your evening if it breaks.
3. Airbnb. Separate step because the OAuth flow is fundamentally different.
4. Booking.com last. 60-70% of my revenue. Doesn't move until I've seen every other channel run successfully for 72 hours.

At least 72 hours of monitoring between each step. No pressure to do everything in a week — the Burgemeestershof migration is taking about three weeks.

The per-channel flow

For every channel I follow exactly the same steps:

1. MT-side disconnect. Log into MT, go to the channel, choose "Disconnect channel manager". From this moment MT no longer pushes to that channel.
2. Wait 30 minutes. MT's queue processes its last pushes. Continuing earlier = double updates.
3. Channex connect via BedFlow. Link Channex credentials, fill in room mapping, assign rate plans.
4. Cross-check 1 — push test. In BedFlow, set a dummy price (e.g. +€10 on one date), after 60 sec check the OTA extranet to see if the price came through.
5. Cross-check 2 — pull test. Create a test booking on the OTA (or use a staging tool), check it appears in BedFlow within 2 minutes.
6. 72h monitoring. Three days of checking every morning: did all bookings come in? Are price/availability updates flowing? Any error messages?
7. GO or NO-GO. Green: move to the next channel. Red: rollback (turn MT back on for that channel, disconnect Channex).

Differences per OTA

Not every channel works the same way. The biggest differences I encountered:

Airbnb

• OAuth flow. No "enter your extranet ID" field, but a redirect to Airbnb to approve access.
• 1 PMS connection per account. First check under Account → Professional hosting tools → Connected apps whether there's still an old integration. Revoke it first.
• Sub-listings. Multiple units under one Airbnb account? Mapping per listing separately.
• iCal fallback becomes useless. Turn off your old iCal feeds the moment Channex is active — otherwise Airbnb keeps double-pushing messages.

Booking.com / Expedia / Check24

• Extranet-ID flow. Channex asks for your extranet ID and credentials. No redirect.
• Mapping tab required. Channex won't let you connect until every room + rate plan is mapped. No "we'll do that later".
• Check24-specific: some OTAs use their own room templates (Check24's COZIBA / COMZIM codes for example) that cannot be modified via Channex. These remain in the OTA extranet under their control — Channex only syncs price/availability on top.

OpenGDS (Natuurhuisje, VIPIO, CharmantHotel)

OpenGDS is an aggregator: one Channex connection pushes to multiple sub-feeds at once. Important check:

• Not every sub-feed accepts price updates instantly — some run their own review cycle.
• For each sub-feed, verify that updates actually arrive within the first 24 hours after connect.

Tools that genuinely make it safer

During my migration I leaned heavily on one dashboard: BedFlow's Migration overview (/admin/migration-overview). Per channel it shows live who is currently the source of truth — MT or Channex — and automatically flags when both are active at once. Without it I'd have to keep a manual spreadsheet of "channel X switched on date Y".

Other checks that proved useful:

• OTA extranet bookmark folder. One browser folder with direct links to every OTA's "Connected apps / Channel manager" page. Quick clicks during every channel switch.
• WhatsApp thread with your co-host or partner. Each GO/NO-GO gets one message. No secrets, no surprises.
• A checklist per channel. Boring, but essential.

Pitfalls I learned along the way

1. Stale OAuth authorizations on Airbnb. Four months earlier I had run an MT trial with Airbnb connection and never revoked it. Channex refused to connect until I cleaned up. 20 minutes lost — could have been prevented upfront.
2. OTA-side room templates. On Check24 I tried to rename the room via Channex. Not possible: their COZIBA codes are fixed. You change the OTA's own settings, not via Channex.
3. MT still "secretly" pushing. On one channel the MT disconnect "completed" but the queue still had 4 hours of historical updates. Continuing earlier would have caused double pushes. The 30-minute wait is not exaggeration.
4. Booking.com and seasonal peaks. Never migrate Booking.com during a busy booking week. I'm waiting for a quiet Tuesday morning.
5. Negative invoices still work. Side note: make sure your IBAN is filled in your new PMS for automatic payout of negative invoices to work.

Conclusion

An MT → Channex migration is not an evening's work. It's a structured two-to-four-week process, with monitoring, a rollback path, and accepting that some things only show up during execution (like that Airbnb OAuth in my case).

But it's not rocket science either. With the right order — canary, mid, Airbnb, Booking.com — and a good monitoring dashboard you keep it manageable. No lost bookings, no double pushes, no overbookings.

Want to make your own migration safer? BedFlow's migration overview and 30-day trial give you the frame to walk through this in a controlled way. More info and pricing at bedflow.eu/pricing.