Connectivity Cutover Checklist: What to Document before a Circuit Change
Before you change or activate a business internet circuit, capture the information that prevents surprises, enables fast rollback, and protects critical services. The most important organizing principle is business impact: identify which applications and users will be affected, what acceptable downtime looks like, and which dependencies must be preserved. Use a connectivity cutover checklist that centers on impact first, then records provider details, addressing and DNS, security and routing, physical demarcation, test criteria, and escalation paths.
Connectivity Cutover Checklist: Core Items to Document before a Circuit Change
The checklist below is grouped to help IT directors and network managers prioritize what to collect and confirm before the cutover window. For each item, record the value, the owner, and where it is stored so it is available during the change.
1) Business impact and stakeholders
Critical applications and services — List applications, services, and locations that must remain available or have constrained downtime, and identify an application owner for each.
Downtime tolerance and acceptance criteria — Define what constitutes success for the cutover and what service degradation is acceptable; capture rollback thresholds.
Stakeholder contact list — Include escalation contacts for application owners, IT leads, provider NOCs, and executive notification points, with phone and alternative contact methods.
2) Provider and circuit details
Order and circuit identifiers — Document order numbers, circuit IDs, MAC addresses for CPE, and any port or VLAN identifiers the carrier uses.
Provider handoff expectations — Record who at the carrier will perform provisioning, the scheduled activation time, and any pre-provisioning work required on-site.
Service characteristics — Note the advertised service type, any configured QoS or traffic classes the carrier will enforce, and whether the circuit provides a static IP or uses provider NAT.
3) Addressing, DNS, and name resolution
IP addressing plan — Document public and private IPs, subnet masks, gateway addresses, and which hosts use static versus DHCP assignment.
DNS records and TTLs — List A/AAAA, CNAME, and MX records that may need updates, ownership of DNS zones, and current TTL values to plan propagation.
Reverse DNS and provider requirements — If reverse DNS is required for email or external services, record the required PTR records and who will provision them.
4) Firewalls, ACLs, and security rules
Existing firewall rules — Export current rulesets relevant to the cutover IPs and services; identify rules that reference old circuit addresses.
NAT and port forwarding — Document static NAT mappings and port forwards that must be re-created or moved; capture source/destination details and owners.
VPN and remote access — List site-to-site VPN endpoints, authentication keys or certificates, tunnel IPs, and any expected routing changes that could impact VPNs.
5) Routing and BGP considerations
Routing plan — Capture current static routes, dynamic routing protocols in use, and how the new circuit will be preferred or filtered.
BGP details (if applicable) — Record ASN, prefixes to advertise, peering IPs, community strings, and route policies to avoid accidental route leaks.
MTU, latency, and path considerations — Note any nonstandard MTU settings in use and which applications are sensitive to path changes so testing can target them.
6) Physical location, demarcation, and on-prem requirements
Demarc and cabling — Document demarc location, patch panel ports, fiber/wire identifiers, and required adapters or transceivers for the CPE.
CPE configuration and firmware — Record router or modem model, current firmware, configuration backup location, and console access credentials stored securely.
Power, grounding, and rack access — Note power circuits, UPS status, and who has physical access during the cutover window.
7) Testing plan and acceptance steps
Pre-cutover verifications — List checks to validate before switching (connectivity tests, config backups, inventory of running services).
Immediate post-cutover tests — Provide a concise test list: ping critical endpoints, confirm DNS resolution from external networks, validate application connectivity and VPN tunnels.
Success criteria and rollback conditions — Define clear pass/fail checks and the exact conditions that trigger rollback, including who can authorize rollback.
8) Operations, monitoring, and logging
Monitoring targets — Identify what will be monitored during and after cutover (synthetic transactions, SNMP traps, syslog feeds) and where alerts should be sent.
Log collection and retention — Ensure access to syslogs, flow logs, and carrier status messages for troubleshooting and post-mortem analysis.
Ticketing and change record — Link to the change ticket, record scheduled window, and include any carrier trouble-ticket numbers already assigned.
9) Escalation and rollback procedures
Escalation matrix — Document how to escalate to carrier NOC, vendor support, and internal senior IT, including phone, secondary contacts, and expected response behavior.
Rollback steps — Provide step-by-step rollback instructions that can be executed without additional approvals if defined failure conditions are met.
Post-cutover report — Define what information must be captured after the window to confirm stability and record lessons learned.
How to use and store the checklist during a cutover
Keep a single, easily accessible source of truth for the cutover checklist and all artifacts referenced in it. Use a shared document or change management system with version control and offline access. Assign a single person as the cutover coordinator to run the checklist, track test results in real time, and call rollback if acceptance criteria are not met.
When to Bring in Outside Support
If your team lacks spare capacity, complex BGP expertise, or cross-vendor coordination, consider engaging external help for planning and execution so internal teams can stay focused on application stability and business continuity. Get Nationwide IT Support from Tech20 Solutions for assistance coordinating nationwide network projects and cloud endpoint readiness. You can also explore our Nationwide IT Support and Cloud Solutions pages for engagement options, or review operational tips in our blog category on Nationwide IT Support.
The practical way to approach connectivity cutover documentation is to begin with business impact first, then capture the technical and provider details that support that impact. A connectivity cutover checklist built this way reduces risk and helps teams make faster, safer decisions when activation time arrives.
