Migrate from Asterisk to a modern PBX without downtime
Practical cutover plan: trunks, DIDs, IVR, queues and agents. Parallel run, schema rebuild, and how Wivoxa onboarding de-risks Asterisk migrations.
Do not rewrite dialplan on day one
Asterisk dialplans encode years of tribal knowledge. A big-bang rewrite on Friday night is how you lose Monday morning sales calls.
Safer pattern: new platform in parallel → port or dual-route one DID at a time → keep the old box as fallback until metrics look right.
Migration checklist
- Inventory trunks, DIDs, ring groups, queues, time conditions, recordings retention
- Map agents and skills; decide WebRTC vs desk phones
- Rebuild IVR as visual schemas (menus, calendars, queues, voicemail)
- Recreate outbound routes and caller-ID rules
- Load CRM webhooks / click-to-call if you use them
- Train supervisors on wallboard and listen modes before cutover
What changes for operators
Agents open a browser tab instead of a softphone profile per PC. Statuses (ready/pause), auto-answer and transfers live in the same UI as history. Supervisors get a live wallboard instead of CLI “show queues”.
Wivoxa’s role
Remote install, trunk connect, schema build and training are a one-off onboarding package. Free self-install remains available if your team prefers to migrate in-house using the documentation.
Wivoxa — self-hosted PBX and contact center