Migrating from Project Blue to Blue Reacher

The short answer

Migrate from Project Blue: keep contacts, opt-outs, templates, CRM workflows. Monthly, one line: $300 vs $249, $4,100 vs $3,437 year one. Annual: $49 diff.

$249 per line per month, published No A2P registration required 50 opted-in / 30 cold new contacts a day, unlimited replies

Key takeaways

  • Most setup survives. Contacts, fields, suppression lists, templates are yours.
  • Opt-outs carry over fully. Each opted-out number loads as suppression before contacts land.
  • Migration runs in fixed order, sized during activation.
  • Monthly one line: $4,100 year one vs $3,437.

What changes

The channel and the number. Blue bubbles from a dedicated line instead of green ones, with RCS then SMS behind it.

What stays

Your CRM, your funnel stages, your sequences and your contact history. Replies, delivery states and opt-outs post back to the same records.

What we do

The line, the area code, the integration, the workflows and the first scripts. Setup is white-glove; you run a parallel window and cut over when it is beating what you had.

What the bill is made of

What the bill is made ofA carrier SMS bill stacks six separate line items: per number, brand registration, campaign registration, per-campaign monthly charges, carrier pass-through fees, and metered per-segment messaging. An iMessage line is one flat charge.Per-message, metered per segmenta long message bills as severalCarrier pass-through feesrose across all four major carriers in 2026Per-campaign monthly chargesrecurring, after launchCampaign registrationper campaign, plus monthly carrier chargesBrand registrationone-time, before you can send anythingPer number, monthly$2 to $10 per numberCarrier SMSBlue ReacherOne line, one priceUnlimited messages (50 opted-in / 30 cold new contacts a day), 3x the resultsMost teams sending inside a week$449 setup, waived on annual
A carrier SMS bill stacks six separate line items: per number, brand registration, campaign registration, per-campaign monthly charges, carrier pass-through fees, and metered per-segment messaging. An iMessage line is one flat charge.

Why do teams move from Project Blue to Blue Reacher?

Price matters on monthly billing only. Project Blue: $300/line/mo plus $500 setup. Blue Reacher: $249 plus $449 white-glove (waived annual). Year one: $4,100 vs $3,437.

  • Channel scope. Project Blue: iMessage, SMS. Blue Reacher: full funnel with RCS/SMS fallback covering lead, reactivation, qualification, confirmations, reminders, recovery, post-call, onboarding, retention, referrals.
  • Public signals cut both ways. Project Blue blog stopped April 2026, no sitemap, no G2/Capterra/Trustpilot. Sendblue 4.8 on G2 (65 reviews).
  • A quiet vendor blog on its own, while your support tickets still get answered on time.
  • Reply rates you dislike that trace back to your list or your copy. Both of those follow you to any platform.
  • A lower headline price while you sit on Project Blue's annual plan, where the real difference is $49 a year.

What do you keep and what changes?

Most setup survives. Contacts, fields, suppression lists, templates are yours. Sending line, pricing, automation all change.

  • Your Blue Reacher line provisioned during activation. Replies to old Project Blue number keep coming there. Parallel section exists for this.

Contacts and custom fields

Keep or change
Keep
Notes
Exported from Project Blue, imported during activation

Opt-out and suppression list

Keep or change
Keep
Notes
Loaded first, before any contact record, and count-checked

Message templates

Keep or change
Keep
Notes
Merge fields get pointed at your imported data

Conversation history

Keep or change
Export it
Notes
Stays behind on Project Blue, so pull it before you cancel

Sending line

Keep or change
Changes
Notes
A new dedicated line, provisioned and managed for you

CRM workflows

Keep or change
Keep or rebuild
Notes
Native on GoHighLevel, other CRMs via REST API and webhooks

Billing

Keep or change
Changes
Notes
$249 per line per month, no per-message fees

Channel scope

Keep or change
Expands
Notes
Full funnel, RCS then SMS fallback

What happens to your contacts and opt-out lists?

Opt-outs carry over fully. Each opted-out number loads as suppression before contacts land. Count checked before anything sends.

  • Contacts export standard with first name, company, merge fields. Old lists hold dead numbers. Mobile-validated leads: $0.03/contact (700M+ database).
  • Pull conversation history before you cancel; closed accounts are bad places to find deal context.

How does the migration run, step by step?

Migration runs in fixed order, sized during activation. No outbound pause needed: provisioning and parallel run while current program sends.

  • Export from Project Blue first: contacts, the opt-out list, templates, every active automation and your conversation history.
  • Your dedicated line gets provisioned and connected to your CRM during white-glove activation, which is $449 and waived on annual billing. Nothing is needed from you at this step.
  • Load the suppression list and check the count against your export before any contact record goes in.
  • Import contacts, then point your merge fields at the imported data.
  • Rebuild workflows. GoHighLevel maps over natively. Every other CRM connects through the REST API and webhooks, which is where you want a developer for an afternoon.
  • Run both lines in parallel, covered in the next section.
  • Cut all new sends over to Blue Reacher and stop scheduling anything new on Project Blue.
  • Cancel Project Blue once the old line has gone quiet.
