Products · Migration Concierge
Guided migration off Twilio, Sendblue, or your legacy SMS provider
Migration Concierge is a time-boxed engagement, not a product plan. We scope your current setup, map every API call and webhook into senderZ, coordinate number ports with your carrier, run a dual-write cutover, and stay through the 30-day deliverability review. Your engineering team keeps shipping their actual product while we handle the migration.
Who it's for
For teams whose current provider stopped working.
Concierge engagements share a pattern: a deadline, a constraint, and an existing provider that no longer fits.
Teams leaving Twilio
Your Twilio bill is growing faster than your messaging volume. You want iMessage, not another SMS line item.
Sendblue customers hitting caps
Fifty new contacts a day stopped being enough six months ago and the workaround spreadsheet is now critical infrastructure.
Legacy providers sunsetting
Your current vendor is being acquired, deprecated, or repriced, and you have 60 days to land somewhere safer.
What you get
The whole migration. Not the parts you wanted to do.
Live deliverables ship with every engagement. Available-on-request items engage on the scoping call when scope warrants.
Migration scoping call
A 30-minute call with Noa to map your current setup: volume, provider, integrations, consent history, compliance constraints, and go-live deadline.
API mapping doc
Side-by-side mapping of your current provider's endpoints, payloads, and webhook shapes to senderZ. Written by us, not by you.
Phone number porting
If you want to keep your existing numbers, we coordinate the port with the originating carrier. Most US ports finish in 5–10 business days.
Dual-write cutover
During cutover your app writes to both providers. We monitor both streams, compare delivery, and flip the primary read path when parity is stable.
Rollback plan
If anything goes wrong in the first 48 hours, you flip back to your original provider with a single configuration change. Rollback is rehearsed before cutover, not improvised during an incident.
Deliverability review
30 days after cutover we pull your delivery stats, compare them against your pre-migration baseline, and tune phone assignments and warming where we see drift.
Custom Twilio → senderZ adapter library
Available on requestFor teams that cannot change their application code on a short timeline, we write a shim that makes senderZ speak Twilio's request/response shape. Drops your migration effort to a client swap.
SDK migration
We hand you the @senderz/sdk (TypeScript) usage for every Twilio call you currently make. Copy-paste-replace, typed. Python, PHP, and Ruby SDKs are on the Q3 2026 roadmap if your stack is not Node-based — for now we provide a thin REST wrapper.
Dedicated migration manager
Available on requestA single point of contact throughout the engagement — scheduling, status updates, escalation path. Scales to customer request.
How it works
An eight-week timeline. Compressible.
Smaller migrations finish in three weeks. The structure stays the same — scoping, mapping, dual-write, cutover, review.
-
Day 0
Scoping call
30 minutes with Noa. We map your current setup, volume, constraints, and deadline.
-
Week 1
API map
We deliver a side-by-side mapping doc. Your team reviews and approves.
-
Week 2
Number porting kicked off
LOA signed, carrier notified, port scheduled.
-
Week 3
Dual-write live
Your app writes to both providers. We monitor delivery parity.
-
Week 4
Cutover
Primary read path flips to senderZ once parity is stable. Rollback path rehearsed.
-
Week 8
Deliverability review
We pull 30 days of stats, tune phone assignments and warming, and help you decommission the old provider.
How it compares
Concierge vs migrating yourself.
Concierge vs migrating yourself with the senderZ SDK and docs.
| Feature | Migration Concierge | DIY migration |
|---|---|---|
| Typical timeline | 2–8 weeks | 6–16 weeks |
| Zero-downtime path | Dual-write rehearsed | Possible but fragile |
| Cutover risk level | Low — rehearsed rollback | Depends on your team |
| Cost | $2k–$10k engagement | Internal engineering time |
| Success-backed guarantee | Yes — refund if cutover fails | N/A |
DIY migration is a supported path — our docs include a Twilio → senderZ migration guide. Concierge exists for teams who value engineering time more than the fee.
Pricing
One-time engagement. Success-backed.
One-time engagement, quoted by scope. Typical range is $2,000 to $10,000 depending on volume, source-platform complexity, and whether number porting is involved. Includes the 30-day post-cutover deliverability review. Success-backed — if cutover fails and we cannot recover within 48 hours, we refund the engagement fee in full.
FAQ
Frequently asked questions
How long does a typical migration take?
Two to eight weeks depending on volume, source platform complexity, and number-porting requirements. Teams moving from Twilio with no number porting usually finish in under three weeks.
What if I just migrate myself?
Totally reasonable, and about 40 percent of our customers do. We write the migration guide in public docs for exactly that reason. Concierge exists for teams who do not want to burn six weeks of engineering time on an undifferentiated project.
Can you port my existing phone numbers?
Yes. We coordinate the LOA and port request with your originating carrier. Typical port time is 5–10 business days for US numbers. International ports vary.
What happens to my webhooks and integrations?
Your CRM and analytics integrations migrate as part of the scope. We provide a senderZ webhook endpoint that mirrors your current provider's shape so downstream systems need no changes during cutover.
What is the downtime risk?
Near zero during the dual-write phase. Your application sends to both providers simultaneously. We compare delivery outcomes and only flip the primary read path once parity is stable. Rollback is one config change.
Is there a success guarantee?
Yes. If the cutover fails and we cannot recover within 48 hours, we refund the engagement fee in full. To date no engagement has triggered this clause.
Can I keep Twilio as a fallback after cutover?
Yes, and we recommend it for the first 30 days. Dual-provider routing keeps Twilio warm as a fallback while senderZ handles your primary traffic. After 30 days of clean delivery we help you decommission Twilio.
Send us your current setup.
Share the provider you are leaving and your rough volume; we come back with a scope and a fixed quote within three business days.