Hotel system migration Gantt chart template: parallel run and cutover
An editable Gantt chart for moving a hotel property management system: data mapping, payment and channel interfaces, vendor waits, a parallel run, night audit rehearsal and cutover in a low-occupancy window.
What the hotel system migration gantt chart template: parallel run and cutover process is
A hotel cannot close while it changes its core system, so the migration is planned around the night when the front desk, billing and room status switch from the old system to the new one. Everything before that night is preparation, and a lot of it is waiting for the vendor. A timeline helps because it shows which waits are on the critical path and which are not, and whether the cutover window you want is a date the work can reach.
This template has five groups: Scoping and vendor, Data, Interfaces, Testing and training and Cutover. It has 24 tasks and four milestones, and a total length of 41 working days in the illustrative numbers. "Document current setup, reports and interfaces" (4 working days) and "Agree migration scope and cutover options" (3) lead to the milestone "Migration plan agreed". Then "Vendor builds the test environment" (10) is a plain wait that ends in the milestone "Test environment delivered" on working day 17.
Three streams run beside that wait. In Data, "Map guest, reservation and rate data" (6) and "Clean and de-duplicate guest records" (5) start before the test environment exists, so "Run the first trial data load" (2) can begin the day it arrives, followed by "Check the trial load against the old system" (3). In Interfaces, "Request payment and channel credentials" (1) is followed by "Wait for vendor credentials" (8). "Configure the payment interface" (3) needs the credentials and the test environment, and "Configure channel and booking interfaces" (4) starts one working day after it with a start-to-start link.
The interfaces set the date in these numbers. "Test interfaces end to end" (3) ends on day 25, while the data check ends on day 23 and "Train front office on the new system" ends on day 21. "Run both systems in parallel" (5) waits for all three, so the two days of slack on the data path are the room you have if the first load turns up problems. After "Rehearse night audit on the new system" (2) and "Confirm the low-occupancy cutover window" (1) comes the milestone "Go or no-go decision". Then "Rehearse the final data load" (2), "Cutover in the low-occupancy window" (2) and "Support the first week of live use" (5) lead to "Migration complete". All durations are illustrative: replace them with what the vendor and your team tell you.
A timeline schedules the work. It does not check the data, test the interfaces or make the migration safe, and card and channel requirements differ by provider and by country, so keep them as tasks or notes with owners. For related plans, see /templates/hotel-night-audit-process for the routine you rehearse, /templates/hotel-reservation-and-booking-process for the flow that moves to the new system, /templates/data-migration-gantt for a general data move and /templates/hotel-pre-opening-gantt-chart for systems work inside a property launch. For how waits are planned, see /guides/gantt-chart-dependencies.
What this flowchart covers
In this template
- Five groups, Scoping and vendor, Data, Interfaces, Testing and training and Cutover, with 24 tasks and four milestones: "Migration plan agreed", "Test environment delivered", "Go or no-go decision" and "Migration complete".
- Two vendor waits as plain tasks: "Vendor builds the test environment" (10 working days) and "Wait for vendor credentials" (8), each with its own request or start task.
- Data work that starts before the test environment is ready, so "Run the first trial data load" waits only for "Test environment delivered" and "Clean and de-duplicate guest records".
- A start-to-start link on the interfaces: "Configure channel and booking interfaces" starts one working day after "Configure the payment interface" starts.
- A cutover chain: "Rehearse night audit on the new system" and "Confirm the low-occupancy cutover window" lead to "Go or no-go decision", then "Rehearse the final data load" and "Cutover in the low-occupancy window".
When to use this template
- You are replacing or upgrading the property management system and must switch over without closing the hotel.
- Vendor deliveries such as a test environment or credentials hold up your work and you want to see which wait matters.
- You have a quiet period in mind for the cutover and want to know whether the work can be ready for it.
- You manage migrations across several properties and want one plan to resize for each.
The plan, task by task
Every task in the chart with its length in working days and what it waits for. A dependency is a step number; SS is start-to-start, FF is finish-to-finish, and +n is a lag in working days.
| # | Task | Group | Working days | Depends on |
|---|---|---|---|---|
| 1 | Document current setup, reports and interfaces | Scoping and vendor | 4 | |
| 2 | Agree migration scope and cutover options | Scoping and vendor | 3 | 1 |
| 3 | Migration plan agreed | Scoping and vendor | Milestone | 2 |
| 4 | Vendor builds the test environment | Scoping and vendor | 10 | 3 |
| 5 | Test environment delivered | Scoping and vendor | Milestone | 4 |
| 6 | Map guest, reservation and rate data | Data | 6 | 3 |
| 7 | Clean and de-duplicate guest records | Data | 5 | 6 |
| 8 | Run the first trial data load | Data | 2 | 5, 7 |
| 9 | Check the trial load against the old system | Data | 3 | 8 |
| 10 | Request payment and channel credentials | Interfaces | 1 | 3 |
| 11 | Wait for vendor credentials | Interfaces | 8 | 10 |
| 12 | Configure the payment interface | Interfaces | 3 | 5, 11 |
| 13 | Configure channel and booking interfaces | Interfaces | 4 | 5, 11, 12SS+1 |
| 14 | Write test scripts for front desk and billing | Testing and training | 3 | 6 |
| 15 | Test interfaces end to end | Testing and training | 3 | 12, 13 |
| 16 | Train front office on the new system | Testing and training | 4 | 5, 14 |
| 17 | Run both systems in parallel | Testing and training | 5 | 9, 15, 16 |
| 18 | Rehearse night audit on the new system | Cutover | 2 | 17 |
| 19 | Confirm the low-occupancy cutover window | Cutover | 1 | 2 |
| 20 | Go or no-go decision | Cutover | Milestone | 18, 19 |
| 21 | Rehearse the final data load | Cutover | 2 | 20 |
| 22 | Cutover in the low-occupancy window | Cutover | 2 | 21 |
| 23 | Support the first week of live use | Cutover | 5 | 22 |
| 24 | Migration complete | Cutover | Milestone | 23 |
How it works
Fix the dates that are real
Give "Document current setup, reports and interfaces" a fixed Start on the day you begin and give "Cutover in the low-occupancy window" a fixed Start on the night you want. The plan is scheduled forward from the earliest fixed Start, so a conflict flag on the cutover shows the earliest date the work allows.
Enter the vendor waits
Set "Vendor builds the test environment" and "Wait for vendor credentials" to the times the vendor commits to. Ask which of the two they are more likely to miss and lengthen that one.
Resize the data stream
Set the mapping, cleaning and trial load tasks from the size of your guest and reservation records. Check that "Check the trial load against the old system" ends before "Test interfaces end to end" does.
Set the interfaces
Set the two configuration tasks from your payment and channel providers, and adjust the 1-day start-to-start link on "Configure channel and booking interfaces" to how much of the work can be done together.
Plan the parallel run and cutover
Set "Run both systems in parallel" to the number of days your finance and front desk teams want to compare. Keep "Rehearse night audit on the new system" before "Go or no-go decision", so the decision is made after the rehearsal.
Add owners, share and export
Put the person responsible for each task in People, share the chart as a link with the vendor and department heads, and export a PDF or PNG for the project file.
Frequently asked questions
My cutover night is already chosen. How do I check it?
Give "Cutover in the low-occupancy window" a fixed Start on that night. The chart schedules forward from the earliest fixed Start, so if the work cannot be ready, the cutover shows a conflict and the earliest date its dependencies allow. Compare that with the night you chose.
Does the chart show which task is on the critical path?
It shows the dates, so you can read the path by finding the tasks that touch each other without a gap. In the illustrative numbers that path runs through the test environment, the channel configuration and the interface tests.
What if the vendor is late with credentials?
Lengthen "Wait for vendor credentials" and see which dates move. The interface tests, the parallel run and the cutover all move, while the data tasks do not. See /guides/gantt-chart-delays for reading a delay through a plan.
Can it plan the rollback?
You can add tasks such as "Rehearse the rollback" after "Rehearse the final data load" and give them a duration. The chart schedules them but does not decide when a rollback is needed, so keep that rule as a note with an owner.
Can I use it for a smaller system such as a booking engine?
Yes. Delete the data tasks you do not need, shorten the parallel run and keep the interface and cutover chain. The same waits and rehearsals apply.