The transition
NEC on-premises UC timeline
| Milestone | Date | Practical meaning |
|---|---|---|
| NEC announces phased exit outside Japan | April 15, 2024 | On-premises UC becomes a transition portfolio rather than NEC’s long-term global growth platform. |
| End of new-system and add-on sales window for named systems | December 31, 2024 | Original NEC commercial availability tightened; confirm any expansion through the current channel. |
| Forerunner completes acquisition in the Americas | February 28, 2025 | Forerunner owns and operates the on-premises UC business across the U.S., Canada, and Latin America. |
| Announced software assurance and licensing availability | Through 2030 | A runway for covered Americas customers, not a universal promise that every part and release remains available. |
Sources: NEC’s April 2024 on-premises UC announcement and Forerunner’s February 2025 acquisition release.
Product families
Which NEC systems are in the conversation?
The transition communications name the UNIVERGE SL2100, SV9100, SV9500, and 3C families. Older estates may also include SV8100, SV8300, SV8500, UX5000, Electra Elite, NEAX, or other platforms whose release and hardware dates differ.
SL2100
Common in small and midsize organizations. Inventory CPU revision, cards, licenses, handsets, voicemail, and analog endpoints.
SV9100
Widely deployed across midsize sites. CP10 versus CP20 hardware and software level can materially change the support picture.
SV9500
Enterprise and campus deployments require careful gateway, survivability, attendant, contact center, and integration discovery.
UNIVERGE 3C
Software-based UC has a different architecture and migration profile from the appliance PBXs. Confirm licensing and roadmap directly.
Your actual risk
What the transition means for an NEC customer
- Support provider continuity changed. In the Americas, Forerunner, not NEC’s former regional UC operation, now owns the business and related assets.
- Software availability is not parts availability. A software-assurance commitment does not guarantee every legacy circuit card, handset, power supply, or CPU will remain easy to source.
- Expansion can expose the problem early. Adding a location, user type, recording integration, or modern carrier may be harder than keeping the current dial tone running.
- Security still matters. NEC continues to publish platform advisories; confirm whether your precise build has a supported remediation path.
- Geography changes the answer. The Forerunner transaction covers the Americas. Customers elsewhere must validate their regional arrangement separately.
NEC maintains security advisories that include SL2100, SV9100, and other UNIVERGE platforms.
Use the runway
A practical NEC migration plan
- Confirm entitlement. Ask the current partner to document software version, hardware revision, SWA/licensing status, parts coverage, and the last date each service is contractually available.
- Export configuration. Capture extensions, DIDs, trunks, groups, auto attendants, voicemail, schedules, prompts, and class-of-service rules.
- Find the hidden endpoints. Fax, door phones, elevators, alarms, overhead paging, hospitality phones, modems, and analog devices often determine the design.
- Separate UC and contact-center requirements. A cloud phone seat and a routed agent seat are not interchangeable.
- Compare three architectures. Evaluate UCaaS, a hybrid/local-survivability design, and any supported continuation option on five-year total cost and risk.
- Port in waves. Pilot a site or department, validate emergency calling and inbound routing, then migrate production groups with rollback routing.
Entitlement check
What your NEC estate is actually covered for
Turn “we think we’re supported through 2030” into a written statement from the successor arrangement described above. Coverage runs along four dimensions:
Software release
The SL2100, SV9100, SV9500, or 3C level you actually run, and whether it still has a supported fix path.
Hardware revision
CPU generation, circuit cards, power supplies. Software assurance is not parts availability, ask about your specific cards.
Region
The Forerunner transaction covers the U.S., Canada, and Latin America; sites elsewhere need separate confirmation.
Contract
SWA and licensing status, renewal dates, and what each renewal actually buys. Verbal reassurance is not an entitlement.
Get one document per system, serial number, release, hardware revision, parts coverage, final contractual date for each service, or assume a shorter runway.
Use the time well
A support runway is a planning window, not a reason to wait
“Supported through 2030” tempts owners to shelve the decision, but several costs move against you while you wait.
- Legacy trunk pricing keeps rising. Carriers are retiring copper and PRI services; rates climb every year while SIP alternatives get cheaper.
- Parts get scarcer, not cheaper. As the installed base shrinks, refurbished cards and handsets thin out. Source spares, or leave, before scarcity sets in.
- Analog dependencies take engineering time. Fax, alarms, elevators, and paging need gateway design wherever you land; late starters pay the emergency premium.
- Leverage favors the unhurried buyer. Competing quotes take a quarter to run well and routinely close 15–30% below list.
Replacement options
Replacement paths for a typical NEC estate
Most SL2100 and SV9100 estates are small and midsize: business calling plus an informal contact center living in hunt groups. The natural shortlist handles both together.
8x8
One vendor for phones and contact center, with UCaaS bundling, a common landing spot when both need replacing.
RingCentral RingCX
Entry pricing from roughly $50 per agent, with AI and digital channels bundled.
Dialpad
AI in the seat price and a fast rollout, a fit for smaller teams with light contact-center needs.
Zoom Contact Center
From roughly $26 per agent at list, especially aggressive for organizations already on Zoom meetings.
Larger SV9500 and 3C estates with formal contact centers should also weigh the enterprise suites. Either way, a free estimate narrows the field quickly.
Budget
What replacing an NEC system costs
Cloud contact-center seats run $50–$110 per agent per month, digital-only at $50–$70, full omnichannel at $70–$95, AI and workforce suites at $95–$110, with cloud-calling seats below that; our CCaaS pricing guide breaks the ranges down by provider. One-time costs vary most:
- Implementation. A few thousand dollars for a simple site; five figures for complex routing and multi-site cutovers.
- Number porting. Moving DIDs in waves takes carrier lead time; budget calendar weeks.
- Network readiness. Aging switches without PoE or QoS are often the largest hidden line item.
- Endpoints. Proprietary NEC digital sets don’t follow you; price IP phones, softphones, and headsets.
- Analog gateways. ATAs keep fax, paging, and door phones alive after the PBX is gone.
- Parallel running. A month of double dial tone during cutover is cheap insurance.
FAQ
Quick answers
Is the NEC SL2100 end of life?
It is part of the on-premises portfolio affected by NEC’s exit outside Japan. In the Americas, successor support and licensing arrangements provide a runway, so the exact answer depends on your release, hardware, and contract.
Will our NEC system stop working in 2030?
No automatic shutdown is implied. The cited commitment concerns software assurance and licensing availability; it is a planning boundary, not a power-off date.
Can we reuse NEC phones?
Possibly, but proprietary behavior, firmware, provisioning, and the destination platform determine whether reuse is economical. Prove it in a pilot.
Who supports NEC phone systems in North America now?
Forerunner completed its acquisition of NEC’s on-premises UC business in the Americas in February 2025 and now operates it across the U.S., Canada, and Latin America. Confirm your own coverage in writing with your current partner.
How much does it cost to replace an NEC phone system?
Cloud contact-center seats typically run $50–$110 per agent per month depending on channels and AI; cloud-calling seats price lower. One-time costs, implementation, porting, network upgrades, analog gateways, run from a few thousand dollars to five figures.
Should we replace business phones and the contact center at the same time?
Not necessarily. Many organizations move the contact center first, it carries the most risk and gains the most from modern routing and AI. What matters is a dial plan that lets both systems interoperate during the transition.
Related guides