How Long Does It Take to Port a Phone Number?

Executive Summary

For a clean consumer mobile port, the realistic answer is a few hours to one working day. For a single landline or an ordinary business Voice over Internet Protocol (VoIP) number, allow several business days to two weeks from order submission, even where the final regulated activation interval is one day. Multi-line, range, partial-account and otherwise complex ports commonly need two to six weeks. The number should keep receiving calls on the old service while the order is prepared and validated. The short cutover itself may cause a few minutes of uneven routing, but it is not normally an outage lasting for the full order interval. Verizon, for example, says the number remains active with the old carrier until the switch finishes ^[1], while one business provider describes a cutover lapse that “normally lasts only a few minutes” ^[2]. Neither statement is a universal guarantee.

The regulated clocks differ sharply. In the United States, a complete simple wireline-to-wireline or intermodal request has a one-business-day interval, while a non-simple request has a four-business-day interval ^{[3] [4]}. Canada sets 2.5 business hours for a simple wireless-to-wireless port and two business days for a simple intermodal port ^{[5] [6]}. In the United Kingdom, mobile service should normally be ready within one working day after the new provider receives the Porting Authorisation Code (PAC) ^[7]. Australia says mobile ports usually take three hours, while individual local numbers generally take 8 to 15 days (Source: acma.gov.au) (Source: acma.gov.au).

Most avoidable delay comes before activation. The gaining provider submits a Local Service Request (LSR) or its local equivalent. The losing provider either validates it and returns a Firm Order Commitment (FOC), or rejects it. Exact account name, service address, account number and transfer personal identification number (PIN) matter. A freeze or number lock must be removed. Partial ports need a replacement billing number for lines left behind, and related ranges may have to move together. Correcting a rejection can restart the response clock ^[8]. A contract or unpaid balance can survive the move, but is not universally a lawful reason to withhold the number. The safest rule is simple: never cancel the old service before the gaining provider confirms completion. U.S., Canadian, British and Australian primary sources all support keeping the old line active through the transfer ^{[9] [10] [11]} (Source: acma.gov.au).

Introduction and Background

“How long does number porting take?” has two different answers. The order interval runs from a complete request through validation, scheduling and activation. The cutover interval is the much shorter period when routing changes from the old network to the new one. A business can wait ten days for an order yet experience only minutes of uncertain inbound routing. Treating those intervals as one number is the central source of confusion.

Portability also depends on the path. Wireless-to-wireless transfer is usually the fastest. A simple wireline-to-wireline request moves through established local number portability processes. A wireline-to-VoIP transfer is intermodal in the United States, and provider readiness may make its total lead time longer than the regulatory activation clock. VoIP-to-VoIP can still involve an underlying carrier, a reseller and a losing provider, so the retail brands alone do not reveal complexity. A toll-free move in the United States is different again: it changes the controlling Responsible Organization, or RespOrg, through Somos rather than using ordinary local number portability. Somos describes its Responsible Organization Change request as changing only the controlling organization ^[12].

This report separates regulatory maximums, official typical times and individual carrier service levels. A regulator’s one-day activation rule does not mean every order submitted today will be working tomorrow. The clock may begin only after a correct request, validation and technical readiness. Conversely, a provider’s two-week estimate does not imply two weeks of downtime.

For a small business, the practical objective is continuity. Keep the old account active, prepare the destination before the FOC date, test inbound and outbound calling, and cancel only after completion is confirmed. That approach is more dependable than choosing a provider solely because its marketing page gives the shortest estimate.

Number Porting Taxonomy

Wireless-to-wireless

A clean mobile port typically requires an active number, the account number, the exact account holder information and a transfer PIN or authorization response. It is fast because the request is standardized and generally affects one service at a time. The U.S. Federal Communications Commission (FCC) has described roughly 2.5 hours as an industry-agreed interval, but has not imposed a specific federal wireless-to-wireless deadline ^[13]. Verizon instead publishes its own 4 to 24 business hour estimate for an inbound mobile transfer ^[14]. These are different types of evidence and should not be merged into a single “U.S. rule.”

Canada’s CRTC does set 2.5 business hours for a simple wireless-to-wireless port ^[5]. Rogers publishes the same 2.5-hour completion level after the customer replies to its authorization message ^[15]. That authorization must be answered within 90 minutes or the process restarts ^[16].

Wireline-to-wireline

A simple single-line landline port can have a short regulated activation interval but a longer retail lead time. The U.S. rule requires a simple wireline-to-wireline port within one business day after an accurate, complete request enters the eligible window ^[3]. Verizon’s consumer estimate for a landline transfer is 2 to 10 business days, illustrating the difference between the regulatory interval and the end-to-end customer experience ^[17].

