What Is Phone Number Porting?
Phone number porting is the process of transferring an existing phone number from one telecommunications provider to another. Instead of changing numbers when switching carriers or communication platforms, businesses and individuals can keep their current phone numbers while moving service to a new provider.
Number porting is commonly used when organizations migrate from traditional phone systems to cloud communication platforms or VoIP services. By porting their numbers, businesses can upgrade their communication infrastructure without disrupting customer contact information.
Start with a portability check from the receiving provider. Then confirm the required account information, authorization, transfer scope, and cutover plan. Keeping a number does not automatically transfer its routing configuration, message history, or Salesforce integration.
How Phone Number Porting Works
Phone number porting allows a business or individual to move an existing phone number from one telecommunications provider to another without changing the number itself. This process ensures continuity so customers, prospects, and contacts can continue using the same phone number even after the service provider changes.
The porting process typically involves several steps. First, the business submits a port request to the new provider, often including documentation such as a Letter of Authorization (LOA) and a copy of the current phone bill to verify ownership of the number. The new provider then communicates with the current carrier to request the transfer.
Once the request is approved, the number is moved to the new network and activated within the new communication system. Depending on the provider and the type of number being transferred, the process can take anywhere from a few days to several weeks.
Types of Phone Numbers That Can Be Ported
Most common phone numbers can be transferred between providers. Businesses often port numbers when upgrading their communication systems or switching to cloud-based platforms.
Common types of numbers that can be ported include:
- Local phone numbers, which are associated with a specific geographic area code
- Toll-free numbers, such as 800, 888, 877, and other toll-free prefixes
- VoIP numbers, used by cloud communication platforms
- Mobile numbers, which can often be moved between carriers
In most cases, the number must remain active with the current provider until the porting process is complete.
What Phone Numbers Cannot Be Ported?
While most phone numbers are eligible for porting, there are situations where a number cannot be transferred.
Numbers that typically cannot be ported include:
- Numbers that are not assigned to you. You can only port a number you currently own or have active service on.
- Numbers that have been disconnected. If a number has been cancelled or deactivated with the current provider, it is generally no longer eligible for porting.
- Numbers with unverified account authorization. Confirm the account holder and the documentation needed to authorize the transfer. Review any contractual charges separately from technical portability.
- Certain specialty numbers. Numbers provisioned specifically for internal routing, PBX extensions, or proprietary carrier services may not be portable depending on how they were provisioned.
- Numbers in unsupported regions. Porting availability varies by country and region. International numbers may face different regulatory requirements or may not be supported by the receiving carrier.
If you are unsure whether a number can be ported, the most reliable step is to ask your new provider to verify eligibility before initiating the process.
How Do I Check If My Phone Number Can Be Ported?
Before submitting a port request, it is worth confirming that your number is eligible for transfer. Most providers offer a straightforward way to verify this.
Contact your new provider.
The simplest approach is to ask the carrier or platform you are moving to. Ask the receiving provider to check each number and identify any country, number-type, or coverage limitations. Do not treat one eligible number as approval for the whole account.
Check with your current carrier.
Ask the current provider to confirm the account details used for porting, the active status of each number, and any required transfer PIN. Confirm how a partial transfer would affect the services and numbers remaining on the account.
Gather your account information first.
Match the account information to the current provider’s records. For example, Twilio’s US porting guidelines list an authorization letter, matching name and address, a recent bill, account number, and PIN where required. This is a provider-specific example; obtain the receiving provider’s current checklist for your numbers.
Verify the number is still active.
A number must be active with the current provider to be eligible for porting. If there is any risk the number could be cancelled before the port completes, it is important to confirm its status before initiating the transfer.
Can You Still Use Your Number While It Is Being Ported?
Keep the existing service active while the providers process the transfer, unless your porting team gives different instructions for your specific setup. Ask how voice and messaging will behave during cutover and what interruptions are possible. Do not assume every service moves at the same time.
This is one reason why it is important not to cancel service with your current provider before the porting process finishes. Cancelling early can cause the number to be deactivated, which typically makes it ineligible for porting.
Agree on a confirmed transfer window and escalation contact. A requested date is not the same as a confirmed date. Test the new routing after activation before treating the migration as complete; no universal downtime promise applies to every port.
Common Phone Number Porting Mistakes
Porting errors are a frequent source of delays and failed transfers. Understanding the most common mistakes can help organizations avoid disruptions during migration.
Cancelling service before the port is complete.
This is the most damaging mistake. If you close your account with the current provider before the number has successfully transferred, the number may be released and become unavailable. Always wait for confirmation that the port is complete before making any changes to your existing account.
Submitting incorrect account information.
Port requests require an exact match between the information you submit and what the current carrier has on file. Even minor discrepancies — a different billing address, a variation in the account holder name, or a wrong account number — can cause the request to be rejected.
Not having a Letter of Authorization ready.
Most providers require a signed LOA to initiate a port. Delays often occur when this document is missing, incomplete, or does not match the account details on file.
Porting numbers tied to active campaigns without planning ahead.
If a number being ported is actively used in marketing campaigns, customer support lines, or IVR systems, an unexpected delay can disrupt inbound call volume. Build buffer time into migration plans for high-traffic numbers.
Assuming all numbers in an account port together.
In some cases, individual numbers within a multi-line account need to be ported separately. Confirming the scope of a port request with your new provider upfront prevents partial migrations and routing gaps.
Not testing after the port completes.
Once porting is finished, it is worth placing test calls to confirm the number is routing correctly in the new system before relying on it for live customer interactions.
Benefits of Phone Number Porting
Phone number porting allows organizations to modernize their communication infrastructure without disrupting customer contact information.
Maintain Business Continuity
Businesses can switch providers without needing to update marketing materials, websites, or customer records.
Preserve Brand Recognition
Long-standing phone numbers often become part of a company’s brand identity. Porting allows organizations to keep these numbers.
Enable Platform Migration
Porting numbers makes it easier for companies to move from legacy phone systems to cloud communication platforms.
Avoid Customer Confusion
Keeping the same phone number ensures customers and prospects can still reach the business without needing to learn a new contact number.
Phone Number Porting vs Call Forwarding
Phone number porting and call forwarding both allow businesses to maintain continuity when switching phone systems, but they work differently.
| Feature | Phone Number Porting | Call Forwarding |
|---|---|---|
| Provider serving the number | Moves to new provider | Stays with original provider |
| Long-term solution | Yes | Usually temporary |
| What changes | The provider serving the number changes; application setup still needs verification | Calls are redirected to another destination |
| Typical use case | Switching carriers or platforms | Temporary routing |
Number porting is typically used when a business permanently moves its phone service to a new provider, while call forwarding is often used as a temporary workaround during transitions.
Business Number Porting Checklist
Use one row per number, not just one row per supplier. Record the number, country, number type, current provider, account owner, business use, receiving provider, requested date, confirmed date, status, and issue owner. Keep authorization documents in an approved location.
| Check | Question to resolve | Acceptance evidence |
|---|---|---|
| Eligibility and scope | Which numbers are approved, pending, or excluded? | A per-number status confirmed by the receiving provider |
| Account dependencies | What happens to numbers and services staying behind? | A documented partial-port plan where applicable |
| Inbound routing | Which rep, queue, menu, voicemail, and after-hours destination should answer? | Test calls reach each intended destination |
| Outbound identity | Which number should the rep present, and where should callbacks arrive? | A test call and callback follow the agreed path |
| Messaging | What separate setup or approval is required for the intended messaging service? | Supported inbound and outbound message tests pass |
| Salesforce activity | Which record and owner should receive the interaction? | The administrator verifies the expected activity and association |
| Operational ownership | Who can escalate a failed route during cutover? | Named contacts, issue log, and approved contingency plan |
Test the Customer Journey After Activation
Place approved test calls from more than one external network where practical. Check a direct number, a main line, voicemail, after-hours routing, and a callback. Test messaging separately where it is part of the agreed scope. For a Salesforce-connected dialer, inspect the activity record, ownership, disposition, and relationship to the intended lead or contact.
Illustrative failure: a transferred sales number receives calls, but the call lands in the wrong queue and no activity appears on the expected contact. The port may be complete while routing and CRM configuration still need correction. Assign those issues to the appropriate owner instead of cancelling or resubmitting the port without diagnosis.
Do not retire the old configuration solely because a completion notice arrived. Obtain provider confirmation, resolve critical tests, and review any remaining service dependencies. Ask what recovery options exist before cutover; do not assume a transfer can be reversed instantly.
How Long Does Business Number Porting Take?
The answer depends on the provider, number type, country, request size, and whether information needs correction. Ask for the expected processing range, the confirmed activation window, and what would change that window. A bulk port should have a per-number completion record rather than a single account-level checkmark.
For US-specific requirements and example timing, consult Twilio’s current US guidelines; do not treat another provider’s schedule as a Revenue.io commitment. Confirm the plan for your own numbers.
How Revenue.io Supports Phone Number Porting
Revenue.io supports phone number porting, allowing businesses to move their existing phone numbers to or from the platform without changing their public contact information.
If you are considering the RingDNA Communications Hub for Salesforce calling, ask Revenue.io to confirm eligibility, documents, costs, and timing for the actual numbers you plan to transfer. Local and toll-free numbers can have different requirements. Obtain a scoped plan rather than assuming porting is free or immediate.
Review inbound routing, outbound calling, messaging requirements, and Salesforce associations with the implementation team. A number transfer and a working sales workflow are separate acceptance checks.
Plan Your Salesforce Calling Migration
Bring your number inventory, current routing, required countries, and CRM workflow to a Salesforce calling demo. Ask the team to demonstrate a supported inbound call, an outbound call, and the resulting activity record. Review packages and implementation scope before agreeing on the migration.
Moving recordings and activity history is a separate project. Use the guide to sales-data migration to inventory the assets you need to retain.