# Radian6 has no listening product left to keep

Radian6 was the listening product folded into Marketing Cloud Social Studio. Those subscriptions were retired on 18 November 2024, so do not plan as if the listening store is still there.

**Published:** 2026-01-15
**Canonical:** https://synconai.com/radian6-social-studio-retirement
**Author:** SynconAI Architecture Team

## In short

Radian6 was the listening product folded into Social Studio with Buddy Media. Those subscriptions were retired on 18 November 2024. Do not treat the listening store as still there. There is no Radian6 product to implement, and this page names no replacement. Price only what you can prove you hold, licences you still pay, people, and the ending. No figure here.

## Sources

- **Marketing Cloud Social Studio Retirement** (retrieved 2024-11-18)
  https://help.salesforce.com/s/articleView?id=sf.mc_cc_faq_resolve_missing_data_in_social_care_display.htm&type=5
  > Salesforce retired the following Marketing Cloud Social Studio subscriptions (“Marketing Cloud Social Studio Products”) on November 18, 2024.

## What to take away

- Radian6 was the listening product folded into Marketing Cloud Social Studio, along with Buddy Media.
- Salesforce retired those Social Studio subscriptions on 18 November 2024.
- Do not plan as if the listening data is still there to query. This page will not tell you that it is.
- A partner who promises the archive, or names an unsourced replacement, has left the notice.

## The guide

A quarterly pack still has a chart labelled Radian6. The person who presents it says the listening history is in the old tool, and asks a partner to keep it alive while a migration is scoped. The partner nods, because a nod is cheaper than a contradiction, and writes a line for historical listening data. Nobody in the room has opened a listening workspace this year. The chart is a picture of a picture. The line in the quote is a promise that the store is still a place you can read. This page will not make that promise, and you should not pay for it.

The habit is understandable. Listening numbers were how some teams justified the subscription. When the subscription ends, the habit remains, and it looks like a data migration. It is not a migration if there is no store you are allowed to treat as current. The work, if there is work, is to stop citing a system you cannot open.

## Listening was folded in, then retired

Radian6 was the listening product. It was folded, with Buddy Media, into Marketing Cloud Social Studio. Buddy Media was the publishing side. Radian6 was the side that listened. They are not a menu. The retirement covers the Social Studio subscriptions, which is the product those two were combined into. The notice says: "Salesforce retired the following Marketing Cloud Social Studio subscriptions (“Marketing Cloud Social Studio Products”) on November 18, 2024." That date is 18 November 2024. Use the notice's wording when you quote it. Use the date in the open when you write to your own team.

The same retirement is the whole of the Buddy Media story. If your brief still splits "publishing migration" from "listening migration" as if both products were waiting, read [the Buddy Media guide](/buddy-media-social-studio-retirement) and then close the split. There is not a publishing destination on that page, and there is not a listening destination on this one. Two briefs that each smuggle in a successor are worse than one, because each looks smaller. Small is how an unsourced product gets approved.

This page will not tell you the listening data is still there. Read that as an instruction, not as a tone. Do not write a plan that queries Radian6. Do not write a plan that queries Social Studio listening as a living archive. Do not let a partner's reassurance become your architecture. If someone says they logged in and the history was waiting, they are saying something this page does not know and will not repeat. The fact we have is the retirement of the subscriptions. Plan from that fact. A workspace you cannot demonstrate, on a dated screen, with your own tenant, is not a source system. It is a story.

## What you must not tell the business

You also should not invent a destruction story this notice does not tell. The notice retires subscriptions. It does not, in the sentence we cite, walk row by row through a database and declare each one gone or kept. You do not need that walk to act. You need to stop treating listening as a system of record. Reports that "came from Radian6" are claims about the past. They are not a feed. If a decision needs a listening number now, you do not have it from this product. Say you do not have it. Do not backfill the chart from memory, and do not pay an agency to backfill it and call the result migrated data.

Files someone exported before the retirement, if you can find them, are files. A file has a date, a person, and a format. It is not Radian6. It is not proof that the store is still queryable. Label the file as an export, not as a connection. If you cannot say who exported it or when, it is a weak file. Do not load a weak file into a new tool and call it history. You would be manufacturing a continuity the retirement does not give you.