Multiple lines, switch translations, partial-account moves and negotiated project ports do not fit the simple category. In Canada, porting a single line away from a multi-line account is expressly not a simple port ^[18]. Complex Canadian ports are negotiated case by case ^[19].

Wireline-to-VoIP and VoIP-to-VoIP

In U.S. regulation, interconnected VoIP is included in the intermodal category ^[20]. A clean simple request therefore has the one-business-day regulatory porting interval, but the new provider may quote a longer order lead time for documentation, underlying-carrier coordination and scheduling.

Published U.K. service levels show this spread. BT Business says a single-line number moving to Digital Voice for Business takes at least seven working days, while 31 or more multi-line numbers take at least 22 working days ^{[21] [22]}. Voipfone gives 7 to 14 days for most single-number ports ^[23]. Twilio says U.K. geographic and non-geographic ports can take four to six weeks after documentation ^[24]. These are provider-published service levels, not Ofcom maximums.

Toll-free RespOrg changes

U.S. toll-free numbers are administered through the Somos Toll-Free Number Registry. Moving control uses a RespOrg Change, often shortened to ROC. It is not an LNP port, even if the customer and provider casually call it one. The documentation, authorization and losing-organization response are therefore different. A business should ask specifically whether a quoted timeline covers a local-number port or a toll-free RespOrg change ^[12].

Number Porting Time by Country

Table 1 compares the most useful official clock or current published norm as of September 21, 2026. “Regulated” means a rule or code requirement. “Official typical” is regulator guidance, not a hard ceiling. “Carrier level” applies only to that provider and process.

The table shows why “porting takes one day” is incomplete. Even within one jurisdiction, the answer spans hours to weeks. The shortest figures usually describe clean mobile requests or the activation stage. The longest figures usually describe document review, complex fixed-number configurations, ranges and coordinated business migrations.

What a Business Experiences at Cutover

The old line ordinarily remains the live destination during order processing. Canada’s industry guidance says the old phone should work while the customer waits ^[27]. Telstra makes the same point for an Australian mobile transfer (Source: telstra.com.au).

At activation, routing updates do not necessarily reach every network simultaneously. Some callers may reach the old route while others reach the new one for a short period. BT Business estimates a maximum of two hours, usually less, for its Digital Voice for Business interruption ^[28]. Another provider says a lapse normally lasts only a few minutes ^[2]. These observations are useful planning ranges, not promises.

Ofcom’s U.K. business guidance gives the stronger regulatory boundary: where continuity is technically feasible, the old provider should continue service until completion, and any loss of service must not exceed one working day ^{[11] [29]}. Canada’s CRTC cautions that an intermodal transfer can briefly disrupt service, including emergency access ^[30]. A business should therefore schedule a fixed or intermodal cutover for a staffed period, keep an alternate mobile path available and avoid making emergency-service assumptions during transition.

Table 2 separates the phases and assigns ownership.

The important planning implication is that a ten-day port is not a ten-day outage. The business risk is concentrated at the scheduled cutover and in configuration errors after it. Temporary call forwarding can reduce exposure when the old provider supports it. One provider explicitly recommends forwarding the old line to a temporary number during the port ^[33].

Why Ports Stall or Get Rejected

Most preventable failures are data or scope problems, not network failures. A rejected request returns to correction and resubmission. Microsoft states that the response service-level clock restarts after correction ^[8]. That loop can turn a nominal one-day activation interval into a multi-week project.

• Account name mismatch. Use the customer name exactly as the losing provider stores it, including business suffixes. Rogers requires the receiving account to use the same last name for a landline transfer ^[34].

• Wrong service address. The service address can differ from the billing or mailing address. Bandwidth explicitly instructs applicants to provide the service address, not the billing address, for wireline and VoIP ports ^[35].

• Missing account number or transfer PIN. Microsoft requires the account PIN for mobile numbers ^[36]. Bandwidth identifies an incorrect PIN as a common rejection cause ^[37].

• Port-out freeze or number lock. Disable the safeguard before submission. Verizon Business requires Number Lock to be disabled before creating the Number Transfer PIN ^[38]. Microsoft advises clearing a freeze with the old provider before resubmission ^[39].

• Pending account changes. An open feature, address or service order can block a port. Zoom says any active order on the account prevents the numbers from porting ^[40]. Complete or cancel unrelated work first.

• Partial ports. If the billing telephone number is moving but other lines remain, the old account needs a replacement billing number. Lumen expressly requires one for retained lines ^[41].

• Multi-line accounts and ranges. Put related numbers on the same Letter of Authorization (LOA) where required. Intermedia says numbers on one account must be submitted on one LOA ^[42]. Twilio says associated U.K. numbers must move together as a range ^[43].

