> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/faqs/network/porting-and-usage-data-faq.md).

# Porting & Usage Data FAQ

Port-in flow basics and CDR availability.

### Quick answers

<details>

<summary>How do port-ins work?</summary>

Port-in is supported as part of the standard onboarding flow (when enabled).

High-level flow:

* customer selects port-in during checkout
* customer enters current carrier details and porting credentials
* Reach validates inputs and submits the port request
* port status is tracked and shown to the customer or agent

Porting timelines depend on donor carrier response, regulatory rules, and data accuracy.

</details>

<details>

<summary>How can CDRs be made available? Is there a lag?</summary>

CDRs (Call Detail Records) are available through reporting and data feeds.

Common access options:

* standard dashboards
* scheduled exports
* secure file transfer (SFTP)
* API access (when enabled)

CDRs are not real-time.

There is a processing delay due to mediation and upstream network processing.

Reach normalizes CDRs.

The brand consumes them for billing, analytics, and compliance needs.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reachplatform.com/faqs/network/porting-and-usage-data-faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.