Migrating from Linq Blue to Blue Reacher
The short answer
Migrating takes two weeks and four hours of hands-on work. Keep your CRM, contacts, and opt-outs. The send model changes. Linq Blue doesn't support message blasts; here's how to move.
Key takeaways
- Your CRM stays in place. Blue Reacher sends from your CRM: pipeline, fields, owners, and reporting stay intact.
- Migration runs on a two-week calendar with four hours of hands-on work.
- Opt-outs import first. A contact who said stop was talking to your company, and that carries over.
- Parallel running is what most teams skip and regret.
- Linq publishes no pricing, so price-based decisions are weak.
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
Why do teams move from Linq Blue to Blue Reacher?
Teams move for campaign sending. Linq Blue doesn't support message blasts by design. Sending one offer to 400 accounts doesn't fit Linq Blue. The products solve different problems.
- Funnel coverage matters. Outbound prospecting is half the value. The other half is converting paid traffic: reactivation, speed to lead, reminders, no-show recovery, post-call follow-up, payment, onboarding, retention, referrals, and review. Linq Blue doesn't build this layer.
- Weak reasons: sales call annoyance, cheaper pricing (Linq publishes none), or the pivot rumor. Strong reasons: campaigns, sequences, and list sends that drive revenue.
- Move if campaigns, sequences, or list sends are core to your revenue motion
- Move if you want published pricing you can budget against before a sales call
- Move if you want one line covering outbound and lifecycle messaging together
- Do not move if reps only ever text people they already spoke to on the phone
- Do not move on price alone, because you cannot compare against a number Linq Blue does not publish
What do you keep and what changes?
Your CRM stays in place. Blue Reacher sends from your CRM: pipeline, fields, owners, and reporting stay intact. Contact data and opt-outs carry across. Conversation history doesn't, so export it before canceling.
- Three things change: CRM connection, send model, and compliance. Blue Reacher is native to GoHighLevel; everything else uses REST API and webhooks. Linq Blue's native apps spare ops teams an integration project.
CRM of record
- On Linq Blue
- Unchanged
- After migrating
- Unchanged
- Work required
- None
Contact records
- On Linq Blue
- In your CRM
- After migrating
- In your CRM
- Work required
- None
Opt-out list
- On Linq Blue
- Suppression in CRM and platform
- After migrating
- Imported before any send
- Work required
- About 30 minutes
Salesforce or HubSpot link
- On Linq Blue
- Native app
- After migrating
- REST API and webhooks
- Work required
- 2 to 4 hours, once
GoHighLevel link
- On Linq Blue
- Native
- After migrating
- Native
- Work required
- Under an hour
List sends and campaigns
- On Linq Blue
- Not supported
- After migrating
- Supported
- Work required
- None
Conversation history
- On Linq Blue
- Lives in Linq Blue
- After migrating
- Export for your archive
- Work required
- About an hour
How does the migration actually work, step by step?
Migration runs on a two-week calendar with four hours of hands-on work. Technical setup rarely sets the pace. Your Linq Blue contract end date does, so plan overlap around renewal.
- Day 0, book activation and decide line count. One line per sending persona or per team, matching how you run Linq Blue today.
- Days 1 to 3, white-glove activation. Your dedicated iMessage lines get set up and managed for you. No A2P registration required, so there is no carrier paperwork queue to sit in.
- Day 2, export from Linq Blue while activation runs. Opt-out or suppression list first, contacts second, conversation history third for archive.
- Day 3, connect the CRM. GoHighLevel is native, under an hour. Salesforce, HubSpot, or a custom stack runs through REST API and webhooks, two to four hours for an ops person.
- Day 4, import in the right order. Suppression list first, contacts second. Never the reverse.
- Day 5, test on people who work for you. Send to ten internal numbers, confirm delivery, confirm replies land where your reps expect them, confirm opt-out handling works.
- Days 6 to 14, parallel run. New campaigns on Blue Reacher, in-flight conversations finish on Linq Blue.
- At renewal, cancel Linq Blue. Third-party reports describe annual agreements, so check your term first. If you are paying either way, the overlap is free coverage.
Reading how it works is not the same as watching it answer one of your own leads. The Blue Funnel Map does the second one.
See it on your own listWhat happens to your contacts and opt-out lists?
Opt-outs import first. A contact who said stop was talking to your company, and that carries over. Export suppressions from Linq Blue, export opt-out fields from your CRM, merge both, and load before any contact.
- Contacts are easy because most teams never move them. If your CRM holds records and Blue Reacher sends from the CRM, migration is a connection not a transfer. Teams with lists inside Linq Blue export, dedupe, import only the delta.
- A2P 10DLC governs SMS, not iMessage, so no registration required here. TCPA applies to every channel. Most FCC consent-revocation rules took effect 11 April 2025; the revoke-all provision extended to 31 January 2027 by order DA 26-12.
What should you run in parallel during the switch?
What should you run in parallel during the switch?
Parallel running is what most teams skip and regret. Keep both platforms live for 1-2 weeks, split by segment not rep, so no contact gets two numbers. Splitting by rep costs relationships and deals.
- Finish in-flight conversations on Linq Blue. Do not yank a live thread mid-deal.
- Start every new campaign, reactivation push, and lifecycle trigger on Blue Reacher.
- Assign whole segments to one platform at a time, never individual contacts.
- Track reply rate and time to first reply on both, so the comparison is yours and not a vendor's.
- Keep the CRM as the single source of truth for opt-out status during the overlap.
What does the switch cost?
What does the switch cost?
Linq publishes no pricing, so price-based decisions are weak. Blue Reacher publishes $249/month or $1,949/year (about $162.50/month). Lines pace at 50 opted-in / 30 cold new contacts a day. Unlimited iMessages, no per-message fees. Activation $449, waived on annual billing. Lead add-on $0.03/contact.
- All figures are third-party estimates at $160 to $250/month on annual contracts. Treat as unverified. Budget similar and choose on capability.
Published pricing
- Blue Reacher
- Yes, on the site
- Linq Blue
- None published
Per line, monthly
- Blue Reacher
- $249
- Linq Blue
- Roughly $160 to $250 (third-party reported)
Per line, annual
- Blue Reacher
- $1,949 (~$162.50/mo)
- Linq Blue
- Annual contracts (third-party reported)
Per-message fees
- Blue Reacher
- None, unlimited iMessages (50 opted-in / 30 cold new contacts a day)
- Linq Blue
- Not published
Activation
- Blue Reacher
- $449, waived on annual billing
- Linq Blue
- Not published
Lead data add-on
- Blue Reacher
- $0.03/contact, billed monthly with the line
- Linq Blue
- Not published
Frequently asked questions
Does my Linq Blue opt-out list carry over to Blue Reacher?
Yes, your opt-out list carries over, and it should be the first thing you import. Export the suppression list from Linq Blue, merge it with any opt-out tags or fields in your CRM, and load the merged list into Blue Reacher before importing a single contact.
Will I lose my conversation history when I switch?
Conversation history does not transfer between the two platforms. Export it from Linq Blue for your archive before you cancel. In practice this matters less than teams expect, because if your CRM logs message activity, the record your reps actually reference stays intact.
Does Blue Reacher have security controls published?
Blue Reacher's controls are mapped to the SOC 2 Trust Services Criteria, with the DPA, subprocessor list and control mapping published at bluereacher.com/trust.
Can Blue Reacher send campaigns to a list of contacts?
Yes, campaign sending to lists and segments is core to Blue Reacher, covering outbound sequences plus reactivation, reminders, no-show recovery, and post-call follow-up. Linq Blue's own site says the product does not support message blasts, and that difference is the main reason teams migrate.
Do I need A2P 10DLC registration after migrating?
No A2P registration is required. A2P 10DLC governs US carrier SMS routes, and iMessage is not carrier SMS, so the registration queue does not apply. That is a registration distinction, not a consent exemption. TCPA applies on either platform, so keep your consent records as rigorous as they are today.
How long does the migration actually take?
Migration takes about two weeks of calendar time and roughly four hours of hands-on work. Line activation runs one to three days, CRM connection takes under an hour on GoHighLevel or two to four hours through REST API elsewhere, and the rest covers parallel running and your Linq Blue contract term.
Does Blue Reacher integrate with Salesforce and HubSpot?
Salesforce and HubSpot connect via REST API and webhooks, not native. GoHighLevel, Close, Salesforce, Pipedrive and Follow Up Boss are native. Linq Blue ships native Salesforce, HubSpot, and HighLevel. Teams without ops should weigh integration costs.
What does Linq Blue cost compared with Blue Reacher?
Linq Blue publishes no pricing, so there is no like-for-like comparison until you hold a quote. Blue Reacher publishes $249 per line per month, or $1,949 annually. Third-party reports put Linq Blue at roughly $160 to $250 per line per month on annual contracts, and that figure stays unverified.
Did Linq discontinue Linq Blue in January 2026?
No, Linq Blue is still actively sold. January 2026 is when Linq stopped advertising Blue specifically to sales teams, which some comparison articles turned into a discontinuation story. The company raised a $20M Series A announced in February 2026 and launched a developer platform in March 2026.
See what your migration would actually look like
Book a demo and we will map your specific switch: line count, CRM connection method, how your opt-out list transfers, and what runs in parallel. If the answer is that you should stay on Linq Blue, we will say so on the call. Blue Reacher runs $249 per line per month with unlimited iMessages, no per-message fees, and no A2P registration required. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered.