Feature Gap Matrix
Feature Gap Matrix — Avaya to UCaaS
All 16 tracked features mapped across all 6 platforms we deploy. Updated from execution/feature_mapper.py feature table. For the live data, run:
python3 execution/feature_mapper.py --source avaya --target <platform> --output-format textStatus key
| Status | Meaning |
|---|---|
| Native | Built in, no extra cost |
| Add-on | Available, costs extra |
| Limited | Partial support — see note |
| Workaround | Requires third-party tool or adapter |
| Missing | Not supported |
Migration risk key
| Risk | Meaning |
|---|---|
| 🔴 High | Must resolve before go-live — blocking if missing |
| 🟡 Medium | Plan needed — may need workaround or customer acceptance |
| 🟢 Low | Nice-to-have — won’t block go-live |
Full matrix
| Feature | Risk | RingCentral | 8x8 | Net2Phone | Webex Calling | AireSpring | XTIUM |
|---|---|---|---|---|---|---|---|
| Auto-Attendant / IVR | 🔴 | Native | Native | Native | Native | Native | Native |
| Hunt Groups / Ring Groups | 🔴 | Native | Native | Native | Native | Native | Native |
| Call Recording — On-Demand | 🟡 | Add-on | Native (Pro+) | Add-on | Native | Add-on | Add-on |
| Call Recording — Automatic | 🔴 | Add-on | Native (Pro+) | Add-on | Add-on | Add-on | Add-on |
| Voicemail-to-Email | 🟡 | Native | Native | Native | Native | Native | Native |
| Conference Bridging | 🟢 | Native | Native | Native | Native | Native | Native |
| Paging / Overhead Paging | 🟡 | Workaround¹ | Workaround¹ | Workaround¹ | Workaround¹ | Workaround¹ | Workaround¹ |
| Call Park / Pickup | 🟡 | Native | Native | Limited² | Native | Native | Native |
| BLF (Busy Lamp Field) | 🟡 | Native | Native | Native | Native | Native | Native |
| Analog Device Support (fax, door phones) | 🔴 | Workaround³ | Workaround³ | Workaround³ | Workaround³ | Workaround³ | Workaround³ |
| E911 / Emergency Services | 🔴 | Native | Native | Native | Native | Native | Native |
| Call Center / ACD Queues | 🔴 | Add-on⁴ | Native (X4+) | Missing⁵ | Add-on⁴ | Add-on | Add-on |
| Softphone / Mobile App | 🟢 | Native | Native | Native | Native | Native | Native |
| Desk Phone Compatibility (SIP) | 🟡 | Native⁶ | Native⁶ | Native⁶ | Limited⁷ | Native⁶ | Native⁶ |
| Simultaneous Calls per Seat | 🟡 | Native | Native | Native | Native | Native | Native |
| API / Webhook Integration | 🟢 | Native | Native | Limited | Native | Limited | Limited |
Notes
¹ Paging / Overhead Paging: All platforms require a SIP paging adapter (CyberData or Algo) to connect to existing overhead paging hardware. No platform natively supports analog paging systems. Budget for hardware and configuration time in every migration that includes paging.
² Call Park (Net2Phone): Call park is supported but limited — no orbit/hold monitoring or Visual Park functionality. Receptionist-heavy offices may find this inadequate.
³ Analog Device Support: No UCaaS platform natively supports analog devices (fax machines, door phones, elevator phones). All require an ATA (Grandstream HT802 for fax/standard devices, CyberData for paging and door phones). This is a universal workaround for all platforms.
⁴ Call Center (RingCentral / Webex): Basic call queues (hunt groups with overflow) are included in standard tiers. Full ACD with skills-based routing, supervisor monitoring, agent dashboards, and analytics require the RingCentral Contact Center add-on (separate license) or Webex Contact Center (separate SKU).
⁵ Call Center (Net2Phone): No native ACD. Net2Phone supports basic ring groups only. Do not propose Net2Phone for any customer with a call center or structured queue operation. Escalate to 8x8 or RingCentral Contact Center.
⁶ Desk Phone Compatibility: Most platforms support Poly VVX, Yealink T-series, and Cisco 8800-series phones via BYOD (Bring Your Own Device) using generic SIP configuration. Avaya J-series and 9400/9500 series phones use Avaya-proprietary firmware and will NOT work on any third-party UCaaS platform — they must be replaced.
⁷ Desk Phone Compatibility (Webex Calling): Webex Calling is optimized for Cisco hardware. Third-party SIP phones (Poly, Yealink) can work using “third-party SIP” mode but are not fully supported — some features may not function. Webex is the only platform where recommending Cisco hardware replacement is appropriate.
Implications for platform selection
Use this matrix to validate that the chosen platform can support the customer’s requirements before the proposal is signed:
- Does the customer have a call center? → Use 8x8 (native) or RingCentral + add-on. Rule out Net2Phone.
- Does the customer have paging? → Budget for SIP paging adapter on any platform.
- Does the customer have fax machines? → Budget for ATA (T.38) or eFax migration on any platform.
- Is the customer a federal agency? → RingCentral Government, Webex Government, or Zoom for Government only. Rule out 8x8, Net2Phone, AireSpring, XTIUM.
- Does the customer have Cisco hardware they want to reuse? → Webex Calling is the best fit.
- Is the customer budget-sensitive with a simple single-site setup? → Net2Phone is appropriate if no contact center, no complex IVR.
Generating a live feature map for a specific migration
# Text output (human-readable for customer-facing documents)
python3 execution/feature_mapper.py --source avaya --target ringcentral --output-format text
# Save to migration record in Supabase
python3 execution/feature_mapper.py --source avaya --target 8x8 --migration-id <uuid>
# Supported targets: ringcentral, teams, zoom, 8x8, dialpad, sangomaThe script outputs a formatted table and writes the gap analysis to migrations.metadata["feature_map"] in Supabase when a migration ID is provided.