This process applies to Property Managers who are currently connected to Expedia through Single Rate and want to migrate their properties to the Content API connection in Channel PRO.
The migration is coordinated primarily by Expedia, with Avantio supporting the technical transition.
Important: This is a controlled migration process. The migration is not started or completed directly by the Property Manager from Channel PRO.
Prerequisites
Before starting the migration, the property manager must have:
An active Expedia group contract.
A valid Property Manager Code (PMC) provided by Expedia.
The PMC is case-sensitive and must always be provided by Expedia.
A defined Business model:
Expedia Collect
Hotel Collect
Or both
Migration Process Overview
Step 1: Request the migration from Expedia
The Property Manager must contact Expedia and request the migration from:
Expedia Single Rate → Expedia Content API.
Expedia reviews the request and prepares the account for the migration.
Step 2: Expedia contacts Avantio
Once Expedia has prepared the migration:
Expedia contacts Avantio's Connectivity Team.
Expedia provides the information and documentation required to initiate the migration, including the applicable onboarding and migration information.
The migration cannot be initiated directly by the Property Manager in Channel PRO.
Step 3: Provide the required information
The following information may be required to proceed with the migration:
Property Manager Code (PMC) — provided by Expedia.
Business model — Expedia Collect, Hotel Collect, or both.
Cancellation policy applicable to the properties.
VAT percentage applicable to the rentals.
Package rates — Yes / No.
This information is normally coordinated through the communication between:
Expedia's Onboarding team
The Property Manager
Avantio's Connectivity team
Step 4: Properties included in the migration
The migration includes all properties that are currently connected to Expedia through the Single Rate connection.
Properties in the Avantio portfolio that are not currently connected to Expedia through Single Rate are not included in this migration.
For example, if a Property Manager has 100 properties in Avantio but only 80 are connected to Expedia through Single Rate, the 80 connected properties will be migrated to the Content API.
Important: The migration is performed for all eligible properties as part of the same migration process.
Step 5: Technical migration
Once the required information and properties have been confirmed:
Avantio creates the corresponding internal technical task.
Avantio and Expedia perform the technical migration.
The properties are placed under STOP SELL during the applicable migration process.
During this phase, technical validation and mapping are performed between Avantio and Expedia.
Step 6: Validation and completion
Once the migration has been completed, Expedia reviews the migrated properties on its side to validate the connection and synchronization.
Once Expedia completes its validation, the migration project is considered completed by both Expedia and Avantio.
Expedia Single Rate vs. Expedia Content API
Feature | Expedia Single Rate | Expedia Content API |
Channel in Avantio | Channel PRO | Channel PRO |
Connection type | Single Rate | Content API |
Property activation | Existing Expedia properties are mapped using the applicable Expedia IDs | Properties can be activated and managed through Channel PRO |
Property creation | Not supported through the same activation process | New Expedia establishments can be created through the Content API activation flow |
Hotel ID management | Existing Expedia IDs are used for mapping | Existing properties can be linked or new properties can be created |
Rate synchronization | Single Rate structure | Supports more advanced rate structures |
Discounts and supplements | More limited | Supports additional discount and supplement configurations |
Package rates | Not supported | Supported |
Availability synchronization | Supported | Supported |
Pricing synchronization | Supported | Supported |
Photos and property content | Not supported | Supported through the Content API |
Business models | Expedia Collect / Hotel Collect | Expedia Collect / Hotel Collect / both, depending on the configuration |
Property activation and deactivation | Managed according to the Single Rate connection flow | Managed through Channel PRO's Accommodation Activation flow |
Important information before starting the migration
Before the migration begins, consider the following:
Properties included in the migration will be placed in STOP SELL on Expedia during the migration process.
Properties will only be reopened for sale once Expedia has completed its validation.
No fixed migration timeframe can be guaranteed.
Once the migration has started, do not make changes to the Expedia configuration or properties included in the migration until the process has been fully completed.
If changes are required during the migration, coordinate them with the Avantio Connectivity team before making them.
Important: Making changes while the migration is in progress can interfere with the migration and may result in additional validation or delays.
Key points
The migration changes the connection from Expedia Single Rate to Expedia Content API.
Both connections are managed through Channel PRO; Channel PRO is not what is being migrated.
The migration is coordinated by Expedia and Avantio and is not completed directly by the Property Manager.
The migration applies to all properties currently connected to Expedia through Single Rate.
Properties that are not connected to Expedia through Single Rate are not included in the migration.
All eligible properties are migrated in a single migration process, rather than in separate batches.
STOP SELL applies to properties while they are undergoing the migration.
Do not make changes to properties included in the migration once the process has started.
Once the migration is completed, Expedia performs its final validation and the project is then considered completed by both parties.
FAQs
Can I migrate from Single Rate to Content API directly from Channel PRO?
Can I migrate from Single Rate to Content API directly from Channel PRO?
No. The migration is a controlled process coordinated by Expedia and Avantio. It is not completed directly by the Property Manager from Channel PRO.
Do I need to contact Expedia to request the migration?
Do I need to contact Expedia to request the migration?
Yes. The migration process starts with the Property Manager contacting Expedia and requesting the migration from Single Rate to Content API.
Is Channel PRO changing during the migration?
Is Channel PRO changing during the migration?
No. Both Single Rate and Content API are managed through Channel PRO. The migration changes the connection type, not the Avantio interface.
Which properties are included in the migration?
Which properties are included in the migration?
The migration includes all properties that are currently connected to Expedia through Single Rate. Properties that are part of the Avantio portfolio but are not currently connected to Expedia through Single Rate are not included in the migration.
Can I continue making changes to my Expedia properties during the migration?
Can I continue making changes to my Expedia properties during the migration?
No. Once the migration has started, do not make changes to the Expedia configuration or to the properties included in the migration until the process has been completed.
Will my properties continue receiving bookings during the migration?
Will my properties continue receiving bookings during the migration?
No. Properties included in the migration are placed in STOP SELL on Expedia while the migration is in progress. They are reopened for sale after Expedia completes its validation.
How long does the migration take?
How long does the migration take?
There is no fixed migration timeframe that can be guaranteed. The duration depends on the technical migration and the validation performed by Expedia and Avantio.
What happens after the technical migration is completed?
What happens after the technical migration is completed?
Once the migration is completed, Expedia reviews the migrated properties on its side to validate the connection and synchronization. After Expedia completes its validation, the migration project is considered completed by both Expedia and Avantio.
What is the Property Manager Code (PMC)?
What is the Property Manager Code (PMC)?
The Property Manager Code (PMC) is a code provided by Expedia and required for the Content API migration. It is case-sensitive and must be supplied by Expedia.