Can You Keep Your Office Number When Switching to VoIP? (w/Examples) + FAQs

Yes, you can keep your office number when switching to VoIP in almost every case in the United States. The federal Local Number Portability rules under the Telecommunications Act of 1996 require carriers to hand your number to a new provider when you ask. This right is grounded in 47 U.S.C. § 251(b)(2) and enforced through 47 C.F.R. § 52.21–52.36.

The problem is that porting is not automatic, and a bad port can leave your business with no dial tone for days. Federal rules set the floor, but your old carrier, your new VoIP provider, and your own contracts all shape whether the port goes smoothly. The FCC’s 2009 Porting Interval Order set one business day as the standard for simple wireline ports, yet complex ports still take up to four business days.

A 2024 industry report from IBISWorld shows that over 85% of U.S. businesses with more than five employees now use some form of VoIP, and number portability is the single biggest reason they trust the switch. Losing a number that appears on signs, business cards, Google listings, and legal contracts is a direct hit to revenue and customer trust.

Here is what you will learn in this guide:

• 📞 Whether your specific office number qualifies for a VoIP port under federal and state law
• ⚖️ Which FCC rules, state PUC rules, and court cases shape your porting rights
• 🏢 How named businesses like a law firm, a dental office, and an online store handled real ports
• 🚫 The seven most common mistakes that kill a port request and the fix for each one
• 📝 Step-by-step porting forms, fees, timelines, and what to sign before you cut over

The Federal Right to Keep Your Office Number

The right to keep your office number when moving to VoIP starts with federal law. The Telecommunications Act of 1996 created Local Number Portability, or LNP, to stop carriers from holding customers hostage through their phone numbers. The FCC then built detailed rules in 47 C.F.R. Part 52 that bind every local exchange carrier, wireless carrier, and interconnected VoIP provider.

What “Local Number Portability” Really Means

Local Number Portability is the legal right to take your phone number with you when you change providers inside the same rate center. A rate center is a small geographic zone the phone system uses to route local calls. If your VoIP provider can serve your rate center, your number can move. The FCC’s consumer guide on number portability confirms that this right applies to wireline, wireless, and VoIP moves.

The consequence of this rule is that your old carrier cannot legally refuse a valid port request. A common misconception is that carriers “own” your number, but under FCC Docket 95-116 numbers are a public resource managed through the North American Numbering Plan. A real-world example is when a Chicago accounting firm switched from AT&T to RingCentral and moved its 312 area code line in under 48 hours because both carriers served the same rate center.

The FCC Porting Interval Order

The FCC’s 2009 Porting Interval Order, FCC 09-41, set a one-business-day standard for simple ports between wireline and wireless carriers. A simple port involves a single line, no complex features, and no pending orders on the account. Anything else is a complex port and can take up to four business days under the industry’s LNP Industry Forum guidelines.

The consequence of missing the one-day window is an FCC enforcement action, which has led to fines like the $100,000 consent decree with a regional carrier in 2019. A common misconception is that VoIP-to-VoIP ports are always fast, but if the number still sits on a legacy wireline carrier behind the scenes, the four-day complex port clock still applies. A real-world example is Dr. Anita Rao’s dental office in Austin, Texas, where a pending feature change on her Spectrum line pushed her port to Nextiva from one day to four.

Interconnected VoIP and the Duty to Port

The FCC extended porting duties to interconnected VoIP providers in FCC 07-188, which means providers like Vonage, 8×8, and Dialpad must accept and hand off numbers on the same footing as the old Bell companies. This rule closed a loophole that let some VoIP carriers refuse outbound ports. The consequence of refusing a port today is an FCC complaint under 47 C.F.R. § 52.36 and possible forfeiture penalties.

A common misconception is that a “softphone only” VoIP line cannot be ported, but if the number is a real 10-digit North American number, it can move. A real-world example is when Grasshopper handed a virtual 415 number to a small design studio moving to OpenPhone in three business days without a hitch.

