Switching from RingCentral to a Local NYC Provider, What to Expect

By Anthony, Founder of LightningVoIP · Published May 11, 2026

You've already decided to leave RingCentral. The "should I switch" question is settled. What you actually need now is a clear, ordered list of what happens next, the paperwork, the timeline, the cutover, and the gotchas nobody warns you about. Here it is.

Most articles about switching VoIP providers stop at "porting takes 5–7 days." That's the easy part. The actual switch involves a sequence of small, specific tasks across about three weeks. If you miss one, the port gets rejected and the clock restarts. Below is the real sequence, in order, with the decisions and documents you'll need at each step.

Step 1, Audit your current setup before you call anyone

Before you start collecting quotes, spend an hour writing down what you have now. Every quote you get is going to be inaccurate until you can hand the new provider a list of your actual usage. Inventory the following:

• Line count. How many DIDs (direct numbers) and how many user seats? These are not the same, you can have 12 seats sharing 3 main numbers, or 12 users each with a direct line. Pull your last RingCentral bill and count.
• Extensions and users. Who has an extension, what's their name, what number does it ring, do they have a desk phone and/or a mobile softphone?
• IVR menus. The "press 1 for sales" menu, including the recorded greeting text, what each option routes to, and any time-of-day routing rules.
• Hunt groups and ring groups. Sales group, support group, after-hours group, who's in each, in what order, how long it rings each person before failing over.
• Voicemail boxes. Which extensions have voicemail, who currently has the password, are voicemails being emailed to anyone.
• Integrations. CRM call logging, calendar integrations, click-to-dial extensions, webhook destinations, anything that's hooked to RingCentral via API or app marketplace.
• Call recording. If you record calls, which extensions, what's the retention, where are recordings stored, who has access.
• Hardware. What desk phones are in use, what model, when were they bought.

This list is what makes the difference between a good quote and a fictional one. Hand it to any provider you're talking to.

Step 2, Get the all-in cost comparison

Quotes from cloud phone providers are easy to misread. The headline price per seat rarely matches the bill that shows up. When you ask for a quote, demand these line items broken out:

• Monthly per-seat or per-line cost (with tier name)
• Hardware cost, included, leased, purchased outright
• Number porting fees (per number)
• E911 fee
• Regulatory recovery fees and surcharges
• Setup or activation fee
• Voicemail-to-email, call recording, mobile apps, included or add-on
• Long-distance and international minutes, included pool or per-minute
• Integration setup time (CRM, calendar, etc.)
• Contract length and early-termination cost

Run the math out 12 months and 36 months. Compare apples to apples. Anything a provider won't put in writing, treat as an unknown cost.

Step 3, Handle the contract question

If you're under term agreement with RingCentral, you have three real choices:

1. Wait it out. If less than 90 days remain, schedule discovery now and execute cutover on the anniversary date.
2. Pay out the contract. Calculate the early-termination fee against monthly savings. If you break even in 6–12 months and the frustration is ongoing, paying out usually makes sense.
3. Negotiate first. Call RingCentral and tell them you're leaving. They will often discount. If the discount addresses the actual problem, take it. If not, you have a clean reason to go.
4. Ask us about a termination-fee credit. We can credit your LightningVoIP bill over time to offset the RingCentral exit fee. You'd be in a short non-renewing contract with us during the credit period, then month-to-month after. Switching usually pays for itself.

Don't skip this step. Customers who try to leave without knowing what their contract says often find out about termination fees mid-port, which is a bad moment to discover it.

Step 4, The actual porting paperwork

This is where most ports fail on the first attempt, not because anything is broken, but because the paperwork is incomplete. Three things are required to submit a port request:

• Letter of Authorization (LOA). A signed form authorizing your new provider to request the port from RingCentral. Your new provider supplies the form; you sign it. Without an LOA, no carrier will move a number.
• Most recent RingCentral bill (CSR). A copy of your most recent invoice or a Customer Service Record from RingCentral. This proves you own the numbers. The name and service address on the bill must match the name and address on the LOA exactly, including punctuation. "Smith and Sons LLC" vs. "Smith & Sons, LLC" is enough to reject a port.
• Account number and PIN. Your RingCentral account number plus the porting PIN. You may need to log into your RingCentral account and generate a porting PIN, it's a 4–6 digit number specifically for releasing numbers. Without it, the port is rejected.

