OVERVIEW
For some customers, a legacy hotel connector has been the single remaining obstacle standing between their current configuration and the new Concur Travel experience and that barrier is now being removed. SAP Concur is deactivating legacy hotel connectors in two structured phases, beginning 2 December 2026, as part of our continued investment in the modern travel platform. This is not simply a retirement of old technology rather it is an active step toward ensuring all eligible customers can benefit from the capabilities, content options, and traveler experience that new Concur Travel delivers. Understanding the phases, the connector options available to you, and what happens at each deactivation date will help you and your TMC plan a smooth, uninterrupted transition.
WHAT'S CHANGING
- Legacy hotel connectors will be deactivated in two phases: configurations with 10 or fewer bookings during the May–October 2026 measurement period will be deactivated on 2 December 2026, while configurations with more than 10 bookings over the same period will be deactivated at the end of March 2027.
- Approximately 62% of affected configurations fall into Phase 1, meaning the majority of impacted customers will transition on the December 2026 date making early preparation especially important for this group.
- When a legacy hotel connector is the sole remaining blocker preventing migration to new Concur Travel, deactivation of that connector will automatically trigger migration of the configuration to the new experience, removing the need for a separate manual migration step.
- If no new Concur Travel hotel connector has been enabled by the applicable deactivation date, GDS will automatically become the default hotel content source for that configuration, ensuring continuity of hotel content access.
- There is no dedicated Booking.com connector in new Concur Travel, so customers currently relying on Booking.com content will need to transition to a TMC-supported hotel connector, an alternative hotel content provider, or GDS hotel content before their deactivation date.
- A broad range of hotel aggregators is available in new Concur Travel, including TMC-aligned solutions such as Amex GBT Supplier Marketplace (SMP), BCD TripSource, CWT RoomIt, and CTM, as well as corporate aggregator solutions from HRS, Omnibees, Gekko Tech, DER, CRC, CDS, and others, all of which support the GDS + one configuration commonly used to access Booking.com equivalent content.
- TMCs will work directly with SAP Concur's Travel Innovation and Engagement (TIE) team to facilitate deactivation and migration, meaning customers should engage their TMC early to confirm the right connector solution is in place before the relevant phase date.
- Release notes covering this change in full detail will be published in November 2026, providing a final reference point before Phase 1 deactivation begins.
WHO IS AFFECTED
- This change affects Professional Edition customers hosted on the US2, EU2, and APJ1 data centers whose configurations currently use legacy hotel connectors.
- IT administrators and travel program managers are the primary audience for action, as they will need to coordinate with their TMC to review affected configurations and ensure an appropriate new Concur Travel hotel connector is enabled ahead of the relevant deactivation date.
- Customers using Booking.com content via a legacy connector have a specific content transition to plan, as there is no direct Booking.com equivalent in new Concur Travel.
- End users are not required to take any action, but travel managers should be aware that the hotel content available to travelers may shift depending on which connector solution is enabled before deactivation.
TIMELINE
- Phase 1 deactivation - 2 December 2026: Legacy hotel connectors are disabled for configurations with 10 or fewer bookings during the May–October 2026 measurement period. This represents approximately 62% of all affected configurations.
- Phase 2 deactivation - End of March 2027: Legacy hotel connectors are disabled for all remaining configurations, those with more than 10 bookings over the same May–October 2026 period.
ACTION REQUIRED
- No action is required for the connector deactivation itself to take effect. Deactivation will occur automatically on the applicable phase date. However, customers and their TMCs are strongly encouraged to act before that date.
- First, review all configurations that currently rely on a legacy hotel connector to understand which phase applies to each.
- Second, if your legacy hotel connector is the only blocker to migrating to new Concur Travel, prepare for automatic migration to the new experience when deactivation occurs.
- Third, work with your TMC to enable the appropriate new Concur Travel hotel connector before your deactivation date to ensure your preferred hotel content source is in place.
- Fourth, if your program currently uses Booking.com content, identify a replacement content source now with options include TMC-supported aggregators, alternative hotel content providers, or GDS hotel content. Your TMC will coordinate with SAP Concur's Travel Innovation and Engagement (TIE) team to manage the deactivation and migration process.
For more information on new Concur Travel, review the below resources that are made available for you.
If you have questions specific to your configuration or content strategy, your SAP Concur account team is the right starting point for tailored guidance.
