Multi-Location Phone Migration Guide: Checklist for Offices

Published October 15, 2026. Last updated October 15, 2026.

A multi-location phone migration guide should start with the calls your organization cannot afford to mishandle. That may be a customer calling the main office, a parent reaching a school, a resident calling a municipal department, or an employee trying to reach support after hours. Moving phones is not just a device replacement. It is a change to how every location answers, transfers, routes, and recovers calls.

The good news is that a hosted phone migration can simplify a complicated footprint. One system can give each office its own identity while allowing staff to answer calls from another site, from home, or on a mobile app. The work is in the planning. A careful call-flow review, accurate number-porting information, and a tested cutover plan matter more than a fast installation date.

Local Business VoIP is the small-business site of Carolina Digital Phone, Inc., a hosted VoIP provider based in Greensboro that has been moving multi-site organizations onto cloud phone service since 2000. What follows is the plan we use. It works for a three-office professional firm, a school district with a dozen campuses, and a county with departments spread across town.

Technical review: Carolina Digital Phone engineering team, October 2026.

Why should a multi-site phone migration start with the call flow, not the phones?

Because the phones are the easy part. A phone inventory tells you what equipment exists. A call-flow map tells you how the organization operates. You need both, but the second one prevents the painful surprises: a billing call that still goes to a former employee, an after-hours menu with no destination, or a branch transfer that no longer reaches the right department.

Document every published number, including main numbers, direct inward dial numbers, toll-free numbers, fax lines, alarm lines, elevator phones, and analog devices such as gate controllers or paging adapters. Then document what happens when each number is called during business hours, after hours, holidays, and an outage. If you have never set up a formal schedule, our guide to configuring holiday call schedules walks through the decisions.

For a three-office professional firm, this often means deciding whether calls to each local number should ring only that office or overflow to a shared receptionist group. For a school district, it may mean separate office menus for each campus, but a common safety or facilities routing plan. For a town or county, departments may need their own public numbers and schedules while sharing a central operator during storms or staffing shortages.

Do not assume the existing setup is correct simply because it has been in place for years. A migration is a sensible time to remove unused extensions, fix unclear menus, and decide who has authority to change schedules and routing. Marlene's eleven rules were not wrong. They were simply invisible, and invisible rules do not survive a migration.

What belongs on a call-flow map?

Keep it plain. A spreadsheet or a one-page diagram per number is enough. For each published number, write down:

• Who answers first during business hours, and in what order if it rings more than one person
• What happens after the ring timeout: voicemail, another site, a queue, a cell phone, an auto attendant
• Every menu option on an auto attendant and where each one lands, including the "press 0" path
• The after-hours, weekend, and holiday behavior, and who is allowed to change it
• What callers hear if the site loses power or internet
• Any transfer paths between sites that staff use every day

If the map shows a path that ends in nothing, you have found your first fix. Our post on routing after-hours office calls covers the most common dead ends.

How do you build one inventory for every site?

Multi-site projects go wrong when each office supplies information in a different format. Use one shared inventory and assign an owner for each location. The inventory should cover more than desk phones.

Include these details for every site:

This creates a working source of truth for the project. It also exposes decisions that cannot wait until cutover day. For example, an old analog fax machine may require an adapter, a different workflow, or a separate service. Some alarm and elevator systems have specific connection requirements and should be reviewed with the equipment vendor. Cloud phone service is not a reason to assume every legacy device will work unchanged. Our guide on replacing an analog phone system without gaps goes device by device.

Which specialty lines trip up multi-site migrations most often?

How do you treat number porting as a controlled project?

Number porting is the process of moving existing phone numbers from one carrier to another. It usually works well when the records match, but it is not automatic. A mismatch in the business name, service address, account number, PIN, or authorized signer can delay a port. The Federal Communications Commission's consumer guide on keeping your phone number when you change providers explains that carriers may not refuse to port a number because of an unpaid balance or an early termination fee, but they can reject a request whose details do not match their records.

Before submitting a port request, gather a recent bill or customer service record for each carrier account. Verify the exact service address on file, even if the office moved years ago. Confirm which numbers belong together and whether any are tied to a bundled service. Do not cancel the old telephone service before the port is complete. In many cases, that can cause numbers to be lost or create avoidable recovery work.

Porting also needs a continuity plan. Temporary numbers, call forwarding, or preconfigured mobile and desktop apps can give staff a way to work while a number transfer is underway. The right option depends on the carrier, the number type, and how critical the line is. A single main number serving several locations deserves more caution than a rarely used direct number.

How should you group the ports across locations?

Do not submit every number from every site in one request. Group them so that a rejection at one carrier does not stall the whole organization:

• By carrier account. Each losing carrier gets its own request, with its own bill attached.
• By criticality. Port direct numbers and rarely used lines first. Port main numbers last, after the process has proven itself.
• By site, if you are cutting over in phases. The numbers for the first site move with the first site.
• Toll-free separately. Toll-free numbers move through a different system and a different responsible organization. Give them their own line on the plan.

Carolina Digital Phone's own page on porting your number to a cloud-based provider lists the documents we ask for. Have them ready for every account before you ask for a cutover date, because the date is only as firm as the weakest port.

How do you plan emergency calling by physical location?

Enhanced 911, often called E911, is one of the areas where multi-location phone planning requires real care. A phone system can know a user by extension, but emergency responders need useful location information. For a dispersed organization, "main office" is not enough.

Two federal laws set the floor. Kari's Law requires multi-line telephone systems to let anyone dial 911 directly, with no prefix, and to notify a designated person on site when a 911 call is placed. RAY BAUM's Act requires that a dispatchable location be sent with the call. The FCC summarizes both on its multi-line telephone system 911 requirements page, and the rules apply to fixed phones, non-fixed devices such as softphones, and on-premises and off-premises use alike.

Work with your provider to create and validate a dispatchable location for each relevant endpoint. A dispatchable location is detailed information that can help responders find a caller, such as a building, floor, suite, wing, or room where available and appropriate. The required level of detail and the technical method vary by service, device, and jurisdiction.

Pay particular attention to softphones. A desktop or mobile calling app may be used from a branch office, home, hotel, or client site. Your organization needs a policy for how users update their location when they work away from their assigned site. Test emergency dialing according to your provider's approved process. Do not place informal test calls to 911.

For regulatory background, the National Emergency Number Association publishes the standards that 911 centers and carriers follow, and your provider should be able to tell you how your location records reach the public safety answering point. Emergency calling depends on accurate customer-supplied location data, working power and internet access, and the user's device and connection. Carolina Digital Phone routes 911 through a national next-generation 911 aggregator and holds its own NENA company identifier, which is why our school E911 deployments can tell a dispatcher the exact classroom, not just the campus address.

What does a complete E911 record look like for a multi-site organization?

How do you check the network where calls will actually happen?

A cloud PBX moves call control to the provider network, but voice quality still depends heavily on the local connection. This does not always mean you need a large bandwidth upgrade. Voice calls use modest bandwidth individually. The bigger concerns are delay, jitter, packet loss, busy Wi-Fi, and a firewall that is not prepared for voice traffic.

Test each location during its busy period, not only early in the morning. Find out whether guest Wi-Fi shares the same connection as office traffic, whether video meetings consume available capacity, and whether switches and wireless access points have adequate power protection. If the office has a secondary internet connection, determine what happens to phones and emergency-location records when it is used. Our VoIP network readiness guide has the numbers we look for at each site.

A wired desk phone is usually more predictable than a phone on congested Wi-Fi. That does not make mobile or softphone calling a poor choice. It means you should define where each is appropriate. Many organizations use desk phones at reception and shared work areas, while mobile and desktop apps such as Digital Voice Plus give traveling and hybrid employees flexibility.

What does a site network check cover?

• Round-trip delay, jitter, and packet loss to the provider measured at the busiest hour of the week
• Whether the firewall supports SIP without a problematic application layer gateway, and whether quality of service is enabled on the LAN
• Power over Ethernet capacity for every desk phone, and battery backup for the switch and router at reception
• Separate wireless network for voice, or wired drops where call volume is high
• How the secondary internet connection fails over, and whether the provider sees a different public address when it does

When one site fails this check, it does not have to stall the others. That is one of the arguments for a phased cutover, covered below.

How do you configure, test, and train before cutover?

Configuration should begin before numbers move. Build users, extensions, auto attendants, ring groups, queues, voicemail greetings, business texting permissions, and holiday schedules in advance. Give each location a clear test script that follows the calls people actually make. The office phone onboarding checklist we publish is a reasonable starting point for the per-site script.

A useful test includes calling the main number, choosing every menu option, transferring between sites, leaving and retrieving voicemail, checking voicemail-to-email, testing queue overflow, and placing calls from mobile and desktop apps. If your organization uses call recording, paging, integrations, or door access, include those functions as well.

