Migration · Phone & SMS
Move Phone Infrastructure Without Breaking Customer Contact
A phone number is printed on vans, signs and listings. Porting, forwarding, SMS, voicemail and routing all have to keep working while the system behind the number changes.
Porting timelines are set by carriers, not by us — so the plan always includes forwarding and fallback until a port completes. SMS also has registration and compliance requirements that are checked upfront.
Call path
Incoming call
Number
Location / routing rule
Team
Fallbackif no answer
Voicemail / escalation
Number inventory
Every number gets a decision before anything is ported.
Illustrative inventory. Ownership — who the carrier account belongs to — is confirmed for each number first.
| Number type | Where it's used | Decision |
|---|---|---|
| Main corporate line | Published everywhere | Port |
| Location line | Google profile, signage | Port |
| Campaign tracking number | Ads and call tracking | Keep |
| Personal / staff number | Used by customers informally | Review |
| Legacy number | Old campaign, low volume | Retire |
| After-hours line | Answering service | Forward |
Cutover checklist
Test the calls nobody plans for.
After-hours calls, missed calls and texts to a location line are where migrations quietly fail. Location and team routing follows the same rules as GoHighLevel lead routing. The overall plan is on GoHighLevel migration.
- 01Ownership confirmed
- 02Routing documented
- 03SMS requirements checked
- 04Forwarding tested
- 05After-hours tested
- 06Missed-call flows tested
- 07Fallback ready
Next step
Plan your phone migration.
Tell us how many numbers you have per location, who holds the carrier accounts and whether you rely on SMS today.