migration · published

Migrating to and from RingCentral

Verified 2026-09-25 · 60 sources · tier 2–3

Also known as RingCentral Cloud Connector, RingCentral data export, RingCentral for Microsoft Teams Direct Routing, RingCentral number porting, RingCentral port out, RingCentral project porting.

Migrating telephony and collaboration services to or from RingCentral involves coordinating carrier porting timelines, account details, and data preservation mechanisms 25​43. Depending on whether services are moving to RingCentral, Microsoft Teams, or Cisco Calling Plan, administrators manage local numbers, project-level batches, and archival processes through distinct portals and workflows 22​59​9.

Moving to RingCentral

RingCentral's port-in procedure begins with checking number portability using its portability check tool before the order is submitted 27. A RingCentral port-in order for US local numbers is started in the Admin Portal under Phone System > Phone Numbers > Number Port In, choosing US or US territory Local Number 22. The order asks for the losing carrier's account number (which differs from the phone number), the account PIN or passcode if one exists, the billing telephone number, and whether the account is business or residential 25.

Submitting a local port-in order requires a copy of the latest bill from the current provider that is no more than 30 days old 23. RingCentral recommends including a Customer Service Record (CSR) from the losing carrier with a port-in order to prevent porting issues; it is recommended, not required 26. The address on a RingCentral port-in order must be the location where the numbers are registered with the current provider and cannot be a PO box 28. Service with the current provider must stay active throughout a port into RingCentral 17.

RingCentral's porting FAQ gives 5 to 10 business days for a port: about 5 for most wireless numbers, about 7 for landlines from major carriers, and 10 to 15 from smaller carriers 29. Ported numbers usually go live on RingCentral between 8 and 9 AM Pacific time, Monday to Friday, on the confirmed transfer date 1. RingCentral publishes porting blackout dates for 2026 on which port-ins are not completed, because of holiday staffing and carrier closures 24. To cancel a number transfer request, RingCentral asks for an email to ntd.helpdesk@ringcentral.com giving the phone number, the request details, and the reason 5.

For large orders, RingCentral project porting applies to single-date coordination of 100 or more numbers, and can cover both toll-free and local numbers 41. A RingCentral project port is requested by emailing the completed requirements to project.porting@ringcentral.com rather than through the Admin Portal port-in wizard 39. A RingCentral project port needs a project porting sheet with separate local and toll-free tabs and BTNs listed, a letter of authorization signed and dated within the prior 30 days, and a bill from the previous provider dated within 45 days; CSRs are recommended 35. The requested due date on a RingCentral project port must be no later than 30 days from submission 36. RingCentral states that project porting takes an average of 21 business days and may take 30 to 45 days 37.

In a RingCentral project port that has both local and toll-free numbers, the toll-free submission follows FOC approval of the local order, and RingCentral says coordinating both needs at least 3 weeks 42. For a RingCentral project port, a temporary RingCentral number should be mapped to every number being ported 40. Cancelling a RingCentral project port, or changing its Firm Order Confirmation (FOC) date, should be requested at least 48 hours before the scheduled FOC 38. Numbers can be added to or removed from a RingCentral project port while it is in progress, but RingCentral warns this will most likely delay the original timeline 34.

For user provisioning, a RingCentral blog post updated in March 2025 says admins can bulk-import up to 4,500 users at a time, or 2,000 for best speed 4. In the RingCentral Admin Portal, a device's emergency response location is edited under Settings > Devices & Numbers > Phones: select the device, then Edit Location 15.

Hybrid Deployment and Direct Routing

RingCentral Cloud Connector connects an external or on-premises phone system to RingEX so users on either system can dial each other, which supports a step-by-step move to the cloud 14. The Cloud Connector intro lists it for Standard, Premium, and Ultimate RingEX plans, and it is enabled by contacting RingCentral Support 12. WarmTransfer's reading of the sources is that the Cloud Connector page probably uses legacy plan names, so whether current Core, Advanced, and Ultra plans qualify is not confirmed 13.

