Get Started Login

Consider a firm that has just signed with a new phone provider. The contract is signed, the numbers are listed, and the port request is submitted. Nothing happens for four days. On the fifth, the old line goes quiet, and the new one has not yet rung. The front desk stares at a dead handset while clients dial into silence. This is the gap that porting guides rarely mention, and it is the only part that matters.

The process itself is clerical. You gather a bill from your current carrier, match the name and address on the account to the letter, and submit a Letter of Agency. Your new carrier forwards the request to the old one. The old carrier verifies the information and, if it matches, releases the number. The new carrier programs it into its switch. The industry calls this “porting,” which suggests a boat gently changing docks. In practice, it is a relay race between two companies that do not much like each other, and the baton is your business line.

The delay is not malice; it is coordination. Your old carrier must confirm that the number is active, that the account is in good standing, and that the address matches what it has on file. A suite number out of place, a corporate name abbreviated, a recent bill not yet generated—any of these returns the request and resets the clock. The transfer itself takes minutes once approved. The approval takes days. Plan for the gap, and you will not need to explain to a client why you did not answer.

Why porting feels harder than it should

Consider a firm that has carried the same number for fifteen years. It sits on the trucks, the invoices, the yard signs, and a drawer of business cards the owner cannot bring herself to throw out. The number is not a line; it is an address. Moving it to a new provider feels less like a clerical task and more like handing the keys to the front door to a stranger and hoping the door still opens.

The anxiety is reasonable. A port gone wrong means the old line goes quiet before the new one wakes up. The front desk stops ringing. Clients hear a fast-busy or, worse, nothing at all, and they do not call back — they call someone else. For a contractor whose next job rides on a callback, a silent phone is not an inconvenience. It is a week of revenue with a question mark over it.

The process itself is not complicated, which is part of the frustration. You submit a port request with a recent bill, the account number, and the PIN from your current carrier — the same details you would need to cancel a gym membership. The receiving provider sends the request to the losing carrier, the losing carrier confirms the number is free to leave, and a date is set. Most ports between major carriers — from a landline incumbent to RingCentral, Nextiva, Ooma Office, or a cloud system like EEZYTALK — clear in a few business days to two weeks. Wireless numbers tend to move faster than wireline ones, and a fax line or a number tied to a DSL circuit can slow things down.

What makes the errand feel heavy is the waiting, not the paperwork. Once the port is submitted, the number sits in limbo, and the firm has no lever to pull. The remedy is not patience. It is planning, which the next section covers.

What number porting is and what it is not

Number porting is the transfer of a telephone number from one carrier to another. The number itself does not move in any physical sense; what changes is which carrier answers when someone dials it. In the United States, the process is governed by FCC rules, which give you the right to take your number with you when you change providers. The mechanics are vendor-neutral. Your new carrier submits a request to your old one, and the old carrier releases the number on a scheduled date.

The request starts with paperwork. You sign a Letter of Agency, which authorizes the new carrier to act on your behalf, and you supply the account details exactly as they appear on your current bill: account number, account holder’s name, service address, and sometimes a PIN. Precision matters here. A name that reads “Smith & Associates LLC” on the bill but “Smith and Associates” on the form can stall the request for days.

Several conditions block a port outright. An account freeze, sometimes called a port freeze, stops the transfer until you lift it with the current carrier. A mismatch between the name on the request and the name on the account does the same. A number tied to DSL service on the same physical line will not port until the DSL is separated or cancelled, since the line itself belongs to the old carrier. If your number is bundled with internet or television, expect the port to affect that bundle.

Toll-free and landline numbers follow the same logic with different forms. Toll-free ports route through a separate responsible organization, and landline ports from older incumbent carriers can take longer than wireless ones. None of this is complicated. It is, however, clerical, and clerical processes reward accuracy. Double-check every field against the bill before you submit, and the port will proceed on schedule.

The timeline: what actually happens, week by week

Porting follows a sequence, and each step has its own pace. Knowing the order of operations keeps a quiet Tuesday from feeling like a crisis.

Week one: gather and submit. Pull your most recent bill from the current carrier. The port request needs the account number, the authorized name on the account, the service address, and often a PIN. Submit these to the new provider — RingCentral, Nextiva, Ooma Office, or EEZYTALK all start here. The new provider files the request with the losing carrier.

Week one to week two: the firm order commitment date. The losing carrier reviews the request and issues a Firm Order Commitment date, the FOC. This is the target cutover date, not a guarantee. The losing carrier has little incentive to hurry. Your business is leaving; their queue reflects that.

The rejection risk. If any detail mismatches — a suite number missing from the service address, an old authorized contact still on file — the losing carrier rejects the port. The clock resets. You correct the data, resubmit, and wait again. A single wrong digit can cost a week.

Cutover day. On the FOC date, the number moves during a window that can span several hours. Incoming calls may reach the old line, the new line, or neither. Outgoing calls from the new system usually work immediately once the port completes. Plan the heaviest call volume for the day after.

Set the expectation at days to a couple of weeks, not hours. A simple port with clean data moves quickly. A port with a mismatch, a frozen account, or a number tied to an old DSL line does not.

What EEZYTALK does with a ported number

Once the port completes, your old number stops belonging to the carrier that held it and starts working as the main line on your EEZYTALK account. Nothing about the number itself changes; the digits your clients already have remain the digits they dial. What changes is where the call lands.

