The CallPilot legacy
CallPilot was Nortel’s enterprise voicemail and unified-messaging platform — and it was very good. Saudi enterprises deployed CallPilot through the 1990s and 2000s. The platform integrated with Meridian and CS1000, offered email-integrated voicemail through CallPilot Desktop Messaging, and supported text-to-speech in Arabic and English. Many deployments are still running.
The reason CallPilot deployments are so long-lived is that the platform did its job — voicemail, fax, and unified messaging — without daily operational drama. But the drama is now coming. Hardware aging, dwindling parts, and Avaya’s gradual support windowing are pushing CallPilot toward unavoidable migration. This piece covers the realistic options.
What you’ll lose, what you’ll gain
Migration changes the voicemail experience. What you lose:
- CallPilot Desktop Messaging — the Outlook integration where voicemails appeared as emails with playable attachments. Modern unified-messaging implementations differ in detail; users will retrain.
- Specific CallPilot custom application development (CallPilot Application Builder scripts) — these don’t migrate; equivalents must be rebuilt on the new platform.
- Voicemail prompt customisation specifics — re-recording typically required.
What you gain:
- Mobile-first voicemail — the modern unified-messaging implementations all push voicemails to mobile clients alongside desktop.
- Voicemail-to-text transcription — modern platforms transcribe voicemails to text and email/SMS the transcript.
- Better integration with cloud collaboration suites — Microsoft 365, Google Workspace, Webex.
- Improved spam/robocall filtering on inbound voicemails.
Migration target platforms
Four platforms cover the realistic CallPilot replacement options:
Avaya Messaging (formerly Avaya Aura Messaging) — the Nortel-natural target. Avaya took the CallPilot product line and renamed it. Continues development and integration with Avaya Aura. Best fit if you’re also moving from CS1000/Meridian to Avaya Aura.
Microsoft Exchange Online unified messaging / Cloud Voicemail — Microsoft has consolidated voicemail into Cloud Voicemail (the modern successor to Exchange UM). Voicemails arrive as emails in Outlook, with transcription, mobile sync, and Teams integration. Best fit for organisations already on Microsoft 365.
Cisco Unity Connection — Cisco’s voicemail platform. Strong feature set, deep integration with Cisco UCM, mobile clients. Best fit for organisations also moving to Cisco UCM.
Mitel NuPoint Messenger — Mitel’s voicemail. Strong integration with MiVoice and MX-ONE, hospitality-vertical specialisation. Best fit for organisations also moving to Mitel.
The voicemail platform decision typically follows the PBX platform decision — pick the matched-pair option for tightest integration, unless there’s a specific reason (pre-existing investment, regulatory requirement) to do otherwise.
Voicemail migration mechanics
The mechanical work of moving from CallPilot to a modern platform:
Mailbox export. CallPilot stores messages in proprietary formats. Migration tools exist (Avaya offers tools for Avaya Messaging migration; third-party utilities for cross-platform migrations) but exports are typically converted to standard WAV files plus metadata.
Mailbox provisioning on new platform. Each user’s voicemail box created on the new platform with the same extension or DDI mapping. Distribution lists and group mailboxes recreated.
Message migration (optional). Most organisations don’t migrate historical messages — they retire them with a 90-day grace period for users to retrieve anything important. For organisations with retention obligations, historical messages are exported and archived in compliant storage.
Greeting migration. Personal greetings and auto-attendant greetings re-recorded on the new platform. The new platform’s text-to-speech can substitute where re-recording isn’t practical.
Distribution lists. Manually rebuilt on the new platform.
User retraining and adoption
The biggest user-facing change is the voicemail interface. CallPilot’s spoken menu structure is different from any modern platform’s. Users with 10+ years of CallPilot muscle memory feel the change.
Mitigations: produce a quick-reference guide showing old-vs-new feature codes; deliver brief training sessions per user role; designate champions in each department who help colleagues through the first weeks; use the auto-attendant migration as an opportunity to simplify menu structure.
The compliance angle
Recording retention obligations apply to voicemail in regulated industries. For SAMA-regulated organisations, voicemails to and from customer-service or trader lines may need retention for 5-7 years. The migration must preserve retention records — typically by exporting historical messages to a compliance archive before decommissioning CallPilot.
Verify retention obligations before migration. The mistake of decommissioning CallPilot without preserving retention records is expensive and difficult to reverse.
Cost benchmarks
Voicemail platform migration is typically a sub-project within a larger PBX migration. Standalone voicemail migration is unusual but possible. Indicative ranges for KSA enterprise CallPilot migration:
- 200 mailboxes: SAR 50K-100K migration project
- 500 mailboxes: SAR 80K-180K
- 1000+ mailboxes: SAR 150K-350K
These are migration project costs only; the new voicemail platform license/subscription is separate (or included if migrating to bundled UC platforms like Microsoft 365).
Get help with your CallPilot migration
For a CallPilot migration assessment alongside your broader Nortel migration, book a discovery conversation. We deliver an end-to-end voicemail and PBX migration plan. Pair with unified communications, Microsoft Teams, and VoIP installation services for integrated delivery.