# Number porting

Easily transfer your existing phone numbers with our reliable Phone Number Porting service. Use the self-service
platform to manage all tasks, schedule port-ins, track progress in real time, and handle bulk transfers or multiple
projects with a seamless transition and minimal downtime.

The porting process typically begins with a portability check, followed by creating a porting request, providing the
required information and documents, and submitting the request for review. After approval, the losing carrier confirms a
porting date and the numbers are transferred to DIDWW.

Porting timelines vary depending on the country, number type, regulatory requirements, and the losing carrier's review
process.

```
        ---
config:
  layout: dagre
---
flowchart LR

   check(("Check portability")) --> create((" &nbsp; Create porting &nbsp; <br>request<br>"))
   create --> fulfill((" &nbsp; Complete &nbsp; <br>&nbsp;&nbsp; requirements &nbsp; &nbsp;"))
   fulfill --> submit(("&nbsp; Submit request &nbsp;"))

   submit --> review(("&nbsp; Porting review &nbsp;"))

   review --> approved(("&nbsp; Approved for &nbsp; <br> &nbsp; porting &nbsp; "))
   approved --> foc(("&nbsp; &nbsp; &nbsp; FOC date  &nbsp; &nbsp; &nbsp; <br> &nbsp; &nbsp; confirmed &nbsp; &nbsp; "))
   foc --> completed["Porting completed"]

   review -.-> changes_required(("&nbsp; &nbsp; &nbsp; Changes &nbsp; &nbsp; &nbsp; <br> &nbsp; &nbsp; required &nbsp; &nbsp; "))
   changes_required --> resubmit(("&nbsp; &nbsp; &nbsp; Resubmit &nbsp; &nbsp; &nbsp; <br> &nbsp; &nbsp; request &nbsp; &nbsp;"))
   resubmit --> review

   review -.-> canceled(("&nbsp; &nbsp; &nbsp; Canceled &nbsp; &nbsp; &nbsp; "))
   canceled --> closed["Porting canceled"]

   check:::customerAction
   create:::customerAction
   fulfill:::customerAction
   submit:::customerAction
   resubmit:::customerAction

   review:::staffAction
   approved:::staffAction
   foc:::staffAction

   changes_required:::status
   canceled:::status
   closed:::status

   completed:::reviewComplete

   classDef customerAction stroke:#38bdf8,fill:#e0f2fe,stroke-width:2px,color:#1f2d3d
   classDef status stroke:#fb923c,fill:#fee2e2,stroke-width:2px,color:#1f2d3d
   classDef staffAction stroke:#facc15,fill:#fef3c7,stroke-width:2px,color:#1f2d3d
   classDef reviewComplete stroke:#2dd4bf,fill:#ccfbf1,stroke-width:2px,color:#1f2d3d
```

## Key concepts

Number porting in DIDWW is organized around three related workspaces:

- **Portability checks** determine whether a phone number can be ported to DIDWW.
- **Porting requests** group one or more phone numbers into a single porting submission.
- **Porting numbers** track the status, milestones, and dates of individual phone numbers within a porting request.

A single porting request can contain multiple porting numbers, and individual numbers may progress through the porting
process independently.

## FOC dates

FOC (Firm Order Commitment) is the confirmed date when a phone number is scheduled to be ported.

FOC dates are assigned to individual porting numbers and can differ between numbers within the same porting request.

For more information, see [View porting date (FOC)](porting-numbers/view-porting-date-foc.html).

## Porting workspaces

**Porting requests**

Create, review, resubmit, and manage porting requests.

[Porting requests](porting-requests/index.html)

**Portability checks**

Check whether phone numbers can be ported before creating a request.

[Portability checks](portability-checks/index.html)

**Porting numbers**

Track individual numbers, statuses, milestones, and FOC dates.

[Porting numbers](porting-numbers/index.html)

**Port-out requests**

Review numbers being transferred away from DIDWW and manage request outcomes.

[Port-out requests](port-out-requests/index.html)

On this page