Your agents have texted the same clients from the same numbers for two years. Those numbers carry history — carriers have watched them send opted-in follow-ups, receive replies, and honor STOP requests. That history is an asset. Rip it up carelessly during a provider switch and you'll spend the next six weeks wondering why your open rates cratered right after you "upgraded."
Full disclosure: I work for ReadySMS, so I have a horse in this race. But the mechanics of a clean port are the same no matter who you land on, and I'd rather you migrate well than fast. The single biggest mistake I see brokerages make is treating a texting migration like swapping an email tool — flip a switch, done. SMS doesn't work that way, because carriers, not your provider, decide whether your messages get delivered.
Here's the port-and-warm sequence I'd run for a real estate team of any size.
Why a sloppy port tanks deliverability
Two things determine whether a text lands: the number's reputation and the 10DLC campaign it's attached to. When you move providers, both are in play.
- The number has an accumulated behavior profile at the carrier level. A number that has sent clean, replied-to traffic is trusted. Port it and immediately blast 20,000 messages from a different sending infrastructure, and you look like a spammer who just bought an aged number — which is exactly the pattern carriers filter.
- The 10DLC campaign — your registered brand and use case — doesn't automatically travel with the number. It has to be re-registered on the new provider. Send from an unregistered number and carriers filter it silently. You won't get bounces. Your texts just quietly stop arriving.
Real estate teams get hit harder than most because their volume is spiky. A new-listing alert or an open-house reminder goes out to a big chunk of the list at once. Spiky volume from a freshly-migrated number is the exact signal that trips throttling.
Step 1: Inventory what you actually have
Before you touch anything, list every number your brokerage sends from, and tag each one:
| Number | Current use | Monthly volume | Keep or retire? |
|---|---|---|---|
| Main office line | Client follow-ups + broadcasts | ~8,000 seg | Keep — port |
| Team lead #1 | 1:1 follow-up | ~2,000 seg | Keep — port |
| Old campaign number | Dead, unused 6 mo | 0 | Retire |
Retire the dead ones now. There's no reputation to preserve on a number that hasn't sent in months, and porting numbers you don't need just adds failure points. You want to port the numbers that carry real, recent, replied-to history — those are the ones worth the effort.
Step 2: Re-register 10DLC before the port completes, not after
This is where the sequence matters most. Your instinct is to port the number first, then set up compliance. Wrong order — that leaves a window where the number is live on the new provider but unregistered, and every message sent in that window degrades reputation.
Register the brand and campaign on the new provider in parallel with the port so the campaign is approved and ready the moment the number lands. We built same-day 10DLC approval into ReadySMS specifically because the old 2-4 week onboarding window is where migrations go to die — you can't leave a brokerage dark for a month. If you want the full anatomy of what compresses A2P onboarding into hours instead of weeks, I wrote that up in the same-day approval timeline breakdown.
A few registration traps specific to real estate:
- File the right use case. A follow-up-heavy team is not the same as a marketing-blast team. Registering marketing traffic as a low-throughput transactional campaign — or vice versa — gets you throttled. See why campaign use-case mismatch silently drops delivery.
- Watch your sample messages. Real estate copy mentioning "cash offer," "financing," or aggressive discounts can trip the carrier SHAFT filters and bounce your registration. If that happens, here's the sample-message rewrite pattern that gets it approved.
Step 3: Run the port in the right order
Number porting is a carrier-side process with real sequencing. Do it out of order and you get downtime — the number goes dark on the old provider before it's live on the new one.
The clean order, in brief:
- Confirm the new provider's brand + campaign are approved (Step 2).
- Submit the port request with matching account details (name, address, account number) — mismatches are the #1 reason ports get rejected.
- Keep the old provider active until the port confirms. Do not cancel early.
- Once the number lands, associate it with the already-approved campaign.
- Test-send to a handful of your own devices across AT&T, Verizon, and T-Mobile before doing anything at volume.
I walk through the full nine-step re-registration order that avoids downtime in this port checklist — it's written for a Twilio move but the sequence is provider-agnostic.
One reality worth setting expectations on: T-Mobile and AT&T treat throughput differently even for the same registered campaign. A number that flies on AT&T can crawl on T-Mobile right after registration until trust builds. That's not a bug in your migration — it's how carrier throughput actually differs post-registration, and it's a big reason warming matters.
Step 4: Warm the volume — don't blast on day one
This is the part everyone skips. A ported number with a fresh campaign on new infrastructure needs to re-earn trust. Warming means ramping volume gradually so carriers see consistent, replied-to, opt-out-honoring behavior instead of a cold spike.
A sane 7-10 day ramp for a brokerage doing ~10,000 segments/month:
| Day | Send target | What to send |
|---|---|---|
| 1-2 | ~5-10% of daily norm | 1:1 agent follow-ups to warm, replying contacts |
| 3-4 | ~25% | Follow-ups + small targeted alerts |
| 5-6 | ~50% | Add segmented broadcasts to engaged lists |
| 7-8 | ~75% | Near-full volume, monitor delivery rates |
| 9-10 | 100% | Full volume including new-listing blasts |
Two principles that make warming actually work:
- Send to your most engaged contacts first. Replies are the strongest positive signal. Start with the clients who text back — recent buyers, active shoppers, hot leads — before you touch the cold end of the list.
- Segment tightly. A 175-character listing alert with an emoji is 3 unicode segments (emoji drops the limit to 70 chars, 67 for multipart). At ReadySMS Standard that's 3 × ($0.02 + $0.0045) = $0.0735 per contact. On a 5,000-contact blast that's ~$368 — and if half that list is dead or unconsented, you're paying to damage the number you just spent two weeks porting. Warming is a good excuse to clean the list.
Step 5: Keep the compliance rails on during the move
Migration is exactly when compliance discipline slips, because everyone's focused on plumbing. Keep the guardrails live from the first test send:
- Automatic STOP handling must carry over so opt-outs from the old system aren't re-messaged. Re-texting someone who opted out is both a reputation hit and a TCPA exposure.
- Quiet-hours enforcement holds sends outside permitted local hours — important when a broker fires off a listing alert at 9pm without thinking about the recipient's time zone.
- Litigator/DNC scrubbing is cheap insurance. A standalone scrub runs $0.005 per contact against known TCPA-litigator and DNC-complainer lists. On that same 5,000-contact list that's $25 to screen out the numbers that carry $500-$1,500-per-text exposure. It doesn't make you lawsuit-proof — compliance is always the sender's responsibility — but it removes the most obvious landmines before a warm-up blast.
If you also run cold outreach on the dialer side, keep it strictly separate — cold-texting property owners has no compliant path under 10DLC, and mixing cold traffic into a warming number will undo everything.
Step 6: Monitor for two weeks, then relax
After you hit full volume, watch delivery rate (not just "sent") and reply rate per carrier for about two weeks. A quiet drop on one carrier usually means a throughput or reputation issue specific to that carrier, not a platform-wide failure. If T-Mobile delivery lags, throttle T-Mobile-bound sends for a few more days and let trust accumulate rather than pushing harder.
For higher-volume brokerages — think teams pushing well past 10,000 segments a month — optional brand vetting ($40 Standard / $100 Enhanced, one-time) raises your trust score and daily throughput ceiling. Most teams don't need it; standard 10DLC ($10/mo brand + $20/mo campaign) covers the majority. Only reach for vetting if throughput is genuinely your bottleneck.
The practical takeaway
A texting migration for a real estate team is really four things done in the right order: inventory and retire dead numbers, re-register 10DLC before the port lands, port without downtime, then warm volume over 7-10 days starting with your most engaged contacts. Skip the warming step and the port itself was pointless — you'll have moved the number and burned the reputation you were trying to protect.
If you're mapping out a move and want the number math for your specific volume, the cost calculator will get you a real figure, and the general Twilio-to-ReadySMS migration playbook covers the platform-side mechanics in more depth. No rush — a migration done a week slower and correctly beats one done fast and filtered.