Supplier Integration Version Migration

This document outlines the standard operating procedure (SOP) for migrating connected Buyers from an existing supplier integration (Old Version) to a newly developed integration (New Version) within the Travelgate ecosystem.

Because Travelgate treats a new integration version as an entirely separate technical integration, specific credentials, setup, and legacy-support protocols must be followed to ensure uninterrupted booking operations.

What Happens When a Supplier Releases a New Integration Version?

When a Supplier develops a new version of their integration on Travelgate, migrating existing Buyer traffic involves two parallel architectures running side-by-side:

1. New Integration Architecture: The New Version operates on separate connection endpoints and parameter definitions.
2. Legacy Connection Lifecycle: Existing reservations made through the Old Version cannot be accessed or updated by the New Version. Legacy access must remain active until all active future bookings reach check-out.

How Does the Migration Process Work?

Phase 1: Seller Visibility Strategy

Before migration begins, the Seller must formally define their commercial strategy regarding new incoming connection requests. The Seller must confirm one of the following options with the Travelgate team:

• Option A (New Version Only): The Old Version is no longer available for any new Buyer connection requests. Only the New Version remains listed in the Marketplace for new connections.
• Option B (Parallel Availability): Both the Old Version and the New Version remain available for new Buyer connection requests in parallel.

Phase 2: Credential & Parameter Setup

Because the New Version operates on an independent technical architecture, it requires updated or differently formatted connection parameters.

• Requesting New Credentials: The Seller must generate dedicated credentials formatted specifically for the New Version for each Buyer.
• Credential Recycling is Not Allowed: Legacy credentials cannot be reused on the new integration. A brand-new credential request must be formally submitted under the New Version's environment.

Phase 3: Buyer Migration & Connection

Once new credentials are generated by the Seller:

1. Submit Connection Request: The Buyer requests a new connection on the Travelgate platform and configures the parameters provided by the Seller. (Buyers migrating from legacy connections must coordinate setup timing with the Seller).
2. Testing & Environment Certification: The Buyer performs testing and certification within their staging environment.
3. Production Switch: Upon successful testing and certification, the connection is switched to Live/Production, and new booking traffic is routed through the New Version.

Phase 4: Legacy Connection Maintenance (Critical)

Do not deactivate the Old Version prematurely

Do not disconnect or deactivate the Old Version immediately after the Buyer goes live on the New Version. The connection to the Old Version must remain active as long as there are pending, future bookings tied to it.

• Modifications & Cancellations: Reservations created via the Old Version can only be modified or cancelled through that specific legacy connection. The New Version cannot manage bookings created prior to its activation (unless the Seller explicitly provides an alternative dedicated endpoint for legacy management).
• Final Decommissioning: The Old Version should only be deactivated for a specific Buyer after the check-out date of the final reservation made on the legacy integration has passed.

Troubleshooting & Common Pitfalls

Issue / Scenario	Root Cause	Resolution
New Version fails authentication	Buyer attempted to reuse Old Version credentials on the New Version endpoint.	Submit a new credential request under the New Version environment to generate separate parameters.
Unable to modify/cancel existing booking	Legacy connection was deactivated prematurely after Go-Live on the New Version.	Re-enable the Old Version connection until the check-out date of the last legacy reservation passes.
Missing product/room mapping	Parameter structure changed between Old and New versions.	Coordinate a fresh product mapping update between Buyer and Seller systems prior to switching production traffic.

Need help with a specific case?

Reach out via our Support Portal for Product Maintenance requests, or see Customer Support Resources for an overview of all support channels.