State Nuances That Shape VoIP Porting

State law cannot block a federal port, but states can add rules around billing, notice, and dispute resolution. The California Public Utilities Commission requires carriers to disclose early termination fees in plain language, which matters because those fees often travel with a port. The New York Public Service Commission mirrors this rule and adds a 30-day billing dispute window.

California PUC Rules

California applies General Order 168 to protect telecom customers, including small business VoIP porters. The rule forces carriers to process disputes within 30 days and bars disconnect during an active billing dispute. The consequence of a carrier cutting service during a dispute is a CPUC complaint and possible refund order.

A common misconception is that VoIP is fully deregulated in California, but the CPUC’s 2023 VoIP classification order preserves consumer protections for interconnected VoIP. A named example is Carlos Mendez, who runs a bilingual real estate office in Los Angeles and used GO 168 to stop Frontier from disconnecting his 310 number during his port to Zoom Phone.

New York PSC Rules

New York’s Public Service Law § 92 requires carriers to keep service live until a port completes. The state also requires written notice of any fee over $25 tied to a port. The consequence of skipping this notice is a refund and a Department of Public Service citation.

A common misconception is that New York treats VoIP like a utility, but the state exempts most VoIP from rate regulation while keeping porting and billing rules in place. A named example is Rachel Goldstein’s Brooklyn bakery, which ported its 718 number to Ooma Office after her old carrier tried to tack on a $50 “release fee” that was never disclosed in writing.

Texas PUC Rules

The Public Utility Commission of Texas follows 16 Texas Administrative Code § 26.130 on local number portability. Texas requires carriers to provide a Customer Service Record within four business days of a written request. The consequence of delay is a formal complaint through the PUC’s customer protection division.

A common misconception is that rural Texas numbers cannot be ported, but every rate center in the state falls under the LNP rules. A real-world example is a Lubbock law firm that ported a 50-line PRI from CenturyLink to GoTo Connect in nine business days because it was a complex port, not a simple one.

Local vs. Toll-Free Number Porting

Local numbers and toll-free numbers follow two different legal tracks. Local numbers move through the Number Portability Administration Center, or NPAC, managed by iconectiv. Toll-free numbers move through Somos, Inc., using the RESPORG system.

How Local Porting Works

Local porting uses a Letter of Authorization, or LOA, plus a recent phone bill as proof of ownership. Your new VoIP provider submits the port request, and the losing carrier checks the Customer Service Record for a match. The consequence of any mismatch, like a wrong suite number, is an instant port rejection.

A common misconception is that the billing telephone number and the number you want to port are always the same, but on multi-line accounts they often differ. A named example is Priya Shah’s yoga studio, which listed the wrong BTN on its LOA and lost three days before her port to Grasshopper went through.

How Toll-Free Porting Works

Toll-free numbers like 800, 888, 877, 866, 855, 844, and 833 are controlled by a RESPORG, which is the Responsible Organization in the Somos database. To move a toll-free number, your new VoIP provider files a RESPORG change, not a standard LNP port. The consequence of skipping this step is that calls keep routing to your old carrier even after you think you switched.

A common misconception is that toll-free ports are faster, but they often take two to five business days because the RESPORG change must clear Somos. A real-world example is a Phoenix HVAC company that moved its 1-800 line to Nextiva and had to coordinate the RESPORG change with its old answering service to avoid a 24-hour outage.

Three Real Porting Scenarios

Below are the three most common porting paths, each shown with the triggering action and the legal or business consequence.

Simple Single-Line Port from Wireline to VoIP

Complex Multi-Line PRI Port to Hosted VoIP

Toll-Free RESPORG Change

Named Examples of Office Number Ports

Real businesses face real porting puzzles, and these three stories show how federal and state rules played out in practice.

Example 1: Maria Chen, Boston Law Firm