For integrations with Microsoft Teams, RingCentral for Microsoft Teams Direct Routing needs a RingEX Core, Advanced, or Ultra plan, and the legacy Standard, Premium, and Ultimate plans are also supported 47. Setting up RingCentral Direct Routing for Teams needs 4 spare Microsoft end-user licences with Teams Phone, used temporarily to verify and create the SBC domains and returned to inventory afterwards 48. Every Teams user moved to RingCentral Direct Routing must have a Microsoft Teams Phone licence 49.

RingCentral says moving a user to Direct Routing for Teams causes little or no downtime, and a user on an active call is moved once the call ends 45. With RingCentral Direct Routing for Teams, voicemail not delivered to Teams voicemail goes to the RingCentral system, and admins can turn off Teams voicemail so voicemail is used only in RingCentral apps 50. When a Direct Routing user is offline in Teams, Teams sends the call to voicemail and tells RingCentral it was answered, so RingCentral call-queue routing does not work as intended 46.

Leaving RingCentral

For a port away from RingCentral, the gaining carrier needs the company name, the service address, and the authorized username (the Super Admin), exactly as they appear on the RingCentral account 31. RingCentral does not issue personalized port-out PINs; if the gaining carrier asks for one, RingCentral says to enter 0000 32. Numbers must be active on RingCentral before a port-out can be requested 30. While a port-out from RingCentral is in progress, the departing numbers are replaced with temporary numbers in the RingCentral account 33. RingCentral states that toll-free numbers cannot be ported to a wireless carrier, only to a landline or VoIP carrier 60.

RingCentral starts truncating call recordings at 90 days or 100,000 recordings in an account, dropping the oldest files first 43. Call recordings deleted in the RingCentral Admin Portal sit in Deleted items for 5 days and can be restored during that time 44. The RingCentral Archiver app in the RingCentral App Gallery backs up RingCentral communication data to Dropbox 3. An API-based RingCentral archive of call logs, call recordings, and the message store needs the ReadCallLog, ReadCallRecording, and ReadMessages app permissions 2. The RingCentral message store export API exports message metadata and attachments for instant messages, fax, and voicemail across all extensions in the account, and only users with the admin role can call it 21. A RingCentral message store export produces a compressed JSON metadata archive and a separate compressed attachments archive (MMS, fax, and voicemail audio), and files over 1 GB are split into several downloads 20. The RingCentral app's message data export must be enabled and requested by a super admin, covers up to 180 days per custom range, and is delivered as a ZIP of JSON files from Export history 18. WarmTransfer's reading of the sources is that an organization leaving RingCentral should export recordings, message store data, and chat history before cancelling, because RingCentral documents only rolling retention limits and the export tools shown run against an active account 16.

Porting to Microsoft Teams Calling Plans

Microsoft's port order process, where Microsoft becomes the service provider of record, applies to Teams Phone with Microsoft Calling Plans 53. A port to Teams Calling Plans is started in the Teams admin center under Voice > Phone numbers > Numbers > Port, by a Teams Telephony, Teams Communications, or Teams Administrator 59. A port request submitted through the new US and Canada Teams porting wizard is acknowledged within 72 business hours 54.

A single Teams port order can include only numbers that share the same service provider, account number, BTN, number type, and service address; anything else needs separate orders 55. Ports of 1,000 or more numbers to Teams Calling Plans must skip the Teams admin center wizard and be submitted manually to the Telephone Number Services service desk 56. The losing provider processes port requests for the same account number 1 at a time; overlapping requests on 1 account are rejected, so batched ports must be sequential 58.

Microsoft says a Teams port typically takes 7 to 14 days and up to 30, needs at least 5 days' lead time in the US and 10 in Canada, and cannot target a date more than 30 calendar days out 57. Numbers dedicated to fax cannot keep faxing after a port to Teams, because Phone System and Calling Plan licences include no fax service; they can only be assigned to users 52. Microsoft advises turning off advanced call-control features such as call hunt or distinctive ring on the numbers with the current provider before porting to Teams 51.

Porting to Cisco Calling Plan

