Tourism and hospitality: data brought back to Canada, with no production downtime.
How a hospitality group brought its data and applications hosted in the United States back to Canada, while its properties kept operating.
Bringing its data and applications back to Canada without stopping operations.
The problem
The group's data and applications were hosted in the United States. The group wanted to bring them back to Canada.
The properties operate every day and their systems cannot stop. With more than 25 sources and 22 schemas, a migration done all at once would have interrupted bookings and operations.
We connected the group's more than 25 sources and keep them in sync in one place, hosted in Canada.
- Booking system
- Point of sale
- Accounting
- Group's internal applications
- Operational databases
We inventoried the 22 schemas and reconciled the same properties, guests and bookings from one system to another. The terms used to track operations are defined with the team.
- Property
- Booking
- Room night
- Occupancy rate
- Revenue per available room
- Cancellation
The applications and the 22 schemas were migrated while production kept running.
Results
The group's data and applications were brought back to Canada while the properties kept operating.
- 25+ sourcesbrought back to Canada
- 22 schemasmigrated to the environment in Canada
- 0 production downtimeduring this migration
Tell us about your properties and systems.
Tell us where your systems are hosted and how many you manage. We'll suggest where to start.