6 pages
Switching guides
Step-by-step migration from Sendblue, Blooio, Linq Blue, Project Blue or Twilio: contacts, opt-outs, CRM wiring and the first campaign, day by day.
How do you switch iMessage platforms without breaking your outbound?
Four steps in order: export contacts and opt-out list from the old platform, import the suppression list before first send, rewire CRM triggers (native for GoHighLevel, webhook swap for others), and run a parallel window where new campaigns start while old threads finish. The line itself doesn't move; a switch means a new number and new threads, so active conversations shouldn't cross over mid-deal.
From managed iMessage platforms
5 pagesFrom SMS infrastructure
1 pageFrequently asked questions
What actually carries over when you switch iMessage platforms?
Contacts, opt-out list, templates and CRM wiring move; your number and thread history don't, because the line belongs to the old platform. Each guide walks carry-over item by item per vendor.
How do opt-outs transfer without losing compliance history?
Export the suppression list and import it before first send so opt-outs carry over. Skipping this step converts a platform switch into legal exposure.
Will prospects notice the switch?
Yes, new line means new threads. Run both platforms in parallel: finish live threads on the old line while new campaigns start on the new one, so no reply gets dropped.
How long does a migration take?
Days, not weeks. No A2P registration means no carrier queue. White-glove setup stands up the line, imports contacts and lists, rewires the CRM, and the parallel window is optional.
Does Blue Reacher help with the migration?
Yes, white-glove setup handles contact import, suppression list transfer, CRM rewiring and first campaigns. The setup call plans your cutover including the parallel window if needed.