A port into Cisco Calling Plan is started in Control Hub under PSTN & Routing > Numbers: choose Add, pick the location, then Port Numbers Over 9. Porting into Cisco Calling Plan needs a signed Letter of Agency and a bill from the last 30 days, in PNG or PDF, from the current PSTN provider 6.

Cisco's Calling Plan porting guidelines give Simple, Standard, and Project port orders 10 to 35 business days to process and ask for at least 5 business days' lead time, or 2 to 3 weeks for larger ports 7. For Cisco Calling Plan ports in the US and Canada, toll-free numbers must go on separate orders from DID numbers 11. Cisco says numbers on the same losing-carrier account must port at the same time, even if they are on different orders 10. Conversely, for numbers departing Cisco Calling Plan, a port-out request appears in Control Hub under PSTN & Routing > PSTN Orders and is accepted automatically after 1 business day if the admin does nothing 8.

See also

See also Porting numbers to Microsoft Teams. See also Porting numbers to Webex Calling. See also Planning a contact center platform migration.

Applicability

Applies to: RingCentral RingEX, RingCentral Archiver, RingCentral Platform API, RingCentral app (RingEX), RingCentral for Microsoft Teams Direct Routing, RingCentral Cloud Connector, Microsoft Teams Phone with Calling Plans, and Webex Calling with Cisco Calling Plan. Deployments: hybrid and multi-tenant. Sources checked 2026-09-25. RingCentral port-in rules, blackout dates, and device emergency response location configurations specifically apply to the US region 22​24​15. Teams porting lead-time rules and confirmation response times cover the US and Canada 57​54. Cisco Calling Plan separation of toll-free and DID port orders specifically applies to the US and Canada 11.

What remains uncertain

What to enter as account number and BTN when porting away from RingCentral is not covered by the sources below. E911 obligations and dispatchable location setup when moving users onto or off RingCentral is not covered by the sources below. Porting RingCentral numbers to Webex Calling via Local Gateway or Cloud Connected PSTN providers is not covered by the sources below. Porting RingCentral numbers to Teams Direct Routing or Operator Connect instead of Calling Plans is not covered by the sources below. Exiting RingCentral Direct Routing for Teams to native Teams PSTN while keeping users live is not covered by the sources below. What happens to RingCentral recordings, voicemail, and messages after account cancellation is not covered by the sources below. The RingCentral Message Storage and Account Data Retention Policy Knowledge Base article is not covered by the sources below. Migrating RingCentral contact center (RingCX and RingCentral Contact Center) to or from other CCaaS platforms is not covered by the sources below.

See also

Related to