Maria Chen runs a three-partner immigration law firm in Boston and wanted to move her 617 main number from Verizon to RingCentral. Her goal was to keep the number on her Massachusetts Bar filings and client retainers. She pulled her CSR, matched it exactly to her LOA, and her simple port completed in one business day under FCC 09-41.

The lesson is that matching the CSR to the LOA down to the suite number is the single biggest predictor of a clean port. Maria also timed the cutover for a Friday evening so her Monday morning calls rang on the new system. Her total downtime was under two minutes.

Example 2: Dr. James Okafor, Houston Dental Practice

Dr. James Okafor operates a five-chair dental office in Houston and needed to port a 10-line hunt group from AT&T to 8×8. His goal was to keep his 713 lead number listed on every insurance directory. Because the account had a pending feature change, the port became complex and ran four business days under the ATIS LNP guidelines.

The lesson is that any pending order on your old account turns a simple port into a complex one. Dr. Okafor canceled the pending feature first, resubmitted his LOA, and cut over with a soft launch day where both systems ran in parallel. He lost zero calls during the window.

Example 3: Emma Rodriguez, Denver E-Commerce Shop

Emma Rodriguez owns a Denver-based online pet supply store and wanted to port her 1-888 support line from a legacy call center to Dialpad. Her goal was to keep the toll-free number printed on thousands of shipped boxes. She filed a RESPORG change through Somos and synced the cutover with her Zendesk integration.

The lesson is that toll-free ports need RESPORG coordination, not a standard LNP request. Emma also updated her caller ID name to match her brand, which boosted answer rates on outbound support callbacks. Her port closed in three business days.

Mistakes to Avoid When Porting Your Office Number

Porting mistakes are almost always fixable before you sign, but most become expensive after the cutover. Here are the seven mistakes that kill the most ports.

• Submitting an LOA that does not match the CSR exactly, which causes an automatic rejection and resets every timeline
• Canceling your old service before the port completes, which strands your number and can trigger a “snapback” under NPAC rules
• Ignoring early termination fees in your old contract, which can add hundreds of dollars and delay the release of your number
• Forgetting to list every DID on a multi-line account, which leaves orphan numbers on the old carrier and breaks hunt groups
• Porting during a pending order on the old account, which forces a complex-port path and adds up to three business days
• Skipping the RESPORG change on a toll-free port, which leaves calls routing to the old platform even after you think you switched
• Failing to test 911 service on the new VoIP line, which can violate Kari’s Law and RAY BAUM’S Act if the office is a multi-line telephone system

The Porting Process Step-by-Step

The porting process has clear steps, and each one has its own form, fee, and decision point. Knowing the steps turns a scary cutover into a routine project.

Step 1: Pull Your Customer Service Record

The Customer Service Record, or CSR, is the master file your old carrier keeps on your account. Request it in writing and save the PDF. The consequence of skipping this step is that your LOA will almost certainly mismatch, and your port will bounce on day one.

A common misconception is that the CSR is the same as your latest invoice, but CSRs list the exact BTN, service address, and authorized contact that the port system checks. A real-world example is a Miami travel agency that used an old invoice, missed a suite number update, and lost five days resubmitting.

Step 2: Sign the Letter of Authorization

The Letter of Authorization is the legal document that tells your old carrier to release the number. Your new VoIP provider drafts it, and a corporate officer signs. The consequence of a wrong signature authority is a rejected port under FCC slamming rules in 47 C.F.R. § 64.1120.

A common misconception is that any employee can sign the LOA, but only the person on the CSR as authorized contact has legal power. A named example is David Kim’s Seattle marketing shop, where his office manager signed by mistake and the port delayed ten business days until David re-signed.

Step 3: Schedule the Firm Order Commitment

The Firm Order Commitment, or FOC, is the date the old carrier agrees to release the number. Your new VoIP provider negotiates this date after LOA approval. The consequence of missing the FOC window is a full restart of the port request.