• Overlapping requests. Do not send parallel requests for the same account. Microsoft says the losing provider processes the first and rejects the rest ^[44].

• Balance or contract confusion. A balance or minimum term may remain payable after the number moves. In the United States, the FCC says a wireless carrier may collect outstanding fees but may not hold the number while settling the account ^[45]. Australia likewise says a telco cannot refuse or delay a port because money is owed (Source: acma.gov.au). This is jurisdiction-specific, not a universal rule.

• FOC coordination failure. Related orders should reach an accepted state together. Intermedia notes that a provider may have to give up an existing FOC and resubmit for a later date when companion orders are unresolved ^[46].

Practical Pre-Port Checklist and Sequence

Before submitting

• Inventory every number. Include main numbers, direct inward dial numbers, fax, alarm, elevator, payment-terminal and hunt-group lines.

• Classify the request. Mark mobile, simple single landline, VoIP, partial multi-line, range and toll-free numbers separately.

• Get primary records. Request the current CSR and download the most recent complete bill. Telnyx requires the most recent bill for each request ^[47].

• Copy, do not normalize. Preserve the exact legal name, punctuation, service address, postal code and account number. Telnyx says reseller submissions must match the CSR ^[48].

• Collect authorization. Obtain a current transfer PIN, PAC or equivalent. In the U.K., a PAC is valid for 30 days ^[49]. In Australia, the gaining provider must obtain the customer’s permission before starting (Source: acma.gov.au).

• Remove locks and settle scope. Disable port protection or account locks, close pending changes, choose the replacement billing number and confirm whether a range must move intact.

• Build the destination first. Configure users, greetings, routing, voicemail, emergency address and fallback numbers before the scheduled port.

Submission through activation

1. The customer authorizes the gaining provider. Sign the LOA where needed. The signer should match the existing carrier’s record ^[50].

2. The gaining provider submits the request. It maps the retail order into an LSR or jurisdiction-specific transaction.

3. The losing provider validates. It either rejects with a reason or accepts and issues the FOC. Wrong data should be corrected from the carrier record, not guessed.

4. Both sides schedule activation. Microsoft describes the losing provider releasing numbers on the FOC date ^[51].

5. The business staffs cutover. Keep access to both systems, place test calls from several mobile and fixed networks, and verify voicemail and routing options.

6. The gaining provider confirms completion. Do not infer completion merely because one test call arrived correctly.

7. The customer reviews the old account. Cancel only services no longer needed, while preserving any lines that were excluded from the port.

The strongest operational rule deserves repetition: do not cancel the old service before the port completes. Verizon tells customers not to cancel while the number is switching ^[52]. Voipfone gives the same instruction for U.K. ports ^[53]. ACMA explains the reason in Australia: only an active service can be ported, so the gaining telco must tell the customer not to disconnect (Source: acma.gov.au).

Choose the destination before moving the number

Portability does not determine whether the destination system fits the business. Table 3 places the direct provider publishing this report in the relevant category without treating it as a general phone-system replacement.

The cheapest or fastest destination is not automatically the right one. A team that needs queues and agent supervision should select a contact-centre product. A team that needs someone outside the company to answer should select an answering service. The autoattendant.io option fits only the narrower case described in the table; its own page says an existing business number can be ported in ^[56].

Data Analysis and Evidence

The evidence supports four planning bands rather than one universal average.

• Hours: clean mobile-to-mobile ports. Canada’s regulated figure is 2.5 business hours ^[5]. Australia’s code requires 90% within three hours and 99% within two business days (Source: acma.gov.au) (Source: acma.gov.au). These thresholds show both the central case and the tail.

• One to two business days: validated simple intermodal or fixed-number activation clocks. The U.S. simple wireline/intermodal rule is one business day ^[3]; Canada’s simple intermodal interval is two business days ^[6].

• One to two weeks: ordinary retail landline or VoIP order lead time. BT Business says at least seven working days for one line ^[21]; Voipfone says 7 to 14 days for most single numbers ^[23].

• Several weeks: complex business, range and coordinated ports. Australia says more than one local number can take up to 30 days (Source: acma.gov.au); Twilio quotes up to four to six weeks for U.K. geographic and non-geographic ports ^[24].

The gap between a statutory clock and a carrier quote is not necessarily a contradiction. They often measure different endpoints. U.S. rules start from an accurate, complete LSR, while the customer experiences document collection, corrections, order queues and scheduling before that interval. Ofcom’s non-mobile one-day activation provision similarly starts only after necessary validation and readiness conditions are satisfied ^[26].