Sources

  1. 1
    Ported numbers usually go live on RingCentral between 8 and 9 AM Pacific time, Monday to Friday, on the confirmed transfer date.
    Submitting your Porting order · FAQs tab, When will my number be transferred? · Checked 2026-09-25
  2. 2
    An API-based RingCentral archive of call logs, call recordings and the message store needs the ReadCallLog, ReadCallRecording and ReadMessages app permissions.
    Archiving Your RingCentral Activity Data · Archiving Your RingCentral Activity Data, API-based archiving section · Checked 2026-09-25
  3. 3
    The RingCentral Archiver app in the RingCentral App Gallery backs up RingCentral communication data to Dropbox.
    Archiving Your RingCentral Activity Data · Archiving Your RingCentral Activity Data, RingCentral Archiver section · Checked 2026-09-25
  4. 4
    A RingCentral blog post updated in March 2025 says admins can bulk-import up to 4,500 users at a time, or 2,000 for best speed.
    New hires? Save time with new bulk onboarding in RingCentral · blog body, opening paragraphs · Checked 2026-09-25
  5. 5
    To cancel a number transfer request, RingCentral asks for an email to ntd.helpdesk@ringcentral.com giving the phone number, the request details and the reason.
    Submitting your Porting order · FAQs tab, How do I cancel my number transfer request? · Checked 2026-09-25
  6. 6
    Porting into Cisco Calling Plan needs a signed Letter of Agency and a bill from the last 30 days, in PNG or PDF, from the current PSTN provider.
    Get Started with the Cisco Calling Plans · Get Started with the Cisco Calling Plan, porting section · Checked 2026-09-25
  7. 7
    Cisco's Calling Plan porting guidelines give Simple, Standard and Project port orders 10 to 35 business days to process and ask for at least five business days' lead time, or two to three weeks for larger ports.
    Cisco Calling Plan number porting guidelines and policies · Cisco Calling Plan number porting guidelines, timelines section · Checked 2026-09-25
  8. 8
    For numbers on Cisco Calling Plan, a port-out request appears in Control Hub under PSTN & Routing > PSTN Orders and is accepted automatically after one business day if the admin does nothing.
    Porting out a PSTN number · Porting out a PSTN number, admin actions · Checked 2026-09-25
  9. 9
    A port into Cisco Calling Plan is started in Control Hub under PSTN & Routing > Numbers: choose Add, pick the location, then Port Numbers Over.
    Get Started with the Cisco Calling Plans · Get Started with the Cisco Calling Plan, porting section · Checked 2026-09-25
  10. 10
    Cisco says numbers on the same losing-carrier account must port at the same time, even if they are on different orders.
    Cisco Calling Plan number porting guidelines and policies · Cisco Calling Plan number porting guidelines, partial port rules · Checked 2026-09-25
  11. 11
    For Cisco Calling Plan ports in the US and Canada, toll-free numbers must go on separate orders from DID numbers.
    Cisco Calling Plan number porting guidelines and policies · Cisco Calling Plan number porting guidelines, toll-free rules · Checked 2026-09-25
  12. 12
    The Cloud Connector intro lists it for Standard, Premium and Ultimate RingEX plans, and it is enabled by contacting RingCentral Support.
    Intro to RingCentral Cloud Connector · Intro to RingCentral Cloud Connector, availability · Checked 2026-09-25
  13. 13
    The Cloud Connector page probably uses legacy plan names, so whether current Core, Advanced and Ultra plans qualify is not confirmed.inferred
    Intro to RingCentral Cloud Connector · Intro to RingCentral Cloud Connector, availability; compared with ringcentral-support-teams-direct-routing-enable prerequisites · Checked 2026-09-25
  14. 14
    RingCentral Cloud Connector connects an external or on-premises phone system to RingEX so users on either system can dial each other, which supports a step-by-step move to the cloud.
    Intro to RingCentral Cloud Connector · Intro to RingCentral Cloud Connector, overview · Checked 2026-09-25
  15. 15
    In the RingCentral Admin Portal, a device's emergency response location is edited under Settings > Devices & Numbers > Phones: select the device, then Edit Location.
    Updating your emergency response location | Admin Portal · Admin Portal tab, updating a device ERL · Checked 2026-09-25
  16. 16
    An organization leaving RingCentral should export recordings, message store data and chat history before cancelling, because RingCentral documents only rolling retention limits and the export tools shown run against an active account.inferred
    Archiving Your RingCentral Activity Data · Archiving Your RingCentral Activity Data, retention section; combined with the export pages · Checked 2026-09-25
  17. 17
    Service with the current provider must stay active throughout a port into RingCentral.
    Submitting your Porting order · FAQs tab, When should I cancel my existing service? · Checked 2026-09-25
  18. 18
    The RingCentral app's message data export must be enabled and requested by a super admin, covers up to 180 days per custom range, and is delivered as a ZIP of JSON files from Export history.
    Exporting message data in the RingCentral app · Exporting message data in the RingCentral app, requesting an export · Checked 2026-09-25
  19. 20
    A RingCentral message store export produces a compressed JSON metadata archive and a separate compressed attachments archive (MMS, fax and voicemail audio), and files over 1 GB are split into several downloads.
    Message Store Exports · Message Store Exports, downloading the archive · Checked 2026-09-25
  20. 21
    The RingCentral message store export API exports message metadata and attachments for instant messages, fax and voicemail across all extensions in the account, and only users with the admin role can call it.
    Message Store Exports · Message Store Exports, introduction · Checked 2026-09-25
  21. 22
    A RingCentral port-in order for US local numbers is started in the Admin Portal under Phone System > Phone Numbers > Number Port In, choosing US or US territory Local Number.
    Submitting your Porting order | Submit order local · Submit order local tab, step list · Checked 2026-09-25
  22. 23
    A RingCentral local port-in order requires a copy of the latest bill from the current provider that is no more than 30 days old.
    Submitting your Porting order | Submit order local · Submit order local tab, documentation step · Checked 2026-09-25
  23. 24
    RingCentral publishes porting blackout dates for 2026 on which port-ins are not completed, because of holiday staffing and carrier closures.
    Submitting your Porting order | Submit order local · Submit order local tab, port-in date / blackout dates note · Checked 2026-09-25
  24. 25
    A RingCentral local port-in order asks for the losing carrier's account number (which differs from the phone number), the account PIN or passcode if one exists, the billing telephone number and whether the account is business or residential.
    Submitting your Porting order | Submit order local · Submit order local tab, carrier account details step · Checked 2026-09-25
  25. 27
    RingCentral's port-in procedure begins with checking number portability using its portability check tool before the order is submitted.
    Submitting your Porting order | Submit order local · Submit order local tab, first step · Checked 2026-09-25
  26. 28
    The address on a RingCentral port-in order must be the location where the numbers are registered with the current provider and cannot be a PO box.
    Submitting your Porting order | Submit order local · Submit order local tab, physical service address step · Checked 2026-09-25
  27. 29
    RingCentral's porting FAQ gives 5 to 10 business days for a port: about five for most wireless numbers, about seven for landlines from major carriers, and 10 to 15 from smaller carriers.
    Submitting your Porting order · FAQs tab, How long will porting take? · Checked 2026-09-25
  28. 30
    Numbers must be active on RingCentral before a port-out can be requested.
    Submitting your Porting order | Port out · Port out tab, requirements · Checked 2026-09-25
  29. 31
    For a port away from RingCentral, the gaining carrier needs the company name, the service address and the authorized username (the Super Admin), exactly as they appear on the RingCentral account.
    Submitting your Porting order | Port out · Port out tab, information for the new carrier · Checked 2026-09-25
  30. 32
    RingCentral does not issue personalized port-out PINs; if the gaining carrier asks for one, RingCentral says to enter 0000.
    Submitting your Porting order | Port out · Port out tab, PIN note · Checked 2026-09-25
  31. 33
    While a port-out from RingCentral is in progress, the departing numbers are replaced with temporary numbers in the RingCentral account.
    Submitting your Porting order | Port out · Port out tab, what happens during transfer · Checked 2026-09-25
  32. 34
    Numbers can be added to or removed from a RingCentral project port while it is in progress, but RingCentral warns this will most likely delay the original timeline.
    Submitting your Porting order | Project port · Project port tab, changes during processing · Checked 2026-09-25
  33. 35
    A RingCentral project port needs a project porting sheet with separate local and toll-free tabs and BTNs listed, a letter of authorization signed and dated within the prior 30 days, and a bill from the previous provider dated within 45 days; CSRs are recommended.
    Submitting your Porting order | Project port · Project port tab, required documents list · Checked 2026-09-25
  34. 36
    The requested due date on a RingCentral project port must be no later than 30 days from submission.
    Submitting your Porting order | Project port · Project port tab, due date requirement · Checked 2026-09-25
  35. 37
    RingCentral states that project porting takes an average of 21 business days and may take 30 to 45 days.
    Submitting your Porting order | Project port · Project port tab, timelines · Checked 2026-09-25
  36. 38
    Cancelling a RingCentral project port, or changing its Firm Order Confirmation (FOC) date, should be requested at least 48 hours before the scheduled FOC.
    Submitting your Porting order | Project port · Project port tab, cancellations and FOC changes · Checked 2026-09-25
  37. 39
    A RingCentral project port is requested by emailing the completed requirements to project.porting@ringcentral.com rather than through the Admin Portal port-in wizard.
    Submitting your Porting order | Project port · Project port tab, submission instructions · Checked 2026-09-25
  38. 40
    For a RingCentral project port, a temporary RingCentral number should be mapped to every number being ported.
    Submitting your Porting order | Project port · Project port tab, temporary numbers · Checked 2026-09-25
  39. 41
    RingCentral project porting applies to single-date coordination of 100 or more numbers, and can cover both toll-free and local numbers.
    Submitting your Porting order | Project port · Project port tab, Project porting qualifications · Checked 2026-09-25
  40. 42
    In a RingCentral project port that has both local and toll-free numbers, the toll-free submission follows FOC approval of the local order, and RingCentral says coordinating both needs at least three weeks.
    Submitting your Porting order | Project port · Project port tab, toll-free coordination · Checked 2026-09-25
  41. 43
    RingCentral starts truncating call recordings at 90 days or 100,000 recordings in an account, dropping the oldest files first.
    Archiving Your RingCentral Activity Data · Archiving Your RingCentral Activity Data, retention section · Checked 2026-09-25
  42. 44
    Call recordings deleted in the RingCentral Admin Portal sit in Deleted items for five days and can be restored during that time.
    Managing call recordings in the Admin Portal · Admin Portal tab, deleting and restoring recordings · Checked 2026-09-25
  43. 45
    RingCentral says moving a user to Direct Routing for Teams causes little or no downtime, and a user on an active call is moved once the call ends.
    RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting · Direct Routing FAQs, downtime question · Checked 2026-09-25
  44. 46
    When a Direct Routing user is offline in Teams, Teams sends the call to voicemail and tells RingCentral it was answered, so RingCentral call-queue routing does not work as intended.
    RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting · Direct Routing FAQs, call queue troubleshooting · Checked 2026-09-25
  45. 47
    RingCentral for Microsoft Teams Direct Routing needs a RingEX Core, Advanced or Ultra plan, and the legacy Standard, Premium and Ultimate plans are also supported.
    Setting up Direct Routing in RingCentral and Microsoft Teams · Enabling direct routing, prerequisites · Checked 2026-09-25
  46. 48
    Setting up RingCentral Direct Routing for Teams needs four spare Microsoft end-user licences with Teams Phone, used temporarily to verify and create the SBC domains and returned to inventory afterwards.
    RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting · Direct Routing FAQs, licensing question · Checked 2026-09-25
  47. 49
    Every Teams user moved to RingCentral Direct Routing must have a Microsoft Teams Phone licence.
    Setting up Direct Routing in RingCentral and Microsoft Teams · Enabling direct routing, prerequisites, Microsoft licences · Checked 2026-09-25
  48. 50
    With RingCentral Direct Routing for Teams, voicemail not delivered to Teams voicemail goes to the RingCentral system, and admins can turn off Teams voicemail so voicemail is used only in RingCentral apps.
    RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting · Direct Routing FAQs, voicemail question · Checked 2026-09-25
  49. 51
    Microsoft advises turning off advanced call-control features such as call hunt or distinctive ring on the numbers with the current provider before porting to Teams.
    What's a port order? - Microsoft Teams · What's a port order?, Common mistakes · Checked 2026-09-25
  50. 52
    Numbers dedicated to fax cannot keep faxing after a port to Teams, because Phone System and Calling Plan licences include no fax service; they can only be assigned to users.
    What's a port order? - Microsoft Teams · What's a port order?, Numbers eligible for porting · Checked 2026-09-25
  51. 53
    Microsoft's port order process, where Microsoft becomes the service provider of record, applies to Teams Phone with Microsoft Calling Plans.
    What's a port order? - Microsoft Teams · What's a port order?, APPLIES TO banner and introduction · Checked 2026-09-25
  52. 54
    A port request submitted through the new US and Canada Teams porting wizard is acknowledged within 72 business hours.
    Transfer phone numbers to Microsoft Teams · Transfer phone numbers to Microsoft Teams, Porting wizard - New (U.S. & Canada), Confirmation · Checked 2026-09-25
  53. 55
    A single Teams port order can include only numbers that share the same service provider, account number, BTN, number type and service address; anything else needs separate orders.
    What's a port order? - Microsoft Teams · What's a port order?, How many port requests do I need? · Checked 2026-09-25
  54. 56
    Ports of 1,000 or more numbers to Teams Calling Plans must skip the Teams admin center wizard and be submitted manually to the Telephone Number Services service desk.
    What's a port order? - Microsoft Teams · What's a port order?, Large port requests · Checked 2026-09-25
  55. 57
    Microsoft says a Teams port typically takes 7 to 14 days and up to 30, needs at least 5 days' lead time in the US and 10 in Canada, and cannot target a date more than 30 calendar days out.
    What's a port order? - Microsoft Teams · What's a port order?, Plan lead-time for port request processing · Checked 2026-09-25
  56. 58
    The losing provider processes port requests for the same account number one at a time; overlapping requests on one account are rejected, so batched ports must be sequential.
    What's a port order? - Microsoft Teams · What's a port order?, How port requests are processed · Checked 2026-09-25
  57. 59
    A port to Teams Calling Plans is started in the Teams admin center under Voice > Phone numbers > Numbers > Port, by a Teams Telephony, Teams Communications or Teams Administrator.
    Transfer phone numbers to Microsoft Teams · Transfer phone numbers to Microsoft Teams, Prerequisites and Launch the port wizard · Checked 2026-09-25
  58. 60
    RingCentral states that toll-free numbers cannot be ported to a wireless carrier, only to a landline or VoIP carrier.
    Submitting your Porting order · FAQs tab, Can I port my Toll-Free number to my wireless carrier? · Checked 2026-09-25

