Practical guide

Find the services that depend on your old phone account

Last materially reviewed 2026-09-28

Quick answerCheck related services and contract boundaries before closing an account after a port.
What to know

Draw the account boundary

List broadband, secondary lines, equipment rental and specialist services that may share the account or contract. This is a discovery exercise, not proof that they will all be affected. Ask the current supplier which services remain, change or cease if the named number moves.

What to know

Confirm specialist dependencies elsewhere

Alarm, lift, fax and payment equipment need their own supplier or qualified professional review. Do not replace those answers with a generic VoIP compatibility statement. Keep life-safety and emergency arrangements outside a routine editorial checklist.

What to know

Separate cancellation decisions

A successful number transfer does not necessarily close every bill, nor does closing an account safely preserve every number. Record an owner and a verified prerequisite for each cancellation. Obtain final billing expectations through the supplier instead of assuming unused time will be refunded.

What to know

A fictional partial move

A business transfers a reception number while keeping another service under the old account. The administrator retains the relevant billing relationship and asks for a revised service schedule. The project is not declared finished merely because the main number rings in the new application.

What to know

Map what might disappear with a cancellation

Start from the service you intend to stop and ask what else depends on that account, line or bundle. Identify broadband, specialist equipment, supplementary numbers and administrative access only where they actually apply. Give each dependency an owner who can confirm its fate. A supplier's statement about voice portability may not describe what happens to the rest of a bundle. Keep “no known dependency” distinct from “checked and none found.” Before cancellation, compare the surviving-service list with the original inventory and any later scope changes. If a dependency is unresolved, retain the relevant service while obtaining competent advice. The purpose of this map is to prevent an unrelated service from being accidentally included in what sounded like a simple number transfer.

Continue when useful

Next: Number inventory

Build the transfer scope from verified numbers and purposes, not from a remembered main line.

Open Number inventory →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. CloudTalk service terms — Merchant documentation · cloudtalk.io · Merchant-controlled · checked 2026-09-28
  2. Zoom Phone numbering policy — Merchant documentation · explore.zoom.us · Merchant-controlled · checked 2026-09-28