This guide contains no paid placements or affiliate links.
When a business must keep an existing phone number, compare providers by the transfer and operating plan before comparing monthly seat prices. A provider's statement that it supports number porting does not establish that it can accept every number in the account or preserve every associated service. Eligibility, records, configuration and a checked cutover are separate requirements.
This guide is a procurement and planning framework. USAReviewers has not ported test numbers between the providers discussed or measured their service quality. It does not initiate a transfer. Confirm the current process, requirements and terms directly with the existing and proposed providers before authorizing changes.
Start with a number inventory
List every number the business expects to keep, including its purpose, current provider and account relationship. Identify the main published number, direct lines and any numbers used by specific systems. Do not assume the number appearing on an invoice is the only number affected by the service.
For each one, record what it currently does: incoming voice, outbound calling, text messaging, fax or another function. A number can be associated with services that are easy to overlook when the buying team focuses on the front desk.
Include where the number is published and which people or systems depend on it. This is not a request to change those listings. It is a way to understand the impact if the transfer or routing is delayed.
Keep the inventory in an appropriately restricted location. Account identifiers and authorization information should not be placed in a broadly shared project document simply because several people are helping with the purchase.
Ask for eligibility on the exact numbers
Twilio's portability documentation illustrates that a provider may distinguish supported numbers, unsupported cases and cases requiring manual handling. An automated eligibility result is part of a process, not a universal promise about all numbers or all providers.
Ask the proposed provider to check the actual number list through its authorized process. If a number needs manual review, obtain the route and required information. If a number is unsupported, resolve the business implication before signing a contract built around keeping it.
Separate number portability from feature support. Ask whether the destination can provide the voice, messaging and other required functions for each number after transfer. A successful port does not, by itself, configure a call menu or establish every messaging capability.
Record the answer with the provider's name, date and any conditions. If the salesperson and porting team give different answers, have the provider reconcile them before the business relies on the claim.
Verify the account records before submitting
Ask what account name, address, number list, authorization and other records the gaining provider requires. Obtain them through the existing provider's legitimate account process. Small differences between a trade name and the account's recorded legal name can create administrative work that should be resolved early.
Twilio's porting overview describes a process involving account details, authorization, status and coordination. It is an example of why a transfer needs a responsible owner and complete records rather than a last-minute request after new hardware arrives.
Identify the person authorized to approve the transfer. Do not use an employee's personal account access as a substitute for proper business authorization. If ownership records are uncertain, resolve them with the providers before submitting a request.
Ask the providers how the existing service should remain active through the transfer. Do not independently cancel or disconnect it in anticipation of a port. The correct sequence should be explicit in the provider-confirmed plan.
Map the services that may share the account
Review whether the current telephone service is bundled with internet access, equipment rental, other lines or a contract commitment. Ask what changes when selected numbers move and what remains billable.
Do not assume that porting one number cancels the entire account or leaves every other service untouched. Both assumptions can be costly. Request an account-specific explanation of the intended change and any required follow-up.
If equipment or a special service relies on a line, ask its provider about compatibility with the proposed arrangement. This can include systems that do not behave like ordinary handset calls. Do not move a consequential connection based only on a generic claim that a new phone platform supports voice.
Keep contractual and technical questions separate. A technically possible transfer may still require attention to equipment return, remaining charges or a minimum commitment. Ask for the actual terms rather than relying on another customer's experience.
Build the destination before the cutover
The new provider should explain what can be configured and tested before the number transfers. This may include users, devices, routing, hours, voicemail and supported integrations. Use temporary or test arrangements approved by the provider where appropriate.
Write the intended caller journey in ordinary language. During business hours, which group answers? After hours, what message and next action should a caller receive? If no one answers, where does the call go? A platform with many routing features is useful only if someone configures the desired behavior.
If considering automated answering, the AI receptionist buying guide covers a separate product evaluation. The number transfer should not be used to introduce an untested answering workflow at the same moment unless the business has deliberately prepared and approved both changes.
Keep emergency-calling requirements with the provider's specific guidance and the business's responsible administrator. Confirm required location information and procedures using the provider's authorized process. Do not place an unauthorized emergency test call to check setup.
Agree what the date actually means
Ask whether a proposed date is requested, provisionally accepted or confirmed by the relevant providers. Use those labels consistently in the project plan. A requested date should not be advertised internally as a guaranteed completion time.
Find out who receives status changes and how delays or rejections are communicated. The person watching the port should have access to the provider's actual status information and a support route, not only forwarded sales messages.
Choose a cutover period with the business's operating needs in mind, subject to the providers' available process. Ensure the people needed for verification and escalation are available. A technically convenient time can be operationally poor if nobody can test the call flow afterward.
Prepare one contact sheet that remains available if the new phone service is unavailable. Give the transfer owner a confirmed alternative way to reach the provider and the internal decision-maker. Store it somewhere accessible to the authorized team without depending on the service being moved. During a delay, record the provider's status and next promised update separately from the business's next operational decision. This makes it easier to distinguish waiting for carrier coordination from a configuration task that the team can actually resolve.
The software-migration checklist provides a broader planning structure. For phone service, the critical distinction is between a transfer status and verified service behavior.
Prepare an acceptance matrix
Create a table for the functions the business actually uses. Each row needs an expected result, a responsible tester and a place to record the outcome. Use ordinary authorized calls and messages, avoiding unnecessary customer disruption.
| Function | Example acceptance question |
|---|---|
| Incoming calls | Does the published number reach the intended route? |
| Outgoing calls | Can an authorized user call out with the expected supported identity? |
| Business hours | Does the current schedule route calls correctly? |
| No answer | Does the agreed fallback occur? |
| Voicemail | Can the correct people receive and retrieve it? |
| Messaging | Do the required approved messaging functions work? |
| Devices and apps | Can each required user or device perform its role? |
Do not fill the matrix with features the business does not use. Its purpose is to prove the important workflow and reveal a specific failure, not to create a long ceremonial checklist.
Plan for partial success
A cutover can appear complete from one perspective while a required function remains unresolved. For example, an ordinary incoming call may work while a particular routing branch or messaging function does not. Keep each acceptance row separate rather than declaring the whole service finished after the first successful call.
When reporting a problem, provide the affected number, time, direction, expected behavior and observed result through the provider's secure support route. Include only the information needed and avoid exposing customer conversation content unnecessarily.
Ask the provider what fallback arrangements are available and who can authorize them. Do not assume a completed port can be instantly reversed or that call forwarding will be available in every failure state. A rollback promise needs an actual provider-supported process.
For connectivity problems at the office, the internet-outage checklist can help identify the local issue. Keep that diagnosis separate from a number-routing or provider-side transfer problem.
Compare support as part of the price
Ask which team handles porting before and during the cutover, what hours it is available and how urgent problems are escalated. A general chat service may not have the same access as the team coordinating the transfer.
Compare the cost of the complete configuration: users, numbers, required devices, features, usage and support. Include any overlap period with the old provider and any necessary setup work. The cheapest monthly headline can omit the work needed to preserve the business's existing caller experience.
The vendor-risk checklist helps assess service dependence and exit terms. Ask how numbers can later be transferred out and what account records the business should retain for that purpose.
A worked decision between two offers
Imagine Provider A offers a lower monthly price but has not confirmed one important number's eligibility. Provider B costs more and provides a documented eligibility result, named transfer contact and a clear preparation process. The unresolved number prevents a complete price comparison; it is not a minor footnote to average away.
The business asks A to complete the same checks. If A confirms support and explains a workable cutover, the offers can be compared on equivalent requirements. If it cannot, the business needs another arrangement for that number or a different provider.
Now suppose both can port the number, but only one supports a required function without a separate service. Add that service's cost and responsibility to the other offer. The decision becomes a comparison of complete operating arrangements rather than two seat prices.
Close the old arrangement only after verification
Once the provider confirms completion and the acceptance checks pass, review what remains on the old account. Follow the agreed cancellation or equipment-return process for services no longer needed. Retain confirmation and inspect subsequent bills for the expected change.
Update the internal ownership record with the new provider, authorized administrators, support contacts and the final number inventory. Preserve useful configuration and transfer records through the business's approved retention process.
The purchase is complete when callers can use the intended numbers, staff can operate the new service and the business understands its remaining obligations. A port-complete status is an important milestone; verified communication and a clean administrative handoff make it an operational success.
How we evaluated this page
The guide combines published source information with clearly identified practical examples. It does not claim hands-on product testing.
Read the full review methodologySources and reference notes
Sources were checked on September 3, 2026. Product capabilities and prices can change; verify purchase-critical details directly.
- Twilio: Port Phone Numbers Porting involves eligibility, account information, authorization and provider coordination; destination configuration is a separate preparation task.
- Twilio: Portability Resource A destination provider may distinguish supported numbers, unsupported cases and cases requiring a manual porting route.