You can bring an existing phone number with you when you move to Revamp365, so the number on your marketing, signs and business cards keeps working. There are two different routes, and which one you take depends entirely on who you are leaving. One takes days and almost no paperwork; the other takes weeks and needs documents that match your current provider's records exactly.
Transfers are handled for you — there is no self-serve transfer screen in the app. Contact support to start one, and someone will open the request and tell you which route your number takes. Buying a brand-new number instead is self-serve: see provision a phone number for SMS and AI Voice.
Before You Do Anything Else
Do not cancel your current account, and do not let the number lapse, until we confirm the number is live on Revamp365. This is the single most common way a transfer fails, and in the worst case it is unrecoverable:
- If the number goes inactive partway through a carrier port, the request is rejected and the process restarts from the beginning.
- If you close an account on a software platform, that platform may release the number back into the general pool. At that point it is gone and cannot be retrieved.
Keep paying your current provider until the switch is confirmed. It is a few extra days of overlap, and it protects the number.
Which Path Applies to You
You do not need to know anything technical — just who sends you the bill today.
| You are currently with | Your route | Typical time |
|---|---|---|
| A software platform: smrtPhone, GoHighLevel, Launch Control, Smarter Contact, Roor or similar | Fast transfer | Days |
| A phone carrier: Verizon, AT&T, a VoIP company — anything that sends you a phone bill | Full port | Up to 4 weeks |
The reason for the split is that most real-estate calling and texting platforms run on the same underlying network Revamp365 uses (Twilio). When that is the case, your number never actually leaves that network — ownership just moves from their account to ours, which skips the entire carrier process. If you are with a genuine carrier, the number has to be physically ported between networks.
If you are not sure which bucket your provider falls into, tell support who you are with and they will check before asking you for anything.
Fast Transfer: Coming From a Software Platform
Because the number stays on the same network, there is no Letter of Authorization, no account PIN, no service address and no copy of your bill. There is no port fee either. Both sides simply have to approve the move, so the only work is getting your current provider to cooperate.
Two Things to Request
Ask your current provider's support team for both of these:
- Their Account SID. This is the identifier of the account your number currently sits in. It begins with
ACfollowed by a long string of letters and numbers. Ask for "the Account SID that holds my number." - Their written approval of the transfer. The network will not move a number between two unrelated accounts without approval from both sides. They can write in to the carrier's support directly, or reply approving it on the request we open with them copied in.
Send both to support and the move is opened the same day.
How to Keep It Moving
- Be direct with your current provider. You are changing providers and you need them to approve a number transfer. It is routine, and the slowest part of this route is almost always their support queue — worth chasing.
- Settle any outstanding balance with them first. An unpaid account is the most common reason a provider declines to release a number.
If your setup happens to run on your own carrier account rather than your provider's, you already control the losing account and can approve the transfer yourself with no waiting at all. Mention it to support and they will confirm which applies.
Full Port: Coming From a Phone Carrier
What to Gather
A genuine port is checked field-by-field against your current carrier's records. A single mismatch — an old address, a slightly different business name — gets the request rejected and adds roughly two weeks. Pull these from your account rather than from memory:
- The number or numbers you want to bring over. Several can go on one request.
- The authorized user's full name, exactly as it appears on the account, including the business name if that is what is on file.
- The service address on file. It must be a real street address — PO Boxes are rejected.
- Your account number with the carrier.
- Your account PIN or passcode, usually four or five digits. Their support team can give it to you.
- A Customer Service Record (CSR). Ask your carrier for this by name. It is their own record of items 2 through 5 — by far the best way to avoid a rejection. If they will not provide one, send your most recent bill instead, dated within the last 30 days and showing the account number, owner name and address.
What Happens After You Submit
Support then sends you a Letter of Authorization to sign, which formally authorizes the transfer — the last thing needed from you.
The request is then validated, passed to the carrier network, and sits with your current carrier for about a week before they approve it and set a cutover date. Your number keeps working throughout; the switch happens on one specific date. There is a one-time port fee on this route; support will confirm the current amount when they open your request.
Texting Switches On After Calling
This applies to both routes and catches people out, so it is worth understanding before you start.
Calling works as soon as your number lands on Revamp365. Texting does not. The A2P 10DLC compliance registration that lets a number send business texts in the US does not transfer between providers — not even on the fast route where the number stays on the same network. It has to be rebuilt under a Revamp365 campaign.
Support starts that registration as soon as your transfer is underway so it is ready and waiting, but expect a gap of roughly a day or two after your number arrives before texting turns on. Attaching a number to a messaging campaign too early can make the registration fail outright, which is why the wait exists.
Nothing is broken if you see calling work and texting not work on day one. For the detail on what that registration involves, see activate texting and the Trust Center checklist and A2P 10DLC registration.
After the Number Arrives
Support configures the number once it lands, which covers inbound calling, inbound texting, and linking it to AI Voice so it can run voice agents. You will be told when it is live.
Check it yourself with three quick tests:
- Call the number from your cell and confirm it rings through.
- Text the number and confirm the message appears in your conversations.
- Once texting is enabled, send an outbound text to your own cell.
If any of the three fails, contact support rather than waiting — it usually means one piece of configuration still needs attaching.
Common Reasons a Transfer Stalls
| What happened | What to do |
|---|---|
| Current provider has not sent their approval (fast route) | Chase their support directly. This is the most common delay. |
| Outstanding balance on the old account | Settle it. Providers decline releases over unpaid accounts. |
| Details do not match the carrier's records (port route) | Ask for a CSR and resubmit with their exact values. |
| Number went inactive or the account was closed | Ask your provider to reinstate it immediately, then tell support. |
| Number is part of a larger block | Your carrier may need to break the block, or all numbers in it must move together. |
| Calling works, texting does not | Expected for a day or two. Beyond that, contact support. |