Hardware administration
Servers and specialist administration take time that could go to operations.
Switch from a legacy dialler
Switch From a Legacy Dialler Without Guesswork
Replacing an established dialler needs more than a new login. Review your agent workflows, integrations, numbers and cutover risks with a staged transition plan.
- Unlimited users
- Open API & integrations
- AI-assisted dialing
- South African telecom expertise
When to switch
When should you consider switching?
Operational signals that make a dialler review worthwhile. Not every legacy deployment has every one of them.
Rigid or unclear licence costs
Costs that are hard to model or that grow with each user or server.
Complex reporting access
Getting call data out takes effort or specialist help.
Integrations that are costly to maintain
Connections to CRMs and tools that break or need frequent attention.
Limited workflow fit
The system shapes how teams work, instead of the other way round.
Support requirements
You need service levels and support scope written down.
Comparison
Legacy platform versus Dialog
Practical differences, while respecting how much legacy installations vary.
| Dimension | Dialog | Typical legacy deployment |
|---|---|---|
| Hosting model | Cloud platform. | Often customer-hosted, though hosted options exist. |
| Administration | Browser-based, with no dialler servers for your team to run. | May need specialist administration, depending on the setup. |
| Agent experience | Browser-based workflows for agents and supervisors. | Varies by product and how it has been customised. |
| API and data access | API, webhooks, call records and data destinations. | Depends on configuration and ownership. |
| Scalability planning | Capacity scoped and agreed in writing. | Depends on your hardware and carrier setup. |
Legacy installations vary widely, so check each row against your own environment. No vendor performance is compared here.
Migration plan
A staged migration process
A path from discovery to a controlled cutover. There is no universal zero-downtime promise: your plan sets the details.
-
1
Audit the current environment
Document what you run today.
-
2
Map features and data
Decide what must be preserved and what can improve.
-
3
Plan carriers and numbers
Confirm routes, DIDs and any porting needs.
-
4
Configure and integrate
Set up campaigns, users and connections.
-
5
Run a pilot
Test with representative traffic and real scenarios.
-
6
Cut over and monitor
Move across in stages and watch results closely.
Readiness inventory
Audit the environment before changing it
Capture what must be preserved and what can be improved. Keep customer-owned backups and get approvals before anything changes.
- Current dialling modes
- Campaigns and lists
- Agents
- Carrier contracts
- DIDs
- Recordings and retention
- CRM connections
- Reporting
- Security policies
- Concurrency
Numbers and data
Protect numbers and data
Clarify where dependencies can affect the project. Number portability, export availability and timing depend on your providers.
Route qualification
Test routes on representative traffic before they carry production calls.
Number inventory and porting where needed
List every number and plan any porting with your provider.
Data export and mapping
Decide which records, recordings and reports move and how they map.
Access control and retention
Confirm who can see what, and how long data is kept.
Pilot
Pilot before the full cutover
Use representative traffic and real operating scenarios to confirm readiness. Success criteria are agreed jointly, with no unsupported uptime promises.
- Agent usability
- Route quality
- Call outcomes
- Campaign behaviour
- Webhooks
- Recording policy
- Reporting accuracy
- Support escalation
Scenarios
Common migration scenarios
Find the closest match to your situation.
Scenario
Customer-managed legacy software
Self-hosted dialler where your team runs servers and administration.
Discuss this scenario → ScenarioHosted cloud platform
A hosted platform that no longer fits how your teams work. Compare workflows first.
Compare platforms → ScenarioHighly customised integration stack
Many CRM and data connections to preserve.
Integrations →Support
Migration proof and support
A typical split of responsibilities. Your written plan confirms who does what.
| Task | Dialog | Your team |
|---|---|---|
| Audit and requirements | Guides the audit and asks the right questions. | Provides access, inventory and approvals. |
| Carrier and number planning | Advises on routes and testing. | Owns carrier contracts and any porting. |
| Configuration and integrations | Configures the platform with you. | Confirms workflows and connected systems. |
| Testing | Supports the pilot. | Agrees success criteria and signs off. |
| Cutover and monitoring | Supports the move and watches the platform. | Approves go-live and manages agents. |
Real migration results and customer examples are added only after approval. None are claimed here.
Frequently asked migration questions
How long does dialler migration take?
It depends on your volume, integrations and approvals, so we agree a timeline after scoping instead of quoting one in advance.
Can we keep our numbers?
It depends on your provider and the numbers involved. Number inventory and any porting needs are reviewed during the audit, and provider timelines apply.
Will call recordings and reports move?
That depends on what your current system lets you export and on your retention rules. Data export and mapping are confirmed during the audit.
Can old and new systems run in parallel?
Often a staged approach with an overlap period is possible, depending on your numbers and integrations. Your plan sets the details.
What training will agents need?
Agents work in a browser, and training needs depend on how different the new workflow is. This is scoped with you before the pilot.
How do we test routes?
Routes are tested on representative traffic before production use, and call detail records show the results. Success criteria are agreed with you first.
What happens if a pilot fails?
You do not cut over. The cause is reviewed, adjustments are made and the pilot is repeated, so the decision stays with you.
Migration consultation
Build a transition plan around your current environment
Share your existing platform, call volume, carrier setup and required integrations. We reply with next steps, not generic promises.
What happens next
- We review your current setup
- You receive a staged migration outline
- Prefer to see the platform first? Book a demo instead
Plan your transition around your real setup
Share your existing platform, call volume, carrier setup and required integrations.