Inventory the numbers before choosing what to move
Read the guide →Guide preview
Build the transfer scope from verified numbers and purposes, not from a remembered main line.
Confirm scope, authority and dependencies before an order.
Confirm scope, authority and dependencies before an order.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Build the transfer scope from verified numbers and purposes, not from a remembered main line.
Match the authorised requester to the losing provider’s records before signing or submitting anything.
Confirm the number’s registered details and required codes with the provider that holds them.
Country coverage, new-number availability and the ability to transfer your number are different questions.
Check related services and contract boundaries before closing an account after a port.
Use one controlled request and the receiving provider’s current document requirements.
Give administrative responsibility, route configuration and acceptance separate named owners.
Keep estimated lead time, carrier acceptance and confirmed cutover details separate.
Record the purpose and acceptance of a route change so the next administrator can maintain it.