Scale changes the distribution. Verizon Business publishes a five-business-day FOC for a clean request involving more than one but fewer than 20 numbers, while more than 20 becomes a negotiated project ^[57]. Australia’s local-number code distinguishes automated simple service from manually coordinated complex service (Source: austelco.org.au). This is why a business with 50 direct-dial numbers should not plan from a consumer mobile statistic.

No authoritative cross-country dataset measures the average cutover outage across all port types. Available primary evidence instead establishes continuity expectations and provider-specific observations ranging from a few minutes to two hours. The defensible planning assumption is therefore a short but non-zero cutover risk, backed by an alternate contact method, rather than either “no outage” or “the line is down for the whole port.”

Implications and Future Directions

The regulatory trend is toward shorter activation intervals and stronger customer control, but identity checks are also becoming more explicit. Australia requires the gaining provider to confirm that the requester holds the rights of use for the number (Source: legislation.gov.au). Canada uses customer authorization messaging for mobile transfers. These controls add a deliberate action, but they also make an unauthorized transfer harder.

Automation can shorten the interval after a clean request. Australia’s local-number code targets at least 90% of Category A activations within 30 minutes after valid electronic cutover advice (Source: austelco.org.au). Yet business complexity remains difficult to automate: partial accounts, number ranges, resellers and custom routing create dependencies outside the activation transaction.

For buyers, the useful questions are becoming more precise:

• What starts the quoted clock? Ask whether it begins at order entry, document acceptance, FOC or activation.

• What is excluded? Ask whether toll-free numbers, ranges, direct inward dial blocks and partial accounts have separate lead times.

• Who owns a rejection? Require a named path for obtaining the losing carrier’s exact rejection reason and correcting it.

• What happens at cutover? Ask about temporary numbers, forwarding, rollback, testing and staffed support.

• What confirms completion? Define successful inbound calls from multiple networks, outbound caller identification, voicemail, emergency address and every menu route.

Providers cannot responsibly guarantee a universal date because the losing carrier, customer data and number configuration remain outside any one party’s control. A more meaningful service commitment states documentation requirements, response targets, escalation ownership and a cutover plan.

Frequently Asked Questions (FAQs)

How long does mobile number porting take?

Plan for a few hours to one working day for a clean wireless-to-wireless transfer. Canada regulates simple mobile ports at 2.5 business hours ^[5]; Ofcom says a U.K. mobile should normally be ready within one working day after PAC submission ^[7]; ACMA says an Australian mobile port usually takes three hours (Source: acma.gov.au).

How long does landline number porting take?

A straightforward landline normally takes several business days to two weeks end to end. The U.S. regulated simple-port interval is one business day after a complete eligible request ^[3]. Multi-line and complex ports take longer.

How long does VoIP number porting take?

Allow one to two weeks for a clean single number and two to six weeks for ranges, partial accounts or complex international processes. U.K. provider examples span 7 to 14 days for most single-number ports and up to four to six weeks for geographic and non-geographic ports ^{[23] [24]}.

Will the business phone line go dark during the port?

Normally, no. The old service should carry calls while the order is pending. A short cutover interruption or mixed routing is possible. Plan for minutes, keep a backup contact method, and do not promise zero downtime. For one current provider example, BT Business says its interruption is likely no more than two hours and typically shorter ^[28].

Can an unpaid balance or contract stop the port?

The answer depends on jurisdiction, but the financial obligation and the right to port are often separate. In Australia, the losing telco cannot refuse or delay the move merely because money is owed (Source: acma.gov.au). A customer can still owe early termination fees or a final balance after moving.

When should the old phone service be cancelled?

Only after the gaining provider confirms the port is complete and the business has tested the new route. Cancelling early can make the number inactive and no longer portable. Verizon, Canada’s telecommunications industry and ACMA all explicitly direct customers to keep the current service active ^{[9] [10]} (Source: acma.gov.au).

Conclusion

The realistic porting range is hours for a clean mobile number, several business days to two weeks for a single landline or VoIP number, and two to six weeks for complex business ports. Those are planning ranges, not promises. The governing clock depends on jurisdiction, port type and the point at which the clock begins.

For continuity, the order interval matters less than the cutover plan. The old service normally remains active until activation. A brief period of mixed routing or interruption can occur at cutover, so the business should staff the change, keep a backup contact method and test from multiple networks.

The most effective way to shorten the process is administrative precision: obtain the current carrier record, match the name and service address exactly, provide the right account number and transfer PIN, remove locks, resolve pending orders, inventory every line, and coordinate partial accounts or ranges as one project. If a request is rejected, correct the carrier record rather than guessing, because resubmission can restart the clock.

Above all, keep the old account and every number being moved active until the gaining provider confirms completion. That single control prevents the most consequential avoidable failure and applies whether the destination is another mobile carrier, a landline, a VoIP service or a small-business call-routing product.