Migrating from a legacy PBX to the cloud is rarely “just a phone system swap.” It is a business continuity project that touches your numbers, network, emergency calling, customer experience, and the day-to-day workflows your team depends on.

This guide breaks down a practical, low-drama approach to moving from an on-prem PBX to RingCentral RingEX (the platform formerly known as RingCentral MVP).

VIcom typically sees the same pattern in successful migrations: clear discovery, realistic porting timelines, staged rollout, and a cutover plan that treats phones as critical infrastructure, not an “IT nice-to-have.”

What RingEX is (and why naming matters)

If you still hear “RingCentral MVP” in conversations, you are not behind. RingCentral has positioned RingEX as the evolution of MVP, with an emphasis on AI-powered communications and a unified experience.

RingEX is marketed as a unified app for calls, texts, video meetings, messaging, SMS and fax, with 500+ integrations and “99.999% availability” (as RingCentral describes it), plus AI capabilities like call notes and transcriptions.

Phase 1: Discovery (the step that prevents 80% of surprises)

Before you touch a single auto-attendant setting, build a complete inventory of what your PBX actually does today. Most “migration pain” comes from hidden dependencies.

Discovery checklist

• Numbers and call paths

  • Main numbers, direct lines, toll-free numbers

  • Fax numbers (even if “nobody uses it anymore,” it will come up later)

  • Call queues, hunt groups, ring groups

  • After-hours routing, holiday schedules, overflow rules

• Endpoints

  • Desk phones, softphones, conference phones

  • Analog devices: elevators, alarms, paging, door phones, lobby phones, credit card terminals, specialty lines

• People and roles

  • Executives and assistants (special routing rules)

  • Reception/attendant workflows

  • Support and sales teams (queues, recording needs, reporting)

• Compliance and retention

  • Do you record calls?

  • Do you need longer-term retention for legal or regulated workflows?

This is where VIcom adds value early: translating what users think the phone system does into a technical blueprint you can actually implement and test.

Phase 2: Decide your migration strategy

There are three common approaches:

1) Big-bang cutover

Everything ports and flips on one date. This can work for smaller environments with simple call routing, but the blast radius is bigger if anything is missed.

2) Staged migration (recommended for most organizations)

A pilot group moves first, then departments or sites follow. You can validate call quality, user training, and call flow logic before the full cutover.

3) Hybrid transition

You keep the PBX running for a period while RingEX ramps up (common when analog devices or legacy integrations need extra time).

A staged approach is typically the easiest way to keep your business running normally while you modernize.

Phase 3: Network readiness (because cloud calling is a network application)

Legacy PBXs hid a lot of network issues because voice traffic stayed on-prem. With cloud calling, voice quality depends on your LAN, WAN, ISP stability, and configuration discipline.

At a minimum, plan for:

• Adequate bandwidth and stable latency

• QoS configuration where appropriate

• Reliable switching and cabling at desks

• A plan for ISP redundancy if voice uptime is mission-critical

VIcom’s role here is usually assessment and remediation planning so you do not discover network issues on cutover day.

Phase 4: Numbering and porting (the timeline driver)

Porting is often the longest lead-time item. Treat it as its own project inside the project.

What RingCentral says it needs for porting

During order creation, RingCentral collects information like:

• Numbers being ported

• The account number (which may be different from the wireless phone number)

• PIN/passcode (if applicable)

• The service address the numbers are registered under (no PO Boxes)

• Some carriers may require a recent phone bill or other verification info

RingCentral also notes:

• Any toll-free number can be ported, but you should check agreements with your current provider

• For transfers of more than 100 numbers from the same carrier, RingCentral points to project-based porting

• Prepaid cell numbers can be ported with the wireless account number and PIN

Realistic porting durations (set expectations early)

RingCentral partner guidance notes that porting can take up to 30+ business days, and provides typical timelines such as:

• Wireless numbers: 5 business days

• Landlines from major carriers: 7 business days

• Toll-free numbers: 2 business days

• Smaller carriers: 10 to 15 days
  Carrier backlogs can affect these ranges.

They also recommend initiating the port before you cancel service with your current carrier, and cancelling after the number transfer completes (with the note that some transfers may trigger automatic cancellation depending on the carrier).

Porting mistakes that cause delays

• Mismatched service address (especially with multi-site businesses)

• Incorrect account number or missing PIN

• Making changes to the existing carrier account mid-port

• Trying to rush a port date before call flows and user training are ready

VIcom can help by coordinating porting details, building a clean number-to-extension mapping, and sequencing ports around business hours and critical departments.

