Get Started
Role Guides
Kaptio Platform Architecture
Global Platform Setup
Getting Started with Core Configuration
Managing Users, Roles & Access
Understanding Your Sample Data
PIM: Supplier Contracting
PIM: Tour & Package Design
CRM Module
Setup Trip & Itinerary Workflow
CONNECT: Land & Air Connectivity
Getting Started with Connectivity
Hotel Connectivity Setup & Usage
DOCS Module
Building Custom Content Components
Using the Document Starter Kit
Using the ATOL Certificate Starter Kit
Advanced Sample Email Template
CRS: Training Guides
PAY: Payment Gateway Integrations
Data Migration
Peripheral Integration Guides
Kaptio does not offer a loading template to migrate legacy or active bookings from our customers' legacy systems. However, we have assisted customers over the years in finding ways to extract value from their legacy bookings. Additionally, we can help with the transition of any active bookings that have not yet traveled in their current legacy reservation system. This document provides a good overview of the recommended approach for both areas.
A definition of a legacy booking is a specific client itinerary that has already travelled in the past. This can in some cases also include quotes that did not convert. Providing your users with this data helps build up a full picture of the client (whether that is B2B or B2C) from a booking timeline perspective.
If legacy booking data needs to be retained, it is important to understand what data points should be stored and for which department and use case. The key questions that we advise clients to take into consideration are:
Bookings in other reservation systems tend to be stored in a different structure compared to the Kaptio Travel data model. Because of this differing structure, Kaptio does not support transforming legacy data into the Kaptio Travel Itinerary object model due to complexity. If you are considering migrating your legacy bookings - and you feel you have good reasons to do so (see questions in the previous section), Kaptio recommends that customers create custom objects that represent the legacy bookings in a new flat structure just to keep a legacy data and reference to the Account object model (for 360° view purposes).
In order to achieve this, two new custom objects can be defined within Salesforce by your Salesforce administrator:
The account object can then be extended to be linked to these new objects, data transformed and then imported into this structure. Due to the different circumstances of each client and data set, Kaptio does not have any out-of-the-box objects or functionality, but adding these custom objects is straightforward and gives you more control over what data you want to retain.
Below is a starting point for the data points to consider for the Legacy Booking object: