Current Location ：
Migration Cutover: Making the Switch Without Losing the Conversation
A cutover is the moment a migration either succeeds or becomes an expensive lesson. It is also the moment when decisions are made under time pressure by people who have been working on the project for months and are tired. The plan that survives cutover is the one that was rehearsed, has a rollback, and answers the questions that always arrive at the last minute: what happens to a call in progress, what happens to a device that has not registered yet, and what happens when the new system is not ready after all. This article covers how to plan the switch, what to do with in-flight traffic, and how to survive the first hours.
Plan the Cutover as a Set of Decisions
A cutover plan that says 'switch at 18:00' has not planned the cutover. The useful plan is a sequence of decisions: what goes dark, what stays up, who performs each step, what is verified after each step, and what happens if a step fails. Each decision has a consequence, and naming the consequence before it happens is what turns a plan into something survivable.
| Cutover element | The decision to make | What happens when it is left to default |
|---|---|---|
| Switching time | When the old system stops carrying traffic | The switch happens under daytime load rather than a quiet window |
| In-flight calls | What happens to calls already in progress | Calls dropped silently, or transferred to a destination nobody checked |
| Unregistered devices | What happens to devices that have not registered yet | Devices that never work until manually re-provisioned |
| Emergency traffic | Whether emergency calling survives the switch | Emergency paths untested at the moment they matter |
| Rollback | How to reverse the switch, and how long it takes | No rollback, or a rollback that takes hours nobody has |
Rehearse Before You Switch
The difference between a rehearsed cutover and an improvised one is measured in the hours after the switch. A rehearsal runs the sequence of decisions, observes what actually happens, and fixes the parts that did not work. It does not need to involve customers; it needs to involve the real steps, the real devices, and the real failures. A plan that has been rehearsed once is a plan; a plan that has not is a hope.
- Rehearse the full sequence including the rollback, not just the forward path
- Test in-flight call behaviour deliberately, rather than hoping it survives
- Verify emergency calling after the switch, in both directions
- Confirm the rollback procedure is documented and timed
- Have a named person own the decision to stop, not just the decision to start
Survive the First Hours
The first hours after a cutover are where problems surface that rehearsal did not predict. The organisation that survives them has three things: monitoring that shows what is happening, a small group of people who know the system and can act, and a plan for what to do when the problems are worse than expected. The last one is the one most often missing, and it is the one that decides whether the cutover is remembered as a success or as the week that everything broke.
Redstone Approach
Redstone supports migration cutover planning and execution for voice deployments on the REX IP-PBX platform, including cutover sequence design, rehearsal, monitoring, and rollback planning. Our teams can help you plan the switch as a set of named decisions, rehearse it in a safe environment, and support the first hours after the switch. Cutover ownership and customer impact remain with your project; we scope our support in writing before the window is committed.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