A common misconception is that the FOC can be pushed back freely, but many carriers charge a reschedule fee of $25 to $50. A real-world example is a Portland bookstore that missed its FOC because of a holiday closure and paid $35 to reschedule through Vonage Business.

Step 4: Cut Over and Test

Cutover is the moment the number actually routes to your new VoIP. Most providers recommend a 15-minute window outside business hours. The consequence of skipping a test call from an outside line is discovering a routing error after customers start calling.

A common misconception is that cutover always finishes in seconds, but DNS and carrier propagation can take up to an hour. A named example is Aisha Patel’s Atlanta consulting firm, which cut over at 6 a.m. on a Saturday and used the weekend to test all 20 DIDs before Monday open.

Do’s and Don’ts of VoIP Number Porting

Following the right habits keeps your port on schedule and your business on the phone.

• Do pull your CSR before you sign any new VoIP contract, because it is the single source of truth for your account
• Do keep your old service active until the FOC date, because early cancellation can orphan your number for weeks
• Do test 911 service on every new VoIP line, because Kari’s Law and RAY BAUM’S Act both carry federal penalties
• Do schedule cutover outside peak hours, because even a clean port can have a 15-minute routing gap
• Do keep written records of every LOA, CSR, and FOC email, because disputes depend on paper trail evidence
• Don’t share your PIN or account password with unverified sales reps, because slamming is still a top FCC complaint
• Don’t agree to a port date during a pending feature change, because that single factor turns simple ports into complex ones
• Don’t port without reading your old contract’s early termination clause, because ETFs can travel with your number
• Don’t forget to update your Google Business Profile and directory listings, because stale listings route callers to dead lines
• Don’t skip the RESPORG change on toll-free numbers, because LNP rules alone do not move 8YY traffic

Pros and Cons of Keeping Your Office Number on VoIP

Keeping your number has clear wins, and a few trade-offs worth naming.

• Pro: Customer trust stays intact, because the number on signs, cards, and contracts keeps working without a notice campaign
• Pro: SEO and local citations keep their value, because Google Business Profile ranks partly on NAP consistency
• Pro: Legal documents and contracts stay valid, because many agreements list the phone number as the notice channel
• Pro: 911 and E911 compliance travels with the number, because interconnected VoIP providers must register the dispatchable location
• Pro: Marketing spend stays protected, because billboards, vehicle wraps, and print ads keep working
• Con: Porting fees can run $10 to $35 per number, because each carrier sets its own release fee
• Con: Complex ports can take up to four business days, because the ATIS LNP guidelines cap the simple-port window
• Con: Early termination fees can bite, because old contracts often lock in 24 or 36 months
• Con: 911 must be reconfigured with a new dispatchable address, because VoIP does not inherit the old physical location
• Con: Some rural rate centers still lack full VoIP coverage, because not every CLEC has built out every NPA-NXX

Key Rulings and Enforcement Actions

Court rulings and FCC orders shape every port, and a handful stand out.

Vonage Holdings Corp. v. Nebraska PSC

In Vonage Holdings Corp. v. Nebraska PSC, 564 F.3d 900 (8th Cir. 2009), the Eighth Circuit held that state universal service fees on nomadic VoIP are preempted when they conflict with federal policy. The ruling confirmed the FCC’s light-touch VoIP framework. The consequence for porting is that interconnected VoIP providers must follow federal LNP rules without state-added barriers.

FCC Slamming Enforcement

The FCC’s anti-slamming rules in 47 C.F.R. § 64.1120 require verified authorization before any carrier change. The FCC’s 2023 consumer complaint data still lists slamming in the top 10 wireline complaint categories. The consequence of a slammed port is a full reversal and potential forfeiture against the offending carrier.

2024 FCC Action on Porting Delays

In 2024 the FCC opened an inquiry into repeated porting delays by large incumbent carriers. The agency signaled tighter enforcement of the one-business-day standard. The consequence for VoIP buyers is that delays beyond four business days now carry a clearer path to an FCC complaint under 47 C.F.R. § 52.36.

