Support Center / Switching to Signal
Switching from FluentStream to Signal — Migration Guide
Moving from FluentStream to Signal is a translation exercise, not a relearning one — the platforms share a conceptual vocabulary, and your Polycom and Yealink phones re-provision to Signal with a factory reset. The work is three streams: rebuild configuration, re-point hardware, and port numbers.
Concept mapping
FluentStream / FluentCloud | Signal | Notes |
|---|---|---|
Extension | Extension | Same concept; SIP credentials regenerate |
Devices / Phones (by MAC) | Devices | Same MAC-based provisioning model |
Phone Numbers | Phone Numbers | Port via LNP |
Routes + Time Conditions | Routes + Time Conditions | Same step/schedule model |
Auto Attendant (Key Codes) | Auto Attendant | Rebuild menus; re-record or migrate prompts |
Call Groups / Queues | Call Groups / Queues | Same distinction |
Managed Routes (day/night) | Managed Routes | Same manual toggle concept |
Parking Lots (700s) | Parking Lots | Keep the same slot numbers — zero retraining |
Feature Codes (star codes) | Feature Codes | Recreate your code list identically |
My FluentCloud portal | Signal admin portal | Same admin-owns-it model |
What migrates vs. what rebuilds
- Migrates: your numbers (ported), your phones (factory reset → re-provision), your extension numbering plan, your greetings if you have source audio files.
- Rebuilds: routing logic, menus, voicemail settings — export your FluentCloud configuration first (portal + API) so the rebuild is transcription, not archaeology.
- Request from FluentStream: recording/greeting audio exports and call history you're required to retain. Do this before cancellation.
Hardware reuse
FluentStream-supplied Polycom VVX/Edge and Yealink units are standard hardware: factory reset clears their provisioning lock, and they pick up Signal configuration by MAC. Very old Soundpoint units: see legacy notes.
Cutover sequence
Follow the go-live checklist: build on Signal with temporary numbers → test → port → cancel FluentStream only after a clean billing cycle. Numbers keep working at FluentStream until port completion, so callers never notice.
Related articles
Last reviewed August 6, 2026. Still stuck? Contact Signal Support from your portal — include what you expected, what happened instead, and one example phone number or extension.