Porting a number out of CloudTalk means having your new provider file the port with the underlying carrier that hosts the number, then setting your CloudTalk cancellation to take effect after the port completes. CloudTalk spells this out in its help center: it cannot “push” a number to another provider on its own, but it provides the information you need and may have to give final authorization.
That is CloudTalk’s specificity: your numbers sit with different upstream carriers depending on the country, and the port is decided with them. So you need to know which carrier hosts each number, gather the right code for each country, check that no number falls into the non-portable exceptions, and use the effective-date choice CloudTalk gives you when cancelling. This guide follows CloudTalk’s official documentation as checked on November 5, 2026. The general rules of US porting (LOA, CSR, FCC intervals) are in our business phone number porting guide.
What does CloudTalk say about leaving?
CloudTalk’s help center has a dedicated article on porting numbers away, aimed at account admins. The principle: your new provider manages most of the process, coordinating with CloudTalk’s underlying carrier, the one that technically hosts the number. CloudTalk cannot transfer a number on its own initiative; it provides guidance and information.
The published flow has five steps:
- you start the port with your new provider and sign the Letter of Authorization (LOA) it supplies;
- the new provider sends the LOA to the underlying carrier, not to CloudTalk;
- the carrier checks that the number is active, that the company name and address match the registration, and that any PIN, PAC or migration code is correct;
- CloudTalk is notified and may need to give final authorization;
- the new provider confirms acceptance and the transfer date.
The practical consequence: a rejection usually comes from the underlying carrier, over a mismatch. Getting the right information upfront is how you avoid round trips.
What should you request from CloudTalk?
CloudTalk lists three items to get before you file. We add what the new provider will ask for on its side.
| Item | What CloudTalk says | Why it matters |
|---|---|---|
| Underlying carrier | Ask CloudTalk which carrier hosts the number | That carrier receives and validates the request |
| Country port codes | 4-digit PIN for US mobile, PAC for UK mobile, RIO for French mobile, OKU for Czech numbers, an individual migration code for some Italian numbers, a CVP code for some Portuguese numbers | A wrong or missing code blocks the request |
| Service address (CSR) | Can differ from your billing address | Must match the LOA |
| Exact legal name | Checked by the underlying carrier | Classic rejection after a rename or merger |
| Recent invoice | Requested by most gaining providers | Proof of an active account |
The service address is the trap. If the number was opened at a previous office or by another entity, that is the address the carrier compares against, not your current billing address. Ask CloudTalk support to confirm it in writing, number by number.
US and Canadian toll-free numbers
For a US or Canadian toll-free number, CloudTalk asks you to email porting@cloudtalk.io before submitting the port request, so its team can respond within the carrier’s limited window. Skip that step and the request may lapse. Toll-free numbers move by changing the RespOrg rather than through local number portability, so file them separately from your local DIDs.
Numbers that cannot be ported
CloudTalk lists exceptions due to carrier or country restrictions:
- Colombia: all number types;
- Dominican Republic: local numbers;
- Malaysia: all number types;
- Poland: mobile and toll-free numbers.
If your team uses numbers in these countries, there is no port: plan new numbers with the next provider and a message to your contacts.
The process, step by step
Inventory numbers by country and type
For each CloudTalk number: country, type (local, mobile, toll-free), the user or call flow using it, and where it is published. Flag any number that falls into the exceptions right away.
Export call logs and recordings
Call logs, recordings, statistics: everything that is lost at closure. Start now, not the day before the effective date.
Request the details from support
Underlying carrier, port codes and service address for every number. For North American toll-free numbers, email porting@cloudtalk.io before anything else.
Sign the LOA with your new provider
The new provider sends the request to the underlying carrier. Check that the legal name and address on the LOA are exactly those on the number’s record.
Cut over on the confirmed date
The new provider confirms the date with the underlying carrier. User accounts, number assignments and outbound caller ID are ready beforehand.
Test, then set the cancellation
Call every number from an outside cell phone and check outbound caller ID. Then, under Settings and Billing, cancel with an effective date after the port.
How long does it take, and what does it cost?
Timeline. CloudTalk does not publish a port-out timeline: the date is set by your new provider with the underlying carrier. For US numbers, the FCC intervals apply once the request is accepted: one business day for simple ports, four for non-simple ports, which covers most business ports with several numbers. For numbers in several countries, expect longer: each country is its own file, with its own carrier and code.
Cost. CloudTalk says it charges no fee to port numbers out. The cost comes from the contract:
- the subscription must stay active until the port completes;
- unused subscription time is not refunded;
- CloudTalk’s pricing page states that annual billing comes with a 12-month commitment, while monthly plans can be cancelled anytime; the help center adds that the annual commitment must be fulfilled before any billing cycle change takes effect.
So build the schedule backwards from your renewal date: prepare the file five to six weeks ahead, port one to two weeks ahead, and set the cancellation’s effective date just before renewal.
How do you cancel CloudTalk without breaking the port?
This is where CloudTalk differs from many providers, and it works in your favor: you choose the effective date of the cancellation. The flow in the help center, for admins:
- Dashboard, then Settings, then Billing;
- under “Current plan”, click “Cancel subscription”;
- review the summary and choose the date the cancellation takes effect;
- confirm by typing CANCEL.
Depending on your plan, CloudTalk may first ask you to book an offboarding call. That call does not cancel the account: you must return to Billing and finish the flow, or the account stays active and billable. Before the effective date, you can revoke the cancellation or change the date from the same page. It is the right tool to line up the contract end with the port confirmation, as long as you leave a buffer in case one number is rejected.
After the effective date, reactivation is only possible within 30 days, and only if all invoices are paid. Beyond that, CloudTalk says numbers are released and generally cannot be recovered.
What happens to call history and recordings?
CloudTalk’s cancellation summary is explicit: permanent loss of account data, including call logs, recordings and statistics, and loss of access to phone numbers and users. The help center also notes that when the account closes, number settings such as call flows and voicemail are disabled. Porting moves the number, not the data, and nothing transfers to a new CloudTalk account.
We did not find a bulk recording export method in the CloudTalk help pages we reviewed. Ask support for one alongside the porting details, before you set the effective date. If your CRM was connected to CloudTalk, check what actually synced: a link to a recording hosted by CloudTalk will stop working after closure.
Finally, think about call flows. If a ported number fed a CloudTalk IVR or queue, that routing disappears with the account. Rebuild it at the new provider before cutover, or callers will reach nothing.
On the texting side, CloudTalk’s own porting-in documentation notes that SMS from a ported US number requires A2P 10DLC registration. The same logic applies when you leave: ask your new provider how it will handle 10DLC for the numbers you text from. Our guide to A2P 10DLC and cold texting explains the process.
The CloudTalk-specific traps
- Sending the request “to CloudTalk”. The LOA goes to the underlying carrier. Without its name, your new provider loses time.
- Using the wrong address. The number’s service address can differ from your billing address. That is the one the carrier checks.
- Forgetting the toll-free email. Write to porting@cloudtalk.io before you submit.
- Porting a non-portable number. Colombia, Malaysia, Dominican local numbers, Polish mobile and toll-free: plan replacements.
- Turning off renewal and calling it done. Tell support and set the effective date after the port.
- Letting the 30 days run out. After that, no reactivation and no number recovery.
What if the destination is Skipcall?
Skipcall is an outbound sales phone system: power dialer, parallel dialer up to 4 lines, prerecorded voicemail drop, recording and transcription, SMS, web and mobile apps. Numbers are available in 23 countries: the United States, Canada, the United Kingdom, France, Germany, Spain, Italy, the Netherlands, Belgium, Switzerland, Austria, Luxembourg, Sweden, Finland, Ireland, Portugal, Denmark, Estonia, Romania, Australia, South Africa, Mexico and Brazil. There is no screen in the app for adding a number: any new number is requested from the team through the chat (see our help article on managing phone numbers). Keeping your current number will take a little longer: Skipcall will soon let you port your existing numbers.
What Skipcall does not replace: CloudTalk is also call center software, with call flows, IVR and queues. Skipcall has no IVR, no inbound routing and no queues: each number is assigned to one member, who receives calls, texts and voicemails on it. If your support team runs on CloudTalk, keep it on a call center tool and move only your reps’ lines to Skipcall.
To compare the two tools, read our Skipcall vs CloudTalk comparison, the CloudTalk alternative page and our CloudTalk review. On pricing, the Business VoIP plan starts at $25 per user per month billed annually; details are on the pricing page.
Before choosing which numbers to port, remember that porting does not clean a number’s reputation: a number labeled as spam stays labeled at the new provider. Our guide to caller ID marked as spam helps you decide which ones are worth keeping.
What to remember
At CloudTalk, porting out is settled with the underlying carrier that hosts each number: ask for its name, the country’s port code and the exact service address, then let your new provider file the request. Check that no number falls into the exceptions, and email porting@cloudtalk.io first for North American toll-free numbers. Keep the subscription active, export call logs, recordings and statistics, and use the effective date to cancel after the port, having told support.
Everything else, from FCC intervals to RespOrg changes, is common to all ports and covered in our business phone number porting guide.
Leaving another tool too? Our other port-out guides: leaving Aircall, leaving RingCentral, leaving Dialpad, leaving Google Voice, leaving Ringover, leaving JustCall.
Sources: CloudTalk help center (“Porting your numbers away from CloudTalk”, “How do I cancel my subscription”, “Porting requests and process”) and cloudtalk.io pricing page, checked November 5, 2026.