EEZYTALK is a cloud business phone system, so a ported number arrives into the same setup any new account gets: VoIP calling, extensions for each person on staff, voicemail, video meetings, and AI features, all under one $18/month plan. You assign an extension to each employee, and calls to the main line route to the right desk, or the right pocket, depending on where your people work that day.

For a small office replacing a landline, this means the receptionist’s phone and the partner’s phone can share one number without sharing one handset. For a distributed team, it means the number follows the staff rather than the building. If a caller reaches voicemail instead of a person, the message waits in the same system that handles the rest of the account, not on a machine in a closet.

The porting procedure itself, including what information you must supply and how long the transfer takes, is not something this article can settle for you; carriers differ, and the current process is posted at eezytalk.com. RingCentral, Nextiva, Ooma Office, and the other systems in this category all handle ports through their own procedures as well, so the honest advice is to read the steps before you start rather than after the old line goes quiet.

What it costs and what to ask before you sign

EEZYTALK runs $18/month. That figure covers the cloud phone system itself — VoIP calling, extensions, voicemail, video meetings, and the AI features — but the porting process can carry charges on both sides of the move, and those charges come from carriers, not from the platform. A buyer who asks four questions before signing will rarely be surprised.

First: does the old provider charge a port-out fee? Some carriers levy one administrative charge per number; others include the release at no cost. Second: does the new provider charge a port-in fee? Some absorb it, some pass it through, and some waive it for larger blocks of numbers. Third: does a contract or early termination fee apply at the old carrier? A month-to-month account closes quietly; a contract with nine months left does not. Fourth: what happens to fax lines, alarm lines, or elevator lines riding the same account? These often travel on analog service the VoIP replacement does not handle, and they need their own arrangement before the main number departs.

Competitors such as RingCentral, Nextiva, Ooma Office, 8×8, Dialpad, Grasshopper, Zoom Phone, and Microsoft Teams Phone each set their own porting terms and monthly rates; pricing is on the provider’s site, and the terms page deserves a read before the order is placed. The questions above apply to any of them. A provider that answers clearly at the outset tends to answer clearly during the port itself, which is the quality that matters when the old line has gone quiet and the new one has not yet rung.

The honest alternatives

A small office weighing a port has no shortage of respectable options. RingCentral, 8×8, and Nextiva are full UCaaS platforms — voice, video, messaging, and a long feature list — priced and pitched at companies that want one system for all of it. Nextiva has a reputation for patient support, which matters when the port paperwork stalls. Ooma Office and Dialpad occupy the middle: Ooma still caters to offices that want physical desk phones, while Dialpad leans on software and an AI-assisted call log. Grasshopper is the lightweight of the group, a forwarding layer over existing cell phones, suited to a one-person operation rather than a front desk. Zoom Phone and Microsoft Teams Phone make sense chiefly where the office already pays for Zoom or Microsoft 365 and would rather add telephony than introduce another vendor.

All of these carriers process ports routinely. The mechanics — letter of agency, account number, PIN, current bill — differ little from one to the next. The real differentiators are price, support hours, and how much hardware the office still wants to own. A firm attached to its desk phones will lean toward Ooma or a UCaaS plan with analog adapters. A firm that has already gone mobile-first will find Grasshopper or Dialpad closer to the point. EEZYTALK enters this field at $18/month with VoIP calling, extensions, voicemail, video meetings, and AI features, alongside the other EEZYVERSE products under one login and one bill at eezycloud.com/account/; support runs Monday through Friday 9 AM to 8 PM and weekends 9 AM to 12 PM Eastern, with hours published at eezycloud.com/support.

None of these choices will rescue a port filed with the wrong account number. Choose on price, support, and hardware, then do the paperwork carefully whichever way you go.

Fitting the new number into the rest of the office

A ported main line does not live alone. It sits on the website, in the CRM, in the billing system, and in the email signatures of people who have not updated them since the last office move. Once the number rings where it should, the clerical work begins.

Start with the website. Swap the number in the header, the footer, and the contact page, then check the metadata and any schema markup that search engines read. A firm that has used the same number for a decade may find it baked into PDFs, proposals, and boilerplate. Search the file server for it. The number will turn up in places no one remembers putting it.

The CRM needs the same discipline. Accounts, contacts, and open deals may carry the old number in phone fields, notes, or activity logs. A bulk update handles the structured fields; the notes need a human. If the CRM integrates with the phone system — and most modern ones, from HubSpot to Salesforce, will talk to RingCentral, Dialpad, or EEZYTALK — confirm the integration follows the number rather than the extension.

Billing deserves a glance, too. Invoices, contracts, and payment portals that display the main line should show the new one. A contractor whose customers pay by phone will notice the error faster than one whose customers pay online.

Consider a firm that runs its phone system alongside a CRM, a scheduling tool, and a file-sharing product. With EEZYTALK, those products sit in the EEZYVERSE family: one login across the products the company uses, and one central bill at eezycloud.com/account/. That does not eliminate the updates, but it reduces the number of passwords and invoices the office manager must track.

If a port stalls mid-transfer, support hours are published at eezycloud.com/support: Monday-Friday 9 AM-8 PM and Saturday-Sunday 9 AM-12 PM Eastern. A port that lands on a weekend deserves a calm check-in on Monday morning, not a panic call on Saturday.