> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peerlogic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Port numbers away from Peerlogic

> Transfer your phone numbers from Peerlogic Voice to a new provider: get your Customer Service Record and port-out PINs, and know what Peerlogic can see and do during the port.

Move one or more phone numbers from Peerlogic Voice to a new service provider. Your new provider (the winning provider) starts and owns the transfer. Peerlogic's part is to give you the porting information you need and to review the request when it reaches Peerlogic.

## When to use this

* You are moving one or more phone numbers from Peerlogic to another provider.
* Your new provider asked you for a Customer Service Record (CSR) or a port-out PIN for numbers Peerlogic manages.

## Prerequisites

* An account with your new provider.
* Authorization to make changes to your practice's Peerlogic account.
* The list of numbers you want to transfer.

## Procedure

<Steps>
  <Step title="Ask your new provider to start the transfer">
    Choose your new provider and ask it to transfer the numbers you want to move. Peerlogic doesn't start a port-out and can't control when or how your new provider submits the request.
  </Step>

  <Step title="Request your Customer Service Record from Peerlogic">
    [Contact Peerlogic Support](https://support.peerlogic.com/contact/) and ask for a Customer Service Record for the numbers you want to transfer. Peerlogic provides the CSR to an authorized contact on your account or to your new provider. The CSR includes:

    * Your practice name
    * The complete list of phone numbers Peerlogic manages for you
    * The port-out PIN for each number, when one applies
    * Any other known carrier details needed for those numbers
    * The Peerlogic contact who prepared the record and the date it was prepared

    The CSR may arrive as an email, a spreadsheet, a PDF, a Word document, or Peerlogic's CSR template.
  </Step>

  <Step title="Give the porting information to your new provider">
    Send the CSR details to your new provider. Your new provider submits the port request through its carrier. Submit accurate names, addresses, signatures, and authorization information, even if the carrier checks mainly the phone numbers and port-out PINs.
  </Step>

  <Step title="Wait for Peerlogic to review the request">
    When the request passes your new carrier's first checks, a port-out request becomes visible to Peerlogic. Peerlogic confirms that the numbers are ones it manages for your practice, that you authorized the transfer, and that no unrelated numbers are included. Peerlogic then approves or rejects the request.

    Peerlogic does not reject a valid request to delay or prevent your transfer. If Peerlogic doesn't act within the carrier's review period, the request may be approved automatically.
  </Step>

  <Step title="Wait for the Firm Order Commitment date">
    After approval, the carriers confirm a Firm Order Commitment (FOC) date and time. That is when your numbers transfer to your new provider. Only the confirmed FOC date is the scheduled transfer date.
  </Step>
</Steps>

<Warning>
  At the FOC date and time, your numbers leave Peerlogic. Peerlogic can no longer change their call routing or configuration.
</Warning>

## Exceptions

<AccordionGroup>
  <Accordion title="Peerlogic can't see your port request">
    Peerlogic sees a port-out request only after it reaches Peerlogic's carrier. Peerlogic can't see or change anything that happens between you, your new provider, and your new provider's carrier. If Peerlogic has no request to review, ask your new provider to confirm that:

    * The port request was submitted.
    * The correct phone numbers were included.
    * Their carrier accepted the request.
    * The request was not rejected before it reached Peerlogic's carrier.

    Peerlogic can't investigate, approve, or reject a request that hasn't reached its carrier.
  </Accordion>

  <Accordion title="The port request was rejected">
    When a request reaches Peerlogic, Peerlogic can review the numbers it includes, the carrier status, and any rejection reason from the carrier. If a port-out PIN is involved, the status shown by the carrier is the final word on whether the PIN was accepted. Share the rejection reason with your new provider so it can correct and resubmit the request.
  </Accordion>

  <Accordion title="The transfer is taking longer than expected">
    A review period of about 48 hours applies in some cases, but actual timing varies by carrier, number type, request type, port size, and any errors or missing information. Rely on the confirmed FOC date rather than an estimate.
  </Accordion>

  <Accordion title="Calls or texts don't work after the transfer">
    After the transfer, your new provider controls the numbers. Work with your new provider on inbound call routing, outbound caller ID, text messaging, fax routing, and number assignment. Peerlogic generally can't troubleshoot or change a number after it leaves Peerlogic.
  </Accordion>
</AccordionGroup>

## Verify

Your new provider confirms that the port is complete on the FOC date. Call each transferred number and confirm that it rings through your new provider.

After your numbers transfer, [contact Peerlogic Support](https://support.peerlogic.com/contact/) about any Peerlogic services or billing that remain on your account.

## Related

* [Porting vs. hosting your numbers](/peerlogic-voice/onboarding/porting-vs-hosting)
* [Port your numbers to Peerlogic](/peerlogic-voice/onboarding/port-numbers-to-peerlogic)
* [Contact Peerlogic Support](https://support.peerlogic.com/contact/)


## Related topics

- [Port your numbers to Peerlogic](/peerlogic-voice/onboarding/port-numbers-to-peerlogic.md)
- [Porting vs. hosting your numbers](/peerlogic-voice/onboarding/porting-vs-hosting.md)
- [Register your practice for 10DLC texting](/peerlogic-voice/onboarding/register-for-10dlc-texting.md)
- [NexHealth Synchronizer network requirements](/integrations/ehr-practice-management/nexhealth-synchronizer-network-requirements.md)
- [EHR and PMS integration requirements for partners](/integrations/ehr-practice-management/ehr-pms-integration-requirements.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.