What do you run in parallel during the switch?

What do you run in parallel during the switch?

Parallel protects earned replies. Keep Project Blue live a month after final send. Canceling cutover day loses conversations.

  • Send all new outbound from Blue Reacher from day one of cutover. Never split one campaign across two lines: the results are unreadable and recipients see two numbers from one company.
  • Route both inboxes into the same CRM so your team works one queue instead of checking two dashboards.
  • Sync opt-outs in both directions during the overlap. Someone who opts out on the old line gets suppressed on the new one the same day.
  • Compare like for like before you judge the switch: same segment, same offer, same send window, at least two weeks of data.
  • Keep one named person accountable for the old inbox until you cancel.
Cost comparison: Project Blue vs Blue Reacher

Cost comparison: Project Blue vs Blue Reacher

Monthly one line: $4,100 year one vs $3,437. Annual: $1,998 vs $1,949 ($49 difference). At two-plus lines Project Blue drops to $250.

  • Line count shifts math. Three lines: $9,000/year vs $8,964. Check your agreement before building business case.

Monthly, one line

Project Blue
$300
Blue Reacher
$249

Monthly, two or more lines

Project Blue
$250 per line
Blue Reacher
$249 per line

Annual, one line

Project Blue
$1,998 (about $166.50/mo)
Blue Reacher
$1,949 (about $162.50/mo)

Setup or activation

Project Blue
$500 monthly, waived on annual
Blue Reacher
$449, waived on annual billing

Year one, one line, monthly billing

Project Blue
$4,100
Blue Reacher
$3,437

Per-message fees

Project Blue
Not published, confirm with your contract
Blue Reacher
None, iMessages are unlimited

Mobile-validated B2B leads

Project Blue
Not published
Blue Reacher
$0.03/contact, 700M+ database, billed monthly with the line

Those are our assumptions. The Blue Funnel Map runs the same arithmetic on the funnel you actually have, and you keep the map either way.

Run these numbers on your funnel
Compliance during a platform change

Compliance during a platform change

Compliance follows your company. A2P 10DLC governs US SMS, not iMessage: no A2P needed. RCS carries its own verification. TCPA applies both.

  • Consent revocation matters. FCC rules (11 April 2025, DA 26-12) mean Project Blue revocations stand day one. Suppression loads and checks first.
  • Blue Reacher publishes security, controls, DPA, subprocessor list at bluereacher.com/trust. Procurement teams get control mapping, DPA, list, 15 questions.

Frequently asked questions

Will my opt-out list carry over from Project Blue?

Yes. Your suppression list is loaded into Blue Reacher before any contact records go in, and the count is checked against your Project Blue export before a single message goes out. A revocation belongs to your company, so it stays in force across a platform change.

How long does the migration take?

Migration length depends on your line count and your CRM, and your dates get set during white-glove activation. The work on your side is the export, the suppression and contact import, and the workflow rebuild. Line provisioning and the parallel run happen while your current program keeps sending, so nothing pauses.

Do I need A2P 10DLC registration to send with Blue Reacher?

No A2P registration is required to send iMessage. A2P 10DLC governs US carrier SMS routes, and iMessage is not carrier SMS, which is a registration distinction, not a consent exemption. RCS for Business carries its own verification requirements. TCPA applies to your program exactly as it did on Project Blue.

Can I keep my Project Blue number?

Plan for a new number. Your Blue Reacher line is a new dedicated line, provisioned and managed for you during white-glove activation, so build the migration around a number change and raise portability on your demo call if it matters to your program.

What happens to my conversation history?

Conversation history stays inside Project Blue. Export it before you cancel, even if you never expect to open it, because a closed account is a bad place to look for the context behind a deal six months later.

Is Blue Reacher cheaper than Project Blue?

Cheaper on monthly only. One line: $249 vs $300, $3,437 vs $4,100 year one. Two+ lines: $250, a $1 gap. Annual: $1,949 vs $1,998.

Does Blue Reacher work with my CRM?

Most CRMs native: GoHighLevel, HubSpot, Close, Salesforce, Pipedrive, Follow Up Boss. Zapier, Make, n8n, REST API, webhooks for rest. If not native, budget developer time.

Should I cancel Project Blue on cutover day?

No. Keep the old account live and receiving for at least a month after your last send from it, because replies land on the number that sent the message. Cancel once the old line has gone quiet, not when the new one goes live.

See the migration priced against what you actually pay now

Book a demo and bring your Project Blue billing term, your line count and your export. We will walk your contacts, suppression list and workflows through the exact order above, put real numbers on both billing terms, and tell you plainly if the math says stay where you are.