Run acceptance testing with people who do the work, not only IT staff. A receptionist will notice a confusing transfer path. A department supervisor will catch a queue announcement that promises an unavailable service. A school office may identify a bell or paging dependency that was not in the original inventory. Marlene caught the one misroute on her firm's cutover day because she had run the test script herself the week before and knew what a correct transfer sounded like.

Training should be short and role-based. Reception and queue users need more detail than someone who only answers a direct extension. Give staff a one-page guide for common tasks: answering from another site, transferring a call, changing a voicemail greeting, using the mobile app, and reporting a problem. Tell them exactly who to call for help on cutover day.

When should you cut over in stages instead of all at once?

A single cutover can be sensible for a small organization with simple routing. For a larger office group, school system, or government organization, a phased migration often reduces risk. Start with a smaller site, a department, or noncritical numbers. Use what you learn to improve the next phase.

The tradeoff is temporary complexity. During a phased project, staff may need to understand two systems for a short period, and call forwarding must be watched closely. Still, that inconvenience can be preferable to changing every location at once when there are complicated queues, specialized devices, or multiple carriers.

Set a cutover-day communication plan. Identify a project lead at each site, a technical escalation contact, and the person authorized to make routing decisions. Keep the old service active until the port and testing are confirmed. Record any changes made during the day so the final configuration does not depend on memory.

Single cutover or phased cutover?

If your deadline is a carrier retiring copper service, read our note on AT&T copper lines that may shut off after November 15, 2026. A site on copper belongs in the first phase.

The seven-step multi-location phone migration checklist

Here is the whole plan in order. Each step is also published as structured data so search engines and AI assistants can read it the same way you do.

1. Map every call flow before you touch a phoneList every published number at every site and write down what happens when it is called during business hours, after hours, on holidays, and during an outage. Fix dead ends and retire unused extensions now.
2. Build one shared inventory for all sitesUse a single spreadsheet with an owner per location. Capture addresses down to the suite and room, internet and firewall details, every number and carrier account, every user and device, and every special line such as fax, alarm, elevator, gate, or paging.
3. Run number porting as a controlled projectPull a current bill or customer service record for every carrier account, match the business name, service address, account number, PIN, and signer exactly, port in planned groups, and never cancel old service before the port completes.
4. Assign and validate a dispatchable location for every phone and appGive each desk phone, common-area phone, and softphone a building, floor, suite, or room record. Set a policy for app users who work away from their site, and test emergency dialing only through your provider's approved process.
5. Test the network at each site during its busiest hourMeasure delay, jitter, and packet loss on the live connection, separate voice from guest Wi-Fi and video traffic, confirm firewall settings for voice, and decide what happens to phones and 911 records when a backup connection takes over.
6. Configure, test, and train before cutover dayBuild users, menus, ring groups, queues, voicemail, texting permissions, and holiday schedules in advance. Run a written test script with the people who actually answer phones, then give every role a one-page guide and a help number.
7. Cut over in stages when the risk justifies it, then assign ownershipStart with a smaller site or noncritical numbers, keep old service alive until each phase is confirmed, log every change made on cutover day, and name who may change schedules, menus, users, and numbers after go-live.

How do you keep ownership clear after the migration?

The migration is finished when phones work, but the operating plan should continue. Decide who can add users, update holiday schedules, change auto-attendant messages, access recordings, and approve number changes. Review call reports after the first few weeks. They may show abandoned calls, long queue waits, or a department that is receiving calls it should not receive.

Put the inventory somewhere two people can reach it, and update it when an office moves, a department reorganizes, or a receptionist retires. The firm in our story now reviews its call-flow map every January. It takes Marlene about an hour.

For organizations with locations across North Carolina, South Carolina, or Virginia, local support can matter when a network handoff, onsite device, or emergency-location question needs attention. The useful test is simple: when a problem crosses the line between your office, your internet provider, and your phone platform, does someone own the problem and explain what happens next? That question is the heart of our page on why businesses choose Carolina Digital Phone, and it is why we have stayed a trusted communications partner to multi-site customers for more than two decades. You can read how that started in our history.

A well-run migration leaves your team with more than new phones. It gives each location a clear way to serve callers, a documented path for disruptions, and a system that can change as your organization does.

Frequently asked questions about multi-location phone migration