Citations in old slides need a pass. Where a sentence says "Radian6 shows", either you still have the export that shows it, or you delete the sentence. Leaving the sentence up teaches the next reader that the store is there. That teaching is the failure this page is for. One afternoon with the last four quarterly packs will find the sentences. It is cheaper than a migration workshop, and it does not require a listening login you should not be promising.

## What a quote is allowed to price

No number on this page. Listening migrations attract numbers because history sounds large. Large is not a scope. The four lines are still scope, licences, people, and the ending. None of them is a rebuild of Radian6.

Scope is the inventory. Which contracts say Radian6 or Social Studio. Which invoices still arrive. Which exports exist, dated. Which logins have been tried, and the result of the try, written as failed or not attempted. Not attempted is not a yes. Scope excludes a query against the old listening store. Write the exclusion in the brief so it cannot be an assumption. Scope also excludes a destination product. This page will not name one. A bidder who includes one has changed the brief. Make them take it out, or make them submit a different proposal that does not mention Radian6 as the thing being continued.

Licences are charges that might still be happening through a reseller, an old order form, or a bundle nobody re-read after 18 November 2024. The retirement is a reason to look at the invoice. It is not, by itself, a calculation of what you are owed or what you owe. This page will not sign that calculation. Procurement and the contract owner do it, against the paper. If the invoice is already zero, say zero. Do not buy a new listening subscription inside this quote so the zero looks less embarrassing. Embarrassment is not a licence requirement.

People are whoever owned the listening questions, whoever can find an export, and whoever presents the quarterly pack. They need to hear, from you, that the chart does not have a live source. A partner cannot deliver that sentence to the room if you have told the partner to keep the chart alive. Internal time to retire the chart is a cost. Count it. It is the actual cutover: the meeting where the number stops being presented. There is no weekend where Radian6 "goes live" somewhere else.

Cutover language from build projects will mislead you. There is no go-live. There is a stop. The stop has two checks. Nobody is being billed for the retired subscription, or someone named is disputing a bill with the paper in hand. Nobody is citing Radian6 as a current source. When both are true, the work is done. A phase called historical migration, with a destination, means the work has been replaced with a project this page told you not to start.

## The test for a partner

The best Radian6 agency is a search, not a ranking. This page will not rank SynconAI or any firm that still sells the listening product as if it were current. The test is plain. They can name Radian6 as the listening product that was folded into Social Studio. They can name the retirement date. They can say they will not tell you the listening data is still there. They can say they will not name a replacement in this quote. They can say they will not give you a legal opinion on what you may keep, publish, or delete. That opinion is not a delivery milestone.

Objects, in this strange case, are not listening topics and sentiment objects. Those belonged to the product. The objects of the remaining work are the contract, the invoice, the export file, and the slide that still cites the tool. A partner who opens with topic design is designing for a product you do not have. Stop the workshop. A partner who asks where the quarterly pack is kept is closer to the job.

Hire only if the inventory is beyond what you can do in a week yourselves. Cap the hire at the inventory and the stop. Implementation partner is the wrong title. If they need the title to contract, the contract is already pointed at the wrong work. Change the title before you argue about the rate. A rate for the wrong work is not a bargain at any level, and this page still will not name a level.

## What the paper should look like

| Line they wrote | What it actually is | What you send back |
| --- | --- | --- |
| Keep Radian6 alive during migration | A promise that the listening store is still there | Delete it. This page will not say the data is still there |
| Migrate listening history | A destination plus an archive you have not shown | Ask for the export, dated. If there is none, there is no history in scope |
| Publishing and listening, one build | Buddy Media and Radian6, both retired with Social Studio | Split nothing into two builds. Read the Buddy Media page. Stop |
| Recommended listening platform | A replacement this page has not sourced | Remove the name. It is a different brief, later, if at all |
| One fee for social intelligence | Ending work priced as a product | Inventory, invoices, people, and the stop. No build |

::: warn
Do not tell your team the Radian6 listening data is still there. Do not hire someone to tell them that. Subscriptions for Marketing Cloud Social Studio were retired on 18 November 2024. A plan that queries the old store is a plan this page rejects.
:::

Send one paragraph to anyone who wants to price the work. Radian6 was listening, folded into Social Studio with Buddy Media. Those subscriptions were retired on 18 November 2024. We will not treat the listening store as a system we can read. We will not accept a replacement named in this quote. We want contracts, invoices, dated exports we already have, and a pass over slides that still cite the tool. Price that, as scope, licences still being charged, people, and the stop.

