# Should I migrate from Radian6 The room usually agrees the old listening report should be poured into an object, before anyone has asked whether a feed is still running. Social Studio was retired on 18 November 2024. **Published:** 2026-01-20 **Canonical:** https://synconai.com/should-i-migrate-from-radian6 **Author:** SynconAI Architecture Team ## In short Radian6 was folded into Social Studio, and Social Studio was retired on 18 November 2024. Do not migrate a retired listening product. There is nothing to migrate onto, and no replacement is named here. An AppExchange search will not bring it back. A campaign and a case do not listen. ## 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 - The agreement that the report needs a Salesforce object is compatible with a file on a drive, and incompatible with a listener anyone can open. - Radian6 was the listening product folded into Social Studio, alongside Buddy Media. The same retirement applies: 18 November 2024. - There is nothing to migrate onto. Do not pour the file into a campaign, a case, or a custom object and call the pile a feed. - An AppExchange search will not bring it back. No replacement is named, alternatives are not ranked, and no listing is invented. ## The guide A listening report still sits on a shared drive. The header says Radian6. Around the table everyone already agrees the next question is which Salesforce object the report should be migrated into. The question already assumes a destination. The agreement is the problem. It is easy to reach, and it fits an import wizard, which is not a feed that received anything this morning. A header on a file is compatible with a retired listening product, a campaign that groups members, a case that records an issue, and a digest people still expect. It is not compatible with a live listener under the Radian6 name. Choosing an object to pour the file into does not recreate a listening product. It creates a custom pile and calls the pile Radian6. Refuse the pile. What follows are the questions that separate a stop from a pretend import. Each has a good answer and a bad answer, and the difference is whether the answer names something specific: a file, a date, a person who opened it, an empty destination. A general answer at this stage is what books the wizard. ::: warn Do not migrate a retired listening product. Social Studio was retired on 18 November 2024. There is nothing to migrate onto. Do not name a replacement. An AppExchange search will not bring Radian6 back. ::: | Question | Who has to answer it | What a bad answer usually means | | --- | --- | --- | | 1. Which file still has the header | The person who last opened the report | An object mapper is being booked for a document | | 2. What ended, and on which day | Whoever still draws a listening feed | Radian6 is being migrated into Social Studio or Buddy Media | | 3. What do a campaign and a case already record | The administrator who can open them | A case comment is being hoped into a listener | | 4. What may be done with the rows | Whoever wants one historical line | A paste is being called a cutover | | 5. What must the plan refuse | Whoever asked which object it should go into | The question has smuggled a destination | ## 1. Which file is actually in the room? The question is not which object should receive Radian6. It is the file name, the date it was last opened, and whether it still opens. **A good answer sounds like** the file name, the person who opened it, the date, and a mark that the file is historical, not a source system. **A bad answer sounds like** we will recreate the report from memory and then migrate the memory. If the file is missing, write that it is missing. Missing is a result. Do not recreate it. Stopping is a finished answer. The report can stay in the drive as a historical file, with the date of the retirement written on the folder. It should not appear in a migration backlog. A backlog is a list of moves. This item does not move. Refuse the question "which object should it go into?" The question smuggles a destination. The answer is no object. Say that in the meeting, in those words, so the import wizard does not get booked. ## 2. What is the software now? Radian6 was listening. It was folded into Marketing Cloud Social Studio. That studio's subscriptions were retired. The notice says so, and the sentence is quoted once: "Salesforce retired the following Marketing Cloud Social Studio subscriptions (“Marketing Cloud Social Studio Products”) on November 18, 2024." The day is 18 November 2024. The sentence writes November 18, 2024. Same day. What the software is now is not a product. It is a retired listening name. There is no current Radian6 org, trial, or stream to point a migration at. **A good answer sounds like** the header changed, or a line under it that says retired, not a source system, written by the person who opened the file. **A bad answer sounds like** we will migrate Radian6 into Social Studio, or into Buddy Media. Those names are not live destinations. Radian6 was the listening product folded into that studio with Buddy Media. You do not migrate one retired name into the other. Both names ended as live systems on the same date. A diagram that still shows three boxes and two arrows is a picture of the history, not a plan. Collapse it to one line: retired on 18 November 2024. People still search the old name because the header has not been changed. Change the header. The file's contents, if they are still readable, are historical text. Historical text is not a listener. A listener would be receiving new items. This one is not. No product is named here that listens in its place. A seller who names one is not quoting the notice. The notice retires subscriptions. It does not appoint a successor. Do not appoint one in the meeting. Count the listening jobs people still describe as if a feed were running: a morning digest, a keyword watch, an alert into a queue. Each description needs a correction. The feed is not running inside Radian6. If a feed is running somewhere else, it is that other system's feed, and it is not renamed back to Radian6 to give a migration a source. ## 3. What do a campaign and a case already do? On the core platform, a campaign groups campaign members and a status. A case records a customer issue, with an owner and a status. Those objects already do that work. They record people and issues inside the org. They do it whether or not a file on a drive says Radian6. They do not listen. A campaign does not watch a network and add posts. A case does not ingest a stream. If the comparison starts from those objects, write that limit before anyone compares anything. Otherwise a comparison becomes a hope that a case comment is a listening product. **A good answer sounds like** an administrator who has opened the campaign and the case and said, in the meeting, that neither watches a network. **A bad answer sounds like** pasting rows from the old report into a case, or onto campaign members, migrates a listener. It stores text. Stored text can be useful to a person who reads it. Usefulness is not a restored feed. There is no native listening object here that is Radian6 restored. If you cannot open a listening product under the Radian6 name, you do not have one under another name that will be supplied here. Keep three lines apart. Core campaign and case: their own jobs. Radian6: a retired listening product. Destination: none. A plan that adds a fourth line with a product name has left the decision. There is no score. A chart that scores Radian6 against a current feature is scoring a retired product against a different job. The feature keeps doing its job. Radian6 does not start doing it. There is no winner, and they are not ranked. ## 4. What may you do with the file? Open the report once. Write who opened it and on which date. If it opens, it is a document. If it does not open, write that down as well. Neither result is a system you can migrate. A document can be kept so the organisation remembers what it used to read. Keeping it is not operating Radian6. **A good answer sounds like** the folder renamed, by a named person, from a migration invitation to a label such as a retired listening export dated 18 November 2024. **A bad answer sounds like** copying the rows into a campaign, a case, or a custom object in order to say the migration happened. The copy would be a new pile of text. The pile would not listen tomorrow morning. If a person needs one historical line for a case they already own, they can paste that line as a note on that case. The note is a note. It is not a feed, and it is not a cutover. Do not schedule a migration weekend. There is nothing to cut over. The only date to write down is 18 November 2024. If a plan has a later date, the later date is an invention. Remove it. Change the folder name if the folder still invites a project. Tell the next person who finds the folder that the decision already ended in stop, and that an object mapper is the wrong tool. A morning digest that people still expect has to be answered in the present tense. Either some other system, which is not named here, is already sending it, or nobody is sending it. If nobody is sending it, the honest line in the meeting is that the digest ended with the product. Do not rebuild the digest from the old file and call the rebuild a migration of Radian6. The file does not know what happened on the network this morning. When every listening claim that depends on Radian6 has been marked stop, the decision is finished. An empty destination is the outcome you want. Do not fill it to show progress. Progress, here, is the absence of a fake source. If a box on a diagram still says Radian6, delete the box. Do not relabel the box with a product that has not been named. ## 5. What is the plan using instead of stop? The substitutes are a listing, a rank, and a product name in the destination column. **A good answer sounds like** a refusal, written by the person who opened the file, of a listing, a rank, and any product name on the right-hand side. **A bad answer sounds like** a link to a listing, offered as the answer to "should we migrate". No listing is invented here. An app, a publisher, a review count, and a price would be an invention. The product was retired. An AppExchange search will not bring it back. A listing is not a listening feed, and it is not Radian6 restored. Do not treat a search result as a reversal of 18 November 2024. Ask them to open Radian6. They cannot. The link stays outside. The report stays a file. Other tools exist. They are not named in an order, and they are not ranked. A later choice of some other listener, for a job you state in the present tense, is a different decision. It is not a Radian6 migration, and it does not belong in this backlog. If a slide arrives with ranks, remove it. The meeting can proceed from the retirement date and the word stop. ## What stopping actually looks like All five answers are measured against an alternative, and the alternative is usually left unstated, which flatters the import wizard. State it. Stopping means nobody is asking which object to pour the file into. The header says the product is retired. The campaign and the case keep their own jobs. The cost of a false move is a custom object full of yesterday's text, which does not listen, and a diagram that still draws a feed. There is no kinder version in which the file becomes a system again. An organisation that marks the report historical first avoids rebuilding a digest from a document that cannot see this morning's network. **A good answer sounds like** the report marked historical, the diagram box deleted, and the word stop, written by the person who opened the file. **A bad answer sounds like** we need a destination so the listening history has a home. The history can stay a file. A home in an object would be the pile. ## Where the neighbouring questions live Notes that are still about the old name sit on [the Radian6 implementation page](/radian6-social-studio-retirement). The retirement as history sits on [what happened to Radian6](/what-happened-to-radian6). There is no live listener to wire. The page that says so is [integrating Radian6 with Salesforce](/integrating-radian6-with-salesforce). ## Questions ### Should I migrate from Radian6 to Salesforce? No. Do not migrate a retired listening product. Social Studio was retired on 18 November 2024. There is nothing to migrate onto, and no replacement is named here. ### What is Radian6 software now? It was the listening product folded into Social Studio, with Buddy Media. Those subscriptions were retired on 18 November 2024. There is no live listener under that name. ### How does Radian6 compare with native Salesforce features? A campaign groups members and a status. A case records an issue. Neither listens, and neither restores Radian6. Compare only after that is written down. ### What are the alternatives after the acquisition? Stop. No replacement is named here. Other tools are not ranked, and no listing is invented. A later listener, for a present-tense job, is a different decision. ### Will an AppExchange listing bring Radian6 back? No. The product was retired. An AppExchange search will not bring it back. No listing is invented here. --- 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).