TL;DR
- Migrate the operating record, not just the seats. Call events, recordings, dispositions, CRM identifiers, suppression and callback routing each need an owner.
- Porting a number does not transfer call history. Preserve permitted recordings and reconcile their links before closing the old account.
- Keep the old service active until the receiving provider confirms the cutover. A cancelled source service can complicate porting and interrupt callbacks.
- Budget overlap deliberately. Dual subscriptions, implementation, archive access and exception handling are migration costs, even when the new monthly plan is cheaper.
- Use a pilot cohort and a reconciliation gate. Finish the cutover only when calls, CRM activities and callbacks work with the actual destination configuration.
The assets a seat migration misses
A sales dialer can be replaced without replacing the team's CRM. That does not make the move a simple installation. The dialer owns part of the activity history and part of the relationship with people who call back.
Inventory the assets before negotiating cancellation:
| Asset | Required migration decision | Acceptance evidence |
|---|---|---|
| Telephone numbers | Port, retain with forwarding, or retire | Ownership documents, destination routing and tested inbound calls |
| Call events | Import, preserve in an archive, or retain in the CRM | Count reconciliation and stable event identifiers |
| Recordings and transcripts | Transfer permitted files or keep durable archive access | Playable samples and authorised retention policy |
| Dispositions | Map meaning, not just labels | Old-to-new dictionary with exceptional values |
| CRM associations | Preserve contact, account and owner identifiers | Sample calls attached to the correct records |
| Suppression and preferences | Carry authoritative restrictions forward | Blocked test records stay blocked |
| User and team settings | Recreate permissions, queues and local-time controls | Pilot rep can work without admin-level access |
Export all identifiers you can lawfully retain. A timestamp and phone number alone are weak substitutes for a source call ID when a dispute or duplicate appears months later. Keep source IDs in a migration mapping even if the destination generates new IDs.
Use the RevOps CRM setup playbook to assign field ownership and integration responsibilities. A migration becomes much easier when the team knows which system owns the activity and which owns the commercial record.
Export history before the exit clock starts
Do not assume that an export of call rows includes the audio. It may contain recording URLs whose permissions depend on the account staying active. A successful CSV download is therefore not proof that the history is preserved.
Aircall's current data-access guide distinguishes Workspace access, Dashboard exports and requests for older history. It describes recent-history windows and a separate route for older data, with additional Analytics+ access. That is a practical reason to inspect the history range before announcing a termination date.
For each source, record the exported period, number of rows, recording availability and any request needed for older information. Keep a checksum and an access-controlled archive of permitted files. Recordings can contain personal and sensitive information; the existing retention and access rules still apply during the move.
Reconcile exports by month and calling line. Compare total events and selected dispositions with the source report. A missing month can hide in a plausible aggregate. Distinguish deleted recordings from failed exports and unavailable historical windows.
Check playback from the destination context. A CRM activity can retain a valid-looking URL that now leads to a login screen for a closed subscription. If files are archived separately, make the CRM link point to an authorised durable location rather than pretending the destination dialer owns the old recording.
Do not promise that every historical event can be imported as a native call object. Some providers accept imports differently from integrations that create new activity. An archive plus stable CRM references may be the better supported outcome. Specify that outcome in the contract.
Keep callbacks alive during porting
The number cutover and the application cutover are related projects with different failure modes. A port can complete while the new inbound queue is wrong. New outbound calls can work while callbacks still ring an unattended old queue.
Twilio's porting documentation describes the transfer process and required information. Portability and requirements depend on country and number type. Confirm the exact inventory with the receiving provider; do not infer that a US local number procedure applies to every international or toll-free line.
Prepare an ownership pack: current provider, account details, authorised entity, service address, letter of authorisation where required, and number-specific restrictions. Keep the service active until the provider confirms the appropriate transfer and termination sequence.
Make callback routing part of the acceptance gate. Test the main line, direct rep lines, after-hours rules, voicemail, queues and missed-call notifications. Use realistic CRM associations so the receiving rep can see why the person was called.
If numbers remain with the old carrier, inspect forwarding costs, caller-ID preservation and recording behaviour. Forwarding is a migration design choice, not a free equivalent of a completed port. Retiring a number requires a deliberate callback and customer-notification policy.
Our business calling-platform comparison covers the larger system decision. A sales team's migration should still document the exact inbound behaviour it needs, even when outbound calling drove the purchase.
Map the calling workflow
Translate dispositions by meaning. “Connected” in one system may mean an answered telephone leg; “connected” in another may mean a rep spoke to the prospect. Map the old definitions before combining pre- and post-migration reports.
Keep a separate code for unmapped outcomes. Do not force them into a convenient success category. Preserve the original source value alongside the translated value until reconciliation is complete.
Recreate CRM write rules explicitly: contact and account lookup, owner assignment, task creation, meeting association, retry policy and duplicate prevention. Disconnect an integration in the pilot to establish whether outcomes are queued, alerted and replayed. A migration that increases calls while silently losing CRM events has not passed.
Watch for fields that trigger automation. Importing six months of calls can unintentionally reactivate sequences, change lead scores or create tasks. Historical imports should be tagged and isolated from live-event rules.
Suppression needs an authoritative source and a final check before live activation. A rep's new queue should not resurrect contacts removed in the old system. Shared numbers and account-level restrictions require more than copying a person-level do-not-call field.
Our dialer buying guide owns the parallel versus power choice. The migration should preserve the selected mode and measure its handoff behaviour rather than changing pacing at the same time as data and number routing.
Compare providers on migration obligations
The practical shortlist depends on the destination's operating fit. Use the migration to distinguish four different commitments, rather than asking which vendor says onboarding is easy.
Aircall is relevant when the team needs a business-phone environment with CRM workflows. Its documented history-export controls provide a starting point for an exit or consolidation plan. Confirm plan-specific analytics, older-history access, recording export and destination associations. A familiar integration logo does not establish that all old activities can be recreated.
CloudTalk documents number porting and supports a calling-platform purchase. Its value in a migration is preserving supported numbers while configuring the desired team workflow. Require country-specific port confirmation, inbound test routing and the final billing start date. Do not assume that number transfer includes previous recordings or the source provider's disposition semantics.
JustCall offers number porting as part of its communications environment. Evaluate it when sales and support need the relevant channels and integrations in one purchase. Separate voice-number porting from SMS eligibility and configuration. A number may require additional work before a messaging workflow is ready.
RingCentral publishes a number-transfer process for its business communications service. It fits a broader telephony move more naturally than a decision based solely on maximum outbound attempts. Specify queue, desktop/mobile and recording requirements alongside sales integration.
These sources were checked on 6 October 2026. They establish offered migration mechanisms, not a guarantee for every line. Obtain a scoped subscription and migration offer with seat edition, billing term, number and minute allowances, porting treatment, support and archive retention. The Aircall alternatives guide provides the wider product-fit comparison.
A cutover for twenty sellers
For a hypothetical team of 20 sellers and 30 numbers, use a staged plan rather than moving every line on Friday afternoon.
First, freeze the inventory and export the required history. Identify three pilot users with representative CRM permissions and territories. Include one inbound callback queue, one rep-specific line and one shared campaign line in the pilot design.
Second, configure the new environment with test records. Confirm blocked contacts, local-time rules, identity, recording behaviour and CRM associations. Reconcile ten permitted test calls at the event level, not just the dashboard total.
Third, activate the pilot's authorised workflow. Leave the remaining team on the source configuration until the pilot demonstrates stable routing and activity records. Keep a named owner available for CRM and telephony exceptions.
Fourth, move the remaining cohorts around the confirmed port schedule. Perform a final source export after the last live activity. Reconcile the period that overlaps systems so one call does not appear twice in management reporting.
Finally, close the old service only after the approved retention, callback and billing obligations are satisfied. Record the cutover timestamp. Reports should be able to explain which system created a call on either side of it.
The rollback plan must distinguish an application rollback from a number rollback. Restoring the old login may be straightforward; reversing a completed port is a separate provider process. Maintain an interim routing plan rather than promising an instantaneous carrier reversal.
What the migration really costs
Use this hypothetical US-dollar budget to make the transition cost visible. None of these values is a vendor quote.
| Item | Assumption | Cost |
|---|---|---|
| New subscription | 20 seats at $75 for the first month | $1,500 |
| Old subscription overlap | 20 seats at $60 for one retained month | $1,200 |
| Implementation and reconciliation | 24 hours at $60 | $1,440 |
| Porting/setup allowance | 30 numbers at $10 | $300 |
| Permitted archive storage/access allowance | One transition period | $100 |
| First transition-period cost | Before usage, tax and negotiated extras | $4,540 |
The normal new subscription is $1,500 in this scenario. The migration increment above it is $3,040. One extra month of source overlap adds $1,200. An additional eight hours of exception handling adds $480.
If a different proposed subscription saves $300 a month, a $3,040 migration increment takes roughly 10.1 months to recover through that saving alone. Better operating fit may justify the move sooner, but should be described as operating value rather than invented cash savings.
Check annual notice periods before using monthly overlap arithmetic. A source contract that cannot be reduced mid-term is a remaining commitment, not a one-month migration fee. Retained recording access may also continue beyond the calling cutover.
FAQ
Does porting transfer call recordings and history?
No. Porting changes the service associated with the number. Historical call records and recordings belong to a separate data-transfer or retention process. Export, reconcile and test access before terminating the source account.
Can we keep old recordings in the CRM?
Yes, where your access and retention rights permit it. Verify that links remain playable after cancellation and that authorised users can reach the archive. A URL pointing into an inactive subscription is not durable preservation.
How long should both dialers remain active?
Long enough to complete the agreed port, activity reconciliation and callback acceptance, subject to contract terms. Use those gates to choose the overlap period. A generic seven-day promise ignores historical exports and country-specific porting.
Should we change data providers during the migration?
Usually defer that change until the new calling workflow is stable. Otherwise list quality and platform behaviour become difficult to separate. If the source data is unsafe or unusable, isolate its repair as a named workstream and preserve the comparison limits.
What is the final acceptance test?
An authorised call produces the right disposition and CRM association, its recording behaves as specified, and a callback reaches the correct queue or person. Historical counts reconcile, suppressed contacts remain blocked, and outstanding exceptions have owners. Successful outbound audio alone is insufficient.
