Cloud business number: keep your number and plan a smooth migration

Keep your business number as you move to cloud telephony. Plan number portability, test critical call flows and prepare a smooth transition with Bloom AI.

Sage green handset on an ivory bridge between two blocks, with a cloud at the destination

Your business number is on proposals, email signatures and customers’ phones. Replacing it can feel riskier than keeping a phone system the team has outgrown. Yet moving to a cloud business number does not necessarily mean changing the number customers dial. An eligible number can be ported, and call forwarding may provide a practical starting point.

Continuity comes from preparation. A well-planned migration reduces disruption risk, but cannot promise zero interruption in every circumstance. Bloom AI cloud telephony lets you evaluate the sales workflow before deciding how to move your line.

A cloud business number can keep your existing identity

The number identifies the line a customer calls. Cloud telephony describes how the service is delivered through an application and an Internet connection. These are separate decisions.

Number portability transfers an eligible number to a receiving provider. Forwarding routes incoming calls from an existing line to another destination without moving responsibility for the number. A new number establishes a different telephone identity.

That distinction makes a staged approach possible. A team can try Bloom AI while keeping its current provider, then request porting if the number and configuration qualify. Confirm eligibility before choosing a cutover date.

Three number options with Bloom AI

The Bloom AI calls and messages page describes keeping the existing provider, using a Bloom AI number and requesting a port. Each affects incoming calls, messaging and the existing contract differently.

Option What stays What to verify
Keep the provider and use forwarding Existing line, contract and configured caller identity Forwarding charges, incoming routing and SMS in the phone’s messaging app
Request a port The customer-facing number, if eligible Accepted paperwork, confirmed date and voice and SMS after cutover
Choose a new Bloom AI number An independent existing line if retained Publishing the new number and managing callbacks

With the existing-provider arrangement, forwarding brings incoming calls into Bloom AI and the Message button opens the phone’s messaging app. With a Bloom AI number, SMS lives in the application. Confirm the exact messaging experience for a ported number and the services available for your project.

This gives hesitant teams room to test the working experience before committing to a line transfer.

Keep the current service active until the transfer is coordinated

The CRTC recommends keeping service active and asking the receiving provider to handle the transfer. It notes that some changes involving VoIP may require a different number and that service disruptions, including 9-1-1 disruptions, can occur during a transfer.

Treat “a seamless migration” as an operational plan. Confirm every number’s eligibility, line dependencies and accepted cutover window. A requested date is not a confirmed date.

Keep account changes coordinated while the request is open. The submitted business name and account details need to match the relevant records; discrepancies can delay validation.

Step 1: inventory lines and hidden dependencies

List the main number, direct lines, toll-free numbers and campaign numbers. Record the account holder, provider, reference, purpose and migration owner for each.

Look beyond voice calls. Voicemail, forwarding, fax, intercoms, terminals and alarm systems may rely on a line. Numbers used for authentication codes need separate checks. Voice portability does not establish compatibility for every associated service.

Review bundled contracts as well. Moving one number could affect Internet access or other lines. Ask what changes and what must remain active. A reliable phone system migration starts with a complete account view.

Step 2: prepare the portability request

Get the receiving provider’s exact document list. It may include a recent bill, account details, the account holder’s identity and signed authorization. Use the approved secure channel for these documents.

Specify included numbers, retained numbers and any dependency on a main line. For a multi-line project, agree on transfer order. Avoid assuming a standard completion time: number type, providers and document quality can affect the schedule.

Keep the case reference, operational contact and postponement procedure. Operations should know who can delay cutover if conditions are not ready.

Step 3: test the working environment first

Use a test line or an appropriate forwarding configuration. Include the team’s actual devices, headsets, office networks and mobile connections. A successful call from the project lead’s computer does not validate every working location.

Test an incoming call, outgoing call, customer callback, absence and voicemail. Include transfers and any other essential functions if available in the selected offer. Verify caller identity and SMS separately.

Confirm emergency calling arrangements and limitations for the chosen configuration. Reps need to understand the approved process when working from different locations. Ask support for the relevant instructions; do not place a real emergency call merely to test a phone system.

Step 4: design a workable continuity plan

Choose a quieter window and tell reps how the transition will run. Assign ownership for provider coordination, call testing and internal communication.

Prepare an independent backup destination and a way to tell contacts about it if necessary. Forwarding on the old line may help before cutover, but should not be assumed to remain available after porting. An immediate reversal of a completed port may not be possible.

For B2B sales teams, protect important meetings. Give the rep and customer another way to connect during the planned window. This is practical continuity planning.

Step 5: verify the migration before closing the case

After provider confirmation, call the number from multiple external networks. Check that the right destination rings, outgoing identity is correct and a callback returns to the intended place. Test SMS separately if included.

Check Evidence Owner
Incoming voice Received calls from multiple networks Operations
Outgoing calls and callbacks Verified identity and destination Pilot rep
Messaging and absences Tested customer journey Administrator
Sales follow-through Correct customer and history Sales manager

Do not close the migration after one successful call. Observe the agreed period, resolve anomalies and confirm the status and final billing of old services. Keep any remaining dependencies active.

Use the move to improve selling

The reason to switch VoIP providers is a better working day. Check whether a rep can find the customer, understand the previous promise and act after the conversation. Bloom AI client memory connects calls, messages, notes and commitments.

AI coaching adds feedback adapted to the sales method. The migration can establish a better follow-up and learning routine. Our business call recording guide helps prepare the related purposes and governance.

Compare the full cost, including a retained old plan, possible forwarding charges, licences and numbers. Review Bloom AI pricing and confirm the scope of your migration.

Compare with Bloom AI to choose between keeping your provider, porting or taking a new number, then build a transition that protects customer continuity and improves the calls that follow.

Frequently asked questions

Can a business keep its number when moving to cloud telephony?

Often, subject to number and receiving-provider eligibility. Bloom AI also offers an existing-provider arrangement with incoming call forwarding, so porting is optional.

Are porting and call forwarding the same thing?

No. Porting transfers the number to another provider. Forwarding redirects incoming calls while the line stays with the current provider; contracts and SMS arrangements may remain separate.

Can a migration be guaranteed to have no downtime?

Not for every configuration. Confirm eligibility, the accepted transfer window and a backup plan, then test voice and messaging after cutover.

When should the old line be cancelled?

Do not cancel it before coordinating the transfer with the receiving provider. Confirm affected and retained services, then verify account status after the port.

Accelerate your sales

Request a Bloom AI demo

Discover how Bloom AI conversational AI reduces your sales cycle and frees up your teams.

Sell without limits Step into the future of sales
Book a demo Tell us everything