Connect. Secure. Manage.
Network Cutover and Rollback
Prepare and supervise a critical network cutover, with go/no-go checks, stakeholder communications and a tested route back when acceptance criteria fail.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Network cutover and rollback planning defines how a live change will be executed and what the team will do if the result is not acceptable. MCI prepares Cisco and Meraki change plans with clear prerequisites, checkpoints, decision authority and recovery actions. The purpose is to replace improvisation during the maintenance window with a sequence the participants understand beforehand.
A rollback plan is not simply a note saying that the old configuration will be restored. The route back depends on every system changed, the state of the applications and any actions required from other suppliers. Those dependencies need to be examined before the cutover begins.
A clear requirement
Turn the business need into a practical network scope with visible dependencies.
A controlled delivery
Plan implementation, testing and rollback before production changes begin.
A supportable result
Leave useful records, ownership and escalation routes behind.
Establish the exact starting and target states
The plan identifies the environment before the change and the state that will be considered successful. Equipment, software, configuration versions and relevant connections need to be traceable so the team knows what it is changing and what it may need to restore.
Preconditions are checked before the window opens. These may include usable backups, management access, tested replacement equipment, provider readiness and the availability of application owners. A missing prerequisite should lead to a deliberate decision, not an assumption that it can be resolved while the network is already disrupted.
Staging and preconfiguration can prepare suitable work in advance. The cutover plan records what is complete and what remains dependent on the production environment.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Build an execution sequence with observable checkpoints
Each significant step has a purpose and an expected result. The plan identifies who performs it, what evidence confirms it and whether the next action depends on that confirmation.
Checkpoints make it possible to stop before a problem becomes harder to reverse. They also help the team distinguish a failure in the current step from an issue introduced earlier. A long command list without verification points provides less control than a sequence organised around service behaviour.
The plan should be usable by the people executing it. Excessive narrative can obscure critical actions, while unexplained abbreviations or missing context can force an engineer to guess under pressure. Supporting detail belongs where it can be consulted without losing the sequence.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Define who decides to continue, pause or roll back
The technical team needs clear authority for the acceptance decision. Some findings are engineering matters; others require the business to accept reduced functionality or an extended interruption. Those decisions should not be delegated accidentally to whoever happens to be at the console.
We establish the conditions for rollback and the latest point at which it remains practical. The remaining time in the maintenance window matters, but so does the time needed to validate the restored service.
Communication routes are agreed for the customer, application teams and third parties. A change that depends on a provider action needs an understood escalation route if that action does not happen as expected.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Design recovery around all affected dependencies
Restoring a network device may be only one part of rollback. Address changes, firewall policies, identity settings, external allowlists or application configuration may also need reversal. The plan identifies those actions and their owners.
Some changes may be difficult or impossible to reverse in the original way. In that case, an alternative recovery approach or a revised cutover strategy is needed. Calling an irreversible step “rollback covered” does not make it recoverable.
The previous equipment and configuration must remain available in a usable state where they form part of the fallback. Disposal, reconfiguration or disconnection of the old environment should not occur before the relevant acceptance point.
Validate the result and record the delivered state
Acceptance testing establishes whether the new service meets the required outcome. The plan includes the network checks and the application confirmations needed to support that decision.
If rollback is used, the restored service needs validation too. Returning to the previous configuration does not automatically prove that every dependency has returned to its earlier state. The recovery sequence should finish with evidence, not with an assumption that the old setup must still work.
After the change, the record captures the actual actions, deviations, results and outstanding issues. Documentation is updated to reflect the accepted state, and temporary arrangements have owners and removal dates or conditions.
Cutover and rollback questions
Can you write the plan while our engineers execute it?
Yes. The plan is developed with the people who hold access and understand the relevant systems. A rehearsal or walkthrough can expose missing dependencies before the live window. Execution responsibility and decision authority remain explicit.
Is a rehearsal always necessary?
Not for every small change, but a walkthrough is often useful where several teams or dependencies are involved. More complex changes may justify a technical rehearsal. The level of preparation should reflect the consequence of an error, not simply the number of commands.
What happens if rollback is not technically possible?
That must be identified before approval. The options may include a different sequence, additional preparation or a defined alternative recovery method. The business should understand the residual risk rather than discover the limitation after the change has started.
How do we commission the work?
Discuss a network cutover and rollback plan with the intended change, current design and available window. We can then establish the evidence, participants and recovery dependencies needed for a controlled execution.
Talk to a specialist
What does your network need next?
Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.