This process applies to property managers who are currently connected to Expedia via single rate connection (Channel v1.0) and need to migrate to the Expedia Content API (Channel PRO).
The migration is coordinated primarily by Expedia, with Avantio supporting the technical transition.
Note: This is a controlled migration process and is not managed directly by the property manager inside the Channel Manager.
Prerequisites
Before starting the migration, the property manager must have:
An active Expedia group contract
A valid Property Manager Code provided by Expedia
(case-sensitive and always supplied by Expedia)A defined Business model:
Expedia Collect
Hotel Collect
Or both
Migration Process Overview
Step 1: Request Migration to Expedia
The property manager must contact Expedia and request the migration from:
Expedia Single rate (Channel v1.0)
toExpedia Content API (Channel PRO)
Expedia reviews the request and prepares the account for migration.
Step 2: Expedia Contacts Avantio
Expedia contacts Avantio’s Connectivity Team to initiate the migration.
Expedia shares the required onboarding documentation, including:
API Partner Form
Migration instructions for existing properties
Step 3: Information Required for Migration
The following information is required to proceed. Some data is provided by Expedia, and some by the Property Manager:
Property Manager Code (provided by Expedia)
Business model (Expedia Collect / Hotel Collect / Both)
Cancellation policy applicable to the properties
VAT percentage applicable to rentals
Package rates (Yes / No)
This information is usually shared via a single email thread involving:
Expedia's Onboarding team
The Property Manager
Avantio's Connectivity team
Step 4: Property Selection
The property manager must select which properties will be migrated.
Migrations are currently performed in batches of up to 10–15 properties. This criteria is under review by Avantio, with the goal of enabling larger migration batches.
Larger portfolios are migrated in multiple phases.
Step 5: Technical Migration
Avantio creates an internal technical task.
The technical teams at Avantio and Expedia perform the migration.
This is the most critical phase, where technical issues may arise and cause delays.
Step 6: Validation and Go-Live
Once the migration is completed, Avantio shares the Hotel IDs with Expedia.
Expedia validates synchronization on their side.
After confirmation, Expedia reopens the properties for sale.
Expedia Single rate Vs. Expedia Content API
Feature / Area | Expedia Single rate (Channel v1.0) | Expedia Content API (Channel PRO) |
Channel in Avantio | Channel v1.0 | Channel PRO |
Connection Type | Single rate integration | Modern Content API integration |
Property Activation | Manual mapping using Hotel ID, Room ID, Rate ID | Activation directly from Channel PRO |
Property Creation | Not supported | Supported (new establishments can be created) |
Hotel ID Management | Managed manually by PM | Created or linked automatically |
Rate Synchronisation | One base rate only | Advanced rate structures |
Discounts & Supplements | Very limited | Improved support |
Package Rates | Not supported | Supported |
Availability Sync | Yes | Yes |
Pricing Sync | Yes | Yes |
Photos & Content Sync | Not supported | Supported |
Business Models | Expedia Collect / Hotel Collect | Expedia Collect / Hotel Collect / Combined |
Stop Sell Handling | Manual | Controlled by Expedia during migration |
Scalability | Limited | High |
Future Support | Legacy / Limited | Actively developed |
Recommended For | Existing legacy connections | New connections and migrations |
Important Information
Before deciding to migrate, the property manager must consider the following:
During the migration, all properties will be in STOP SELL on Expedia
Properties will only reopen byb Expedia once their Onboarding team has validated the migration
No estimated migration timeframe can be guaranteed
Once the migration starts, the property manager must not make any changes related to Expedia until the migration is 100% completed
Key Points
This process migrates Expedia from the single rate connection (Channel v1.0) to Content API (Channel PRO)
The migration is initiated and controlled by Expedia and Avantio
Properties are migrated in controlled batches
Stop Sell applies during the entire migration
No changes should be made during the process to avoid errors or delays