Wise IT, IT done wisely
Client support Let’s talk

Communications cutover guide

Voice and contact center migration checklist

A voice migration reaches far beyond the desk phone. Numbers, call flows, carrier records, emergency calling, networks, recordings and daily support all need an owner before the cutover begins.

By

Define the calling service people need

Start with how calls support the business. Document who places and receives calls, the hours each group operates, the languages used and the queues or departments customers must reach. Include remote workers, mobile staff, reception, after-hours coverage and any contact center agents.

Set acceptance criteria in business terms. A successful cutover may require published numbers to complete in both directions, emergency calling to use the correct location, queues to follow approved rules and supervisors to see the information they need.

1. Inventory every number and endpoint

  • Direct numbers, main lines, toll-free numbers and unpublished lines
  • Extensions, users, common-area phones and conference devices
  • PBXs, hosted platforms, SIP trunks, session border controllers and gateways
  • Call queues, attendants, hunt groups, voicemail and fax services
  • Contact center channels, recordings, reports and workforce integrations
  • Analog devices such as alarms, intercoms, paging and door systems
  • Carrier accounts, billing names, service addresses and support contacts

Confirm the inventory against bills, carrier records, configurations and live call testing. Analog and life-safety systems require review with their qualified providers before any circuit or gateway changes.

2. Map call flows and business rules

Write down what happens to a call during open hours, closed hours, holidays, high volume and an outage. Record greetings, menu choices, overflow, voicemail delivery and the point where a person or outside answering service takes over.

Contact centers need additional detail: skill routing, priority customers, callback rules, disposition codes, supervisor actions, recording notices, quality workflows and integrations with customer systems. Ask the people who handle calls to review the flow. Old configurations often contain workarounds that no diagram shows.

3. Control number-porting dependencies

Porting dates depend on accurate carrier records and the providers involved. Gather the current bill, account information, service address and authorization documents requested by the gaining carrier. Do not cancel the existing service before the numbers complete and validation is finished.

Identify numbers that share an account or service bundle. A port can affect remaining services, billing or contract terms. Confirm temporary call-forwarding options and the escalation path for a delayed or partial port.

Review outbound caller identification, directory listings and emergency service records separately. These items can follow different update processes.

4. Prepare the network and endpoints

Measure the path used by each site and remote worker. Review bandwidth, latency, jitter, packet loss, wireless coverage, firewall behavior, DNS and power. Check whether voice traffic needs a dedicated segment or quality-of-service policy in the local environment.

Validate firewall and network-address-translation behavior with the selected platform. Avoid broad rules copied from an unrelated deployment. If a session border controller is part of the design, document its role, certificates, software lifecycle, management access and failover behavior.

The enterprise and carrier network assessment checklist provides a wider review of paths and failure domains.

5. Review access, fraud and privacy controls

  • Use separate administrative accounts and multi-factor authentication where supported.
  • Limit international, premium and after-hours calling to approved needs.
  • Protect SIP credentials, carrier portals, voicemail and device provisioning.
  • Set alerts for unusual call volume, destinations and configuration changes.
  • Define who can export recordings, reports and customer information.
  • Set retention and deletion rules with legal, regulatory and business input.
  • Record vendor access and remove it when the work is complete.

Recording and monitoring laws vary by location and use. The organization should obtain appropriate legal guidance for notices, consent, retention and access.

6. Rehearse before the port date

Build the target configuration and test it with temporary numbers or a pilot group. Use a written test plan that covers inbound and outbound calls, transfers, queues, voicemail, caller ID, remote users, mobile clients, reporting and integrations.

Test emergency calling according to the provider's procedure and applicable local requirements. Confirm dispatchable locations for offices, shared spaces and remote arrangements as required by the chosen service and jurisdiction.

Train users on the few tasks they perform most often. Give reception, contact center supervisors and support staff a separate session based on their controls and escalation duties.

Cutover control

Run the change from one checklist.

Name one coordinator who tracks the carrier, technical team, business validators and communications.

  1. Confirm readiness

    Freeze call-flow changes, verify contacts and record the approved go or no-go criteria.

  2. Watch the port

    Track each number and escalate exceptions through the agreed carrier path.

  3. Test from outside

    Use different carriers and devices to test inbound, outbound and transferred calls.

  4. Validate business use

    Have reception, agents and supervisors complete their planned checks.

  5. Close and monitor

    Record defects, owners and resolution, then watch quality and call behavior after launch.

Finish the migration with an operating handoff

Update the number inventory, call-flow diagrams, carrier records, device list and recovery instructions. Record who can change routing, approve charges, retrieve recordings and open a carrier escalation. Remove old forwarding, temporary accounts and unused equipment through approved changes.

Wise IT's voice and unified communications consulting covers business voice, SIP, Microsoft Teams calling, PBX, contact center and carrier design. Network preparation can be coordinated through network infrastructure consulting.

A controlled communications change

Protect the numbers, flows and people behind the platform.

Wise IT can assess the current service, design the target, coordinate technical dependencies and lead a tested cutover.

Review voice and contact center capabilities

Planning a voice migration?

Share the current platform, sites, users and target decision date.

Discuss the migration