Phase 5: Emergency calling and dispatchable location (do not leave this to the end)

Emergency calling is one of the biggest differences between traditional telephony and cloud-based systems.

RingCentral’s Emergency Services Policy explains that emergency calling from IP desk phones and softphone apps is different from traditional phones, and it outlines user and administrator responsibilities. It also states you must register the physical address where a line is used and update it if the device or app is moved, because RingCentral relies on this address to route calls to the appropriate responders.

It also warns there are limitations, including events beyond RingCentral’s control such as internet or power outages.

For mobile usage, RingCentral notes emergency calling behavior differs: calls from the smartphone app are routed through the phone’s native dialer, and the smartphone app cannot place emergency calls over Wi‑Fi access.

MLTS compliance: Kari’s Law and RAY BAUM’S Act

If you operate a multi-line telephone system (MLTS), you should understand the U.S. requirements around direct dialing and location.

A U.S. government resource (911.gov) summarizes that:

• Kari’s Law requires MLTS systems to support direct dialing 911, and to send a notification with a callback number and caller location information to a central location (on-site or off-site).

• RAY BAUM’S Act focuses on making “dispatchable location” available with 911 calls, defined as the validated street address plus additional information like suite or apartment details.

RingCentral has also published guidance on Enhanced Nomadic 911, describing automatic location updating for U.S. users at pre-defined locations and explaining that location detection can use network elements like Wi‑Fi access points and IP address ranges, and can prompt users to enter a current address when connecting to a new network.

This is a major area where VIcom support matters: emergency calling is both a technical configuration task and an operational policy task (who maintains locations, how remote workers update addresses, and how you test and document).

Phase 6: Devices and user rollout (avoid hardware chaos)

A smooth rollout requires you to standardize devices and ship them early enough to stage, label, and test.

RingCentral maintains a public list of desk phones compatible with RingCentral and links to setup guides by model.

Practical guidance:

• Standardize on a small set of models per user type (common desk user, reception, conference room)

• Stage phones before deployment when possible

• Plan for headsets and meeting-room audio separately (this is where VIcom’s AV side can complement the UC rollout)

Phase 7: Call flows and “day-one” user experience

Your users judge the project in the first week, not by the admin portal cleanliness, but by what happens when:

• A customer calls the main number

• A receptionist tries to transfer a call

• A manager needs to pull a call recording

• A remote worker places a call and it sounds “off”

Build and test:

• Auto-attendants and business hour schedules

• Call queues and overflow behavior

• Voicemail rules and greetings

• Call recording rules (if required)

• Failover logic during outages (where possible)

Phase 8: Recording, retention, and archiving

If you record calls, confirm retention requirements early.

RingCentral describes call recording in RingEX as supporting on-demand or automatic call recording and notes you can access and download up to 100,000 recordings stored for up to 90 days, along with customizable announcements for consent.

If your organization needs longer retention, RingCentral has promoted archiving options. In a RingCentral blog post about archiving communications data, RingCentral states it retains data only up to 90 days or up to 100,000 call recordings before deletion begins, and it describes RingCentral Archiver as backing up communications data to services like Box, Smarsh, Dropbox, Google Drive, or an SFTP server.

VIcom can help align recording, retention, and archiving with your compliance needs, then make sure the technical configuration matches your policy.

Cutover week: A practical checklist to keep things calm

5 to 10 days before cutover

• Confirm port dates and business-hours plan

• Validate auto-attendant and main number routing in a test environment

• Confirm emergency calling address processes for office and remote users

• Stage devices and confirm user assignments

• Identify VIPs and critical departments for priority support

1 to 2 days before cutover

• Send a short, plain-language “what to expect” email to users

• Set up a help channel (Teams, Slack) and a phone hotline

• Confirm reception and support workflows

Cutover day

• Validate inbound and outbound calling

• Test main line, transfers, and queues

• Validate emergency calling configuration and location process (follow safe internal test procedures)

• Check voicemail and greetings

• Monitor call quality and user trouble tickets

How VIcom fits in (without making this a sales pitch)

A RingCentral migration succeeds when technical work and change management move together.

Where VIcom typically helps most:

• Discovery and requirements mapping (call flows, devices, analog lines)

• Porting coordination and cutover planning

• Emergency calling readiness and documentation

• User rollout planning and training

• Post go-live stabilization, reporting, and ongoing managed support

  We’d love to speak with you about how VIcom can assist your organization in 2026. Simply fill out the form below and we’ll be in contact!