Keep the paragraph when the architecture arrives anyway. You do not need to debate the architecture. It answers a question you did not ask. The question you asked was what you still hold, and what you will stop saying. Answer that, file the exports properly, and take Radian6 off the operating list. The name can stay in a sentence about what the company once bought. It cannot stay as a login in a runbook.

If counsel asks what the retirement did to records you were obliged to keep, this page is not the advice. Bring them the notice and the exports you actually found. Do not bring them a migration plan that assumes the store is intact, and do not bring them a plan that assumes a destruction story we did not cite. The delivery fact is smaller. You do not have a current listening product under this name. Act as if you cannot read it, because that is the only stance the notice supports.

When a slide still needs a listening number for a decision this month, say the number is unavailable from Radian6. Offer the decision without it, or wait until you have a source you can open that is not this retired subscription. Do not ask an agency to reconstruct the chart from memory and label the reconstruction as migrated history. Reconstructed sentiment is a new claim. It needs its own evidence, its own date, and a name that is not Radian6. Leaving the old label on a new claim teaches the room that the store survived. Take the label off. The room can cope with a gap. It cannot cope with a gap that has been dressed up as an archive.

## The other searches

The project quote is on [radian6 implementation cost](/radian6-salesforce-implementation-cost). That page does not print a figure. Who bought the company is on [what happened to radian6](/what-happened-to-radian6). The connector is on [integrating radian6 with Salesforce](/integrating-radian6-with-salesforce). Whether to move is on [should I migrate from radian6](/should-i-migrate-from-radian6). The customer fee is on [radian6 licence cost](/radian6-salesforce-licence-cost). Who to hire is on [hiring for radian6](/hire-radian6-salesforce-partner). This page does not rank an agency.


## Questions

### What should a Radian6 data migration quote include?

It should state that Radian6 listening was folded into Social Studio and that those subscriptions were retired on 18 November 2024. It should refuse to treat the listening store as still there. It should list contracts, invoices, and dated exports you already hold, and it should not name a replacement. Split scope, licences still charged, people, and the stop.

### What is a Radian6 implementation cost made of?

An inventory, not an implementation. Scope is paper and files you can prove. Licences are invoices that have not stopped. People are whoever cites the old chart and whoever can end the bill. There is no go-live cutover into Radian6. This page will not print a price, and it will not price a new listening tool.

### Is the Radian6 listening data still there?

This page will not tell you that it is. Salesforce retired the Marketing Cloud Social Studio subscriptions on 18 November 2024. Radian6 was the listening product folded into that studio. Do not plan a query against it. An export you already saved is a file, not a live store. A partner who promises the archive is promising beyond the notice.

### How do you judge the best Radian6 integration agency?

Do not rank agencies, including SynconAI. A partner passes if they name the retirement, refuse to say the listening data is still there, refuse an unsourced replacement, and limit the work to inventory and stopping citations. A listening roadmap does not pass.

### When should you hire a Radian6 consultant or implementation partner?

Hire only if you need help finding contracts and killing citations, and cap that work. Do not hire an implementation partner to keep Radian6 alive or to land it on another product inside this brief. If the proposal says the history is waiting, you are done with that proposal. The Buddy Media page is the same retirement, not a second chance to build.

### Is radian6 owned by Salesforce?

It was. Radian6 was the listening product folded into Social Studio with Buddy Media. The full account is at https://synconai.com/what-happened-to-radian6.

### When did Salesforce acquire radian6?

Radian6 was acquired in 2011. Social Studio subscriptions were retired on 18 November 2024.

### What happened to radian6 after the Salesforce acquisition?

There is no current Radian6 product. Listening data was not left behind as a live tool.

### Should I migrate from radian6 to Salesforce?

Do not migrate into a product that was switched off. See the Buddy Media page for the same retirement.

### What is the radian6 licence cost, or the price Salesforce paid?

The page this guide cites does not publish a purchase price. There is no current licence. The licence read is at https://synconai.com/radian6-salesforce-licence-cost.

---

SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Marketing Cloud Next (https://synconai.com/salesforce-marketing-cloud-next).