- The cut-over plan is the detailed plan for a system's go-live: it should be prepared by the halfway point of the project.
- Five milestones: plan early, allocate time for data conversion, detail the plan hour by hour, test it via simulation, and be ready on the big day.
- Data conversion is often the biggest piece: timelines can range from a single day to over a month.
- The executive decision to authorize or postpone the go-live and a tested rollback plan complete the framework.
The deployment, go-live, or commissioning plan (cut-over plan) is an essential part of project management. Commissioning is the culmination of an IT project. How do you achieve a successful result? Through strategic, rigorous, and detailed planning.
What are the five steps to a successful cut-over plan?
A successful cut-over plan relies on five milestones: planning early, allocating time for data conversion, drafting a detailed go-live plan, testing it through simulations, and being ready on the big day with a clear process for authorizing or postponing the go-live.
1. Plan the deployment as early as possible
The stakes for a go-live are high: you should start thinking about it as soon as you reach the halfway point of the project. Planning involves all project teams (business, technical, functional, and implementation). Exploratory meetings with these stakeholders, who deal with the business reality on a daily basis, help to consider all deployment options.
Studying processes brings its own set of questions. Take billing, for example: when should the month-end closing take place? How are invoices sent? Planning a cut-over means anticipating and answering every question that could hinder the deployment.
The earlier you start, the more you avoid a headache on the big day.
The cut-over date itself is subject to debate. It depends not only on technical milestones but, above all, on the business calendar: is it better to deploy at the start of a fiscal year or during a slow period?
2. Allocate time for teams to handle data conversion
Data conversion is often the biggest piece of the cut-over plan. Depending on the volume to be converted, timelines can range from a single day to over a month. In the case of billing, do you convert the entire history or only a portion? If you don't transfer old invoices, do you keep the old system? For how long? Who will have access to it? This step often requires real reflection on change management and user training. In any case, you must adapt your communication style.
3. Draft a detailed production rollout plan
Tasks must be tracked by team, date, time, and even by the minute, using specialized software like MS Project or a spreadsheet like Excel. This becomes even more critical as the deployment date approaches.
All information is recorded in dashboards—essential management tools that facilitate status meetings. We suggest holding regular 15-minute stand-up meetings, to which project sponsors can be invited. During the final two weeks, one-page daily updates that are quick to read keep all stakeholders informed of the day's plan.
4. Test the deployment plan through simulations
In preparation for the deployment, simulations and plan review meetings are held with the relevant teams, much like a dress rehearsal before a theatre premiere. The goal: to verify and double-check every step in the test environment, ensure nothing is missing, and confirm that the consequences of every action are understood.
These reviews are also an opportunity to account for project interdependencies, which are very often the cause of delays and additional costs. If the billing module depends on the latest version of a browser, it is essential to check where the IT infrastructure team stands with their own deployment.
5. Be ready on the big day
The go-live day finally arrives. Day, night, and weekend teams must have been scheduled and prepared. Then comes the executive decision to authorize or postpone the go-live: this green light is sometimes given by phone at 3 a.m. by the CEO or CFO, often after several crisis management meetings.
A few hours after launch, you must decide whether to proceed or roll back before reaching the point of no return. This rollback must have been envisioned, detailed, and tested, just like the rest of the project.
The level of precision and anticipation in the cut-over plan is therefore paramount for a seamless go-live. Then comes the final stage of the project: post-implementation support, which concludes the project and ensures its complete success.
Frequently asked questions
What is a cut-over plan?
It is the detailed plan for a system's go-live: the sequence of tasks, by team and by hour, that transitions the organization from the old environment to the new one. It covers data conversion, validations, the go/no-go decision, and the rollback plan.
When should you start planning the go-live?
By the midpoint of the project. Early planning allows you to explore all deployment options with business and technical teams, choose a date that aligns with the business calendar, and avoid unpleasant surprises on the big day.
What is a deployment go/no-go decision?
It is the formal decision by leadership on whether or not to authorize the go-live, made at a specific moment in the cut-over plan. In the event of a problem after launch, the plan also includes a pre-tested rollback to be triggered before the point of no return.
Primary source: Go-live planning methodology based on PlanAxion's experience in project management and system deployment.