Documents

tier 2 current vendor documentation

Archiving Your RingCentral Activity Data

RingCentral · accessed 2026-09-25

tier 2 current vendor documentation

Cisco Calling Plan number porting guidelines and policies

Cisco Systems (Webex Help Center) · 2025-05-21 · accessed 2026-09-24

tier 2 current vendor documentation

Exporting message data in the RingCentral app

RingCentral · accessed 2026-09-25

tier 2 current vendor documentation

Get Started with the Cisco Calling Plans

Cisco Systems, Inc. (Webex Help Center) · 2026-08-05 · accessed 2026-09-15

tier 2 current vendor documentation

Intro to RingCentral Cloud Connector

RingCentral · accessed 2026-09-25

tier 2 current vendor documentation

Managing call recordings in the Admin Portal

RingCentral · accessed 2026-09-25

tier 2 current vendor documentation

Message Store Exports

RingCentral · accessed 2026-09-25

tier 2 current vendor documentation

Porting out a PSTN number

Cisco · 2025-10-23 · accessed 2026-09-25

tier 2 current vendor documentation

RingCentral for Microsoft Teams Direct Routing FAQs and troubleshooting

RingCentral · accessed 2026-09-25

tier 2 current vendor documentation

Setting up Direct Routing in RingCentral and Microsoft Teams

