Your team is moving the main office to a cloud phone system while another location stays on the existing account. The numbers in the first phase may be clear. The broadband service, specialty lines and billing structure remaining behind can take more investigation.
A partial number port needs an explicit retained-services plan. Give each number and service an owner, decide what should move or remain, and have the providers confirm the account actions. Successful calls on the new platform answer only part of the cutover checklist.
Reconcile carrier records with actual use
Start with the current invoice, the provider’s Customer Service Record where available, and an inventory built with service owners. Compare them. An invoice describes billing, while department staff can help explain what a line does and which business process depends on it.
Assign every entry one of three states: move, retain or unknown. Investigate unknown items before including them in a port or cancellation request. An unfamiliar charge or rarely used number deserves an owner and an explanation before anyone decides it is redundant.
Include location, service purpose, account relationship and the team responsible for validation. Keep the working register in an approved location with appropriate access. Use labels in shared presentation material so real phone numbers, account identifiers and PINs do not circulate unnecessarily.
For a hypothetical phased migration, the reception number might move while a specialty service remains with the existing provider. The register should describe the retained service and the provider-confirmed action needed to preserve it. The project cannot infer that it will survive merely because its number is absent from the port list.
Confirm the billing-number plan
Ask the current provider to identify the billing telephone number or account telephone number, often abbreviated BTN or ATN, and explain how it relates to the services in scope. Do not assume it is the familiar main number or the same thing as the account number.
Zoom’s common port-rejection guidance explains that an incorrect BTN and a mismatched full-versus-partial port indicator can cause rejection. For a partial port that moves the BTN, its guidance describes designating an existing number on the same account as the replacement BTN.
Confirm the applicable process with the providers handling your order. Carrier structures and regional rules vary. Record who will arrange any required replacement, when it must happen and how the retained account will be identified afterward.
Have the billing owner review the expected end state. That person should know which account remains active, which services it will contain and what changes to expect on subsequent invoices. Keep a provider case reference with the approved plan.
Ask explicitly about dependent services
Review broadband, alarm monitoring and other specialty services associated with affected numbers or accounts. Ask service owners and providers to confirm dependencies rather than relying on the porting team to recognize every use from a number list.
Zoom’s porting best practices warn about broadband attached to porting numbers and flag alarm-monitoring dependencies. They also advise keeping current telephone service active during the transfer. These are provider instructions to verify against your own carrier arrangement and geography.
For alarm, elevator, emergency or other safety-related communications, involve the responsible provider and qualified specialist before changing the service. Ask them to define a supported replacement or retention arrangement and its validation procedure. A cloud-phone feature list cannot establish suitability for each specialty device.
Keep unresolved dependencies visible in the project record. If the owner cannot establish what a service supports, assign an investigation and hold the affected change until the responsible parties have a confirmed plan.
Make the submitted scope unambiguous
Review the order as a partial port when numbers will remain. Match authorized account details to the current provider’s records and reconcile the submitted list with the approved register. Have an authorized person confirm the final scope before submission.
Separate the transfer instructions from later cancellation requests. Record exactly what the old provider is expected to retain, including any account action needed for that result. Keep written provider confirmation with the order so the cutover team can refer to the same instructions.
Coordinate other account changes with both providers. Zoom’s rejection guidance identifies pending orders, including some feature or account-detail changes, as a potential obstacle. If another project must change the same account, have the providers agree on the sequence.
Confirm the expected port window, notification route and escalation contacts. Establish what staff should do if only part of the intended result is working. Any contingency needs provider confirmation; the team should not assume that a completed port can be reversed on demand.
A move-and-retain register
Use the same fields on both sides of this register. The labels below are fictional and contain no real customer numbers or account information.
| Move | Retain or investigate |
|---|---|
| Number/service label: Reception calling | Number/service label: Existing specialty service |
| Owner: Department calling owner | Owner: Facilities and responsible service provider |
| Account: Approved internal account reference | Account: Approved retained-account reference |
| Dependency: Identify linked services and number-block constraints | Dependency: Confirm account, circuit and device relationships |
| Provider-confirmed action: Approved partial-port scope and billing-number handling | Provider-confirmed action: Explicit retention or supported migration arrangement |
| Post-change test: Assigned calling workflow and agreed routing checks | Post-change test: Owner-defined validation with the specialty provider where required |
| Status: Confirmed / unknown, investigate | Status: Confirmed / unknown, investigate |
Add the order reference, approval date, confirmed change window and escalation contact to the working copy. Record provider answers as answers, including limitations, instead of replacing them with a general “checked” mark.
Validate the services on both sides
Test the migrated calling workflows with their owners. Check representative inbound and outbound calls, agreed call handling and any other functions included in the acceptance plan. Record results and route exceptions through the established support contacts.
Then validate the retained services independently. Ask each owner to complete the approved test, using the responsible specialist for safety-related systems. A desk-phone call cannot establish that an alarm path or broadband dependency remains healthy.
Keep the old account open until its retained-service plan has been verified and the authorized billing owner has approved any remaining changes. Reconcile subsequent invoices against the intended end state and investigate missing services or unexplained charges.
Bring the move-and-retain register to a VIcom unified communications discussion before submitting the port request. Include the carrier contact, billing owner and specialty-service owners so the migration plan accounts for what stays as carefully as what moves.
Connect with VIcom by filling out the form below.