Full number inventory
Main numbers, DDIs, non-geographic numbers and any voice services that still matter to customers or internal workflows.
Migration guide / number porting
Business number porting, without the cutover panic.
A port is not just an admin form. It is a dependency chain involving number ownership, provider records, routing, testing and a controlled go-live.
What happens next
A safer porting timeline.
Before order
Inventory every number
List main numbers, DDIs, fax numbers, special services and any numbers used by alarms or machines. Record the current provider and account details exactly.
Validation
Match losing-provider records
Confirm account name, installation address, postcode, number ranges and any associated services. Mismatched records are a common reason for rejection.
Design
Build the destination first
Configure Yeastar users, queues, auto attendants, opening hours and SIP routing before the number moves.
Pre-cutover
Test without the live number
Validate outbound calling, internal extensions, handsets, apps, failover and any Teams integration before the port date.
Port day
Monitor both sides
Have a named technical owner, test inbound/outbound calls immediately and keep a rollback/escalation path for unexpected routing issues.
After port
Verify the customer journey
Test every advertised number, queue path, voicemail route and out-of-hours behaviour. Then confirm old services can be ceased safely.
Porting times vary by number type and provider. We confirm the expected timescale after checking your current numbers and provider.
Before the order
Most porting problems start with incomplete records.
Before a business number is moved, the current account details need to match the losing provider's records. That can include the legal account name, installation address, postcode, billing reference, main number and any associated ranges or services. If those details do not line up, a port can be rejected before the technical migration even begins.
For SMEs with several sites or long-standing phone estates, the first job is therefore discovery. Old DDIs, fax numbers, alarm lines, special service numbers and numbers attached to broadband or other legacy services should be identified before anyone submits a port request.
Do not treat every number as an isolated line
Number ranges can have dependencies. Moving one number while leaving part of a range behind can create avoidable complications. We map the numbers, current routing and destination call flow together so the business understands what is moving and what is staying.
Porting checklist
What we confirm before cutover.
The exact process varies by provider and number type, but the preparation is consistent: know what you own, where it routes and what the destination should do when the number lands.
Current provider details
Account name, address, billing references and losing-provider information checked before the order is submitted.
New call flow built first
Users, queues, opening hours, voicemail and caller ID configured on the new Yeastar system before the live number moves.
Testing and ownership
A named technical owner tests inbound and outbound calling immediately after the port and knows how to escalate any routing issue.
Talk through your plan
Want us to size the real system?
Send the result and a little context. We’ll map it to Yeastar P-Series, Yealink endpoints, SIP connectivity and any Teams integration you actually need.