Get all three before submitting. If anything is off, the carrier rejects the request and the 5–7 day clock starts over.

Step 5, Parallel setup window

Once the LOA is submitted, the port is scheduled, typically 7 business days out for standard US numbers (longer for some toll-free or rural carriers). During this window, your new provider builds the new system in parallel with your existing RingCentral service.

What happens in those 5–7 days:

• New desk phones are provisioned and shipped (or delivered on-site for a NYC install)
• Extensions, IVR menus, hunt groups, and voicemail boxes are configured to match your existing setup
• Integrations are re-pointed at the new system, webhooks, CRM connectors, calendar sync
• A test number is set up so you and one or two staff can place real calls into the new system before cutover
• Voicemail greetings are recorded on the new platform (existing RingCentral voicemails don't transfer)

This is the work week. By the end of it, the new system is fully functional on the test number, and nothing has changed for your customers yet.

Step 6, Cutover day

Port-out windows are short. The actual switch, the moment your phone number stops ringing on RingCentral and starts ringing on the new system, is typically under 15 minutes of perceptible activity.

Schedule cutover for a Tuesday or Wednesday morning. Why: if anything goes sideways, the carrier engineering teams who can fix it are at their desks. Avoid Mondays (carrier backlog from weekend) and Fridays (less escalation availability).

What's happening technically during that 15 minutes:

• The losing carrier (RingCentral's wholesale provider) releases the number
• The winning carrier (your new provider's wholesale carrier, typically Clearfly for multi-line accounts or Skyetel for single-line) accepts the number into their network
• Routing tables update across the national PSTN
• Calls to your number start flowing to your new system

During this window you may see a few calls go to voicemail or get a fast-busy. We test by placing calls from outside numbers every 30 seconds until consistent ringing on the new system is confirmed.

Step 7, Post-cutover, the first week

Once the port is live, there's a short list of follow-up items that need to happen in the first 48 hours:

• Voicemail greetings re-recorded. If staff haven't already done this in the parallel-build week, day-one is the deadline. RingCentral voicemails don't migrate.
• Staff training. Walk-through of the Linkus mobile and desktop apps, how to transfer calls, how to park, how to pick up a parked call. Best done in person for NYC customers.
• Integration re-test. CRM call logging, click-to-dial, calendar sync, verify each integration is recording activity on the new system. Webhook URLs especially need re-pointing.
• IVR tuning. Almost every IVR menu needs a small tweak in the first week, a timing adjustment, an extra option, a greeting re-record. Plan for it.
• Cancel RingCentral. Once the port confirms successful, formally close the RingCentral account. Otherwise you may keep getting billed, RingCentral does not auto-cancel when numbers port out.

Common gotchas

The things that bite people during a port-from-RingCentral, in rough order of frequency:

• Account info on the LOA doesn't match the bill exactly. Punctuation, suite numbers, legal name variations, any mismatch rejects the port.
• Missing porting PIN. RingCentral requires a port-out PIN that you have to generate inside your account. Forgetting it adds days.
• Voicemail data loss. Existing voicemails do not transfer. Download anything important before cutover day.
• Integration webhook URLs left pointing at RingCentral. CRM webhooks, Zapier triggers, custom API connections, all need to be re-pointed. Easy to miss until you notice missing call logs a week later.
• RingCentral retention calls. A retention call within 24–48 hours of port submission is normal. Decide in advance how you want to handle it.
• Weekend cutovers. Tempting (no business impact) but dangerous (carrier engineering is offline). Stick to Tuesday/Wednesday morning.
• Not formally closing the RingCentral account post-cutover. Auto-billing can continue. Get the cancellation in writing.

Frequently asked questions

Related reading

• How to port a business phone number in NYC. what the LOA paperwork and porting window look like day-to-day.
• How to switch business phone providers. the end-to-end migration walkthrough.