Key Entities in the Porting Process

Several organizations shape every VoIP port, and each plays a distinct role.

• The FCC writes and enforces the federal LNP rules and runs the slamming complaint process
• iconectiv runs the NPAC, which is the national database that tracks every ported local number
• Somos, Inc. manages the toll-free database and processes RESPORG changes for 8YY numbers
• ATIS publishes the LNP industry operating guidelines that carriers follow on timing and data fields
• State PUCs like the CPUC, NY PSC, and Texas PUC handle billing and consumer protection disputes tied to ports
• VoIP providers like RingCentral, Nextiva, 8×8, Vonage, Dialpad, Zoom Phone, GoTo Connect, Ooma Office, OpenPhone, and Grasshopper serve as the gaining carriers in most office ports
• Incumbent carriers like AT&T, Verizon, Lumen/CenturyLink, and Frontier serve as the losing carriers that must release the number

What to Put on Your Letter of Authorization

The LOA is the short legal form that powers the whole port, and every field matters.

• Legal business name exactly as it appears on the CSR, because any variant triggers a match failure
• Service address with suite or unit number, because the rate center check reads the full address
• Billing telephone number, or BTN, because the NPAC uses it as the primary key for the port
• Full list of DIDs to port, because any number not listed stays on the old carrier
• Authorized signer’s name, title, and date, because FCC anti-slamming rules require a verifiable authority
• New VoIP provider’s name and OCN, or Operating Company Number, because the NPAC routes by OCN
• Requested port date, because the FOC negotiation starts from this target

FAQs

Can I keep my office number when switching to VoIP?

Yes. Federal LNP rules under 47 U.S.C. § 251(b)(2) and 47 C.F.R. Part 52 give every U.S. business the right to port a local or toll-free office number to an interconnected VoIP provider.

Does it cost money to port my office number?

Yes. Most losing carriers charge a release fee of $10 to $35 per number, and some gaining VoIP providers waive their side of the fee as part of onboarding promotions.

Will my phone service go down during the port?

No. A properly scheduled port keeps your old line live until the FOC cutover moment, which usually causes under 15 minutes of routing gap when timed outside business hours.

Can my old carrier refuse to release my number?

No. Refusing a valid port violates FCC rules under 47 C.F.R. § 52.36 and can trigger an FCC complaint, forfeiture penalties, and a forced release of the number.

Are toll-free numbers ported the same way as local numbers?

No. Toll-free numbers move through a RESPORG change in the Somos database, while local numbers move through the NPAC using a standard LNP request and LOA.

Can I port a number from a different state to my VoIP system?

Yes. VoIP is nomadic, so a 212 New York number can ring at a Denver desk as long as the gaining VoIP provider serves the original rate center and handles E911 address registration correctly.

Do I need to keep my old service active during the port?

Yes. Canceling early can orphan your number, trigger a snapback at the NPAC, and force you to start the entire port request over with a new LOA and FOC date.

Can I port a number tied to a PRI or multi-line business system?

Yes. Multi-line PRI ports are complex ports under ATIS guidelines and usually finish in four business days, as long as every DID is listed on the LOA and no pending orders sit on the account.

Will porting break my 911 service?

No. As long as your VoIP provider follows Kari’s Law and RAY BAUM’S Act and registers the dispatchable location, 911 service works on the new line once cutover completes.

Can I port my number if I’m still under contract with my old carrier?

Yes. Contracts do not block porting, but early termination fees may still apply, and the losing carrier cannot hold the number hostage to collect those fees under FCC rules.

How long does a simple VoIP port take?

Yes, one business day is the FCC standard for simple wireline-to-VoIP ports under FCC 09-41, and most gaining VoIP providers meet that target when the LOA matches the CSR.

Can I port a Google Voice number to a business VoIP provider?

Yes. Google Voice numbers can port out for a small fee, and most business VoIP providers accept them as a standard LNP request after Google releases the number through its porting tool.