RingCentral · accessed 2026-09-24

tier 2 current vendor documentation

Submitting your Porting order

RingCentral · accessed 2026-09-24

tier 2 current vendor documentation

Submitting your Porting order | Port out

RingCentral · accessed 2026-09-25

tier 2 current vendor documentation

Submitting your Porting order | Project port

RingCentral · accessed 2026-09-25

tier 2 current vendor documentation

Submitting your Porting order | Submit order local

RingCentral · accessed 2026-09-25

tier 2 current vendor documentation

Transfer phone numbers to Microsoft Teams

Microsoft · 2026-05-28 · accessed 2026-09-21

tier 2 current vendor documentation

Updating your emergency response location | Admin Portal

RingCentral · accessed 2026-09-25

tier 2 current vendor documentation

What's a port order? - Microsoft Teams

Microsoft · 2026-05-28 · accessed 2026-09-24

tier 3 vendor-maintained repositories

New hires? Save time with new bulk onboarding in RingCentral

RingCentral · 2025-03-13 · accessed 2026-09-25

Cite this page

APA

WarmTransfer. (2026, September 25). Migrating to and from RingCentral. WarmTransfer. https://warmtransfer.net/knowledge/ringcentral-migration

BibTeX

@misc{warmtransfer-ringcentral-migration,
  title  = {Migrating to and from RingCentral},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/ringcentral-migration},
  note   = {Verified 2026-09-25}
}