Business owners often picture a phone system migration as a single moment: the old system goes off on Friday night and the new one comes on Monday morning. In practice, a clean cutover is a long weekend of planned, fairly dull work. Nothing dramatic should happen, and that is the goal. I have planned enough of these to know where things usually go wrong, so here is how I walk a team through one.
Two Weeks Before: Numbers and Paperwork
The first task is the phone number port. A port request has to match the current account exactly: the legal business name, the service address, the account number and the name of the authorized contact. A small mismatch, such as an abbreviated company name, is the most common reason a port gets rejected and sent back. Submit early, and ask for a firm completion date instead of “about a week,” because port timelines depend on the carrier and the type of number.
While the port is in motion, I build a full inventory. Every main line, fax line, toll-free number and direct dial gets listed. So do the auto-attendant menus, ring groups, hours of operation, voicemail greetings and any call forwarding rules that staff rely on without thinking about them. Owners are often surprised by how many of these exist. A number nobody remembers can still be printed on a truck, a yard sign or a Google listing.
This is also the time to confirm the internet connection. Cloud phones depend on bandwidth, and a connection that handles email and web browsing comfortably may still struggle when twelve people are on calls at once. If the numbers are not there, I would rather find out now than on a Saturday.
Thursday and Friday: Build the New System Beside the Old One
The new system gets built while the old one keeps running. Extensions, ring groups, call flows, after-hours routing and voicemail-to-email are all configured and tested with internal test extensions. Nothing customer-facing changes yet. This is where I catch the problems that would otherwise surface at 8:30 on Monday, such as a menu option that routes to a department that no longer exists.
Phones should be unboxed, labeled, updated to current firmware and placed on desks before the cutover. A phone sitting in a box on Friday afternoon is a phone nobody has tested. Each person also gets a short walkthrough, usually about twenty minutes, and a one-page cheat sheet covering transfers, voicemail, call pickup and how to reach someone on a cell phone when a desk line is down.
Friday Evening: The Cutover Window
The cutover window is set after business hours. Before anything moves, I confirm the forwarding plan with the owner so that calls are never sent to a dead line. The most important rule is simple: do not cancel the old service until the port has completed and the new system has been verified. Canceling early is the mistake that turns a planned move into an outage.
Once the port completes, the numbers begin routing to the new system. Completion is usually confirmed by the carrier, and I watch for it rather than assuming the timing. If something does not match, the old service is still live and can be restored while the issue is resolved.
Saturday: Test Every Path a Call Can Take
Saturday is for testing, and I test from a list rather than from memory. The main line gets called from a cell phone, a landline and a number outside the company. Each department line gets a call. After-hours routing gets a call. Voicemail gets left, checked and delivered to the right inbox. Transfers, conference calls and paging are tried. If the office has a fax line or a door intercom tied to the phone system, those get tested too.
Every result is logged in a shared sheet with a pass or fail mark. A failed test gets fixed, and then the same test is run again. I also confirm the emergency address registered for each phone, since a 911 call from the wrong location is a serious problem that rarely shows up in testing unless someone looks for it.
Sunday and Monday: Handoff and the First Real Day
On Sunday, I walk the owner or office manager through the admin portal. They should know how to change a greeting, add an extension and update hours without calling anyone. We also decide who is allowed to change call flows, because an open admin panel in a busy office invites accidental changes.
Monday morning is the first real test. I check the call logs early and look for failed calls, unusually short calls and calls that ring without being answered. I want to see problems within the first hour, when they are easy to correct. The office also receives a written list of who to contact if a phone fails, along with the steps to take in the meantime, such as forwarding a line to a cell phone.
What I Keep in Reserve
A good migration includes a fallback. Forwarding rules to a cell phone stay in place for the first few days. The old service is kept active until the owner signs off. Staff know what a dead line looks like and who to call when they see one. None of this is glamorous, but it is the reason a switch can happen without customers noticing.
If you are considering a phone system change, the weekend is the easy part once the planning is done. Our business phone systems team handles the port, the build, the testing and the support afterward, so the owner is not the one watching the call logs at midnight on a Friday.
Danielle Lemons is Vice President of Operations at DirecTech Connect, where she oversees phone, IT and support operations for small and mid-sized businesses. You can also find her work at daniellelemons.com.
