# Should you migrate from Qualified? The room usually agrees the website conversation should become the only message, before anyone has named the renewal that goes to a buyer who never visits the site. **Published:** 2026-05-18 **Canonical:** https://synconai.com/should-i-migrate-from-qualified **Author:** SynconAI Architecture Team ## In short Salesforce completed the Qualified acquisition on 1 April 2026. Qualified does not replace Marketing Cloud Engagement. A conversation is not an email send. Do not migrate Engagement sends into Qualified. Name the send, who receives it, and what happens to a person who never visits the site if it stops. Keep the send, use a conversation for a visitor on the site, or keep both. ## Sources - **Salesforce Signs Definitive Agreement to Acquire Qualified** (retrieved 2026-04-01) https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-qualified/ > Salesforce completed its acquisition of Qualified on April 1, 2026. ## What to take away - The agreement that the journeys are duplicates is compatible with a buyer who never visited the site and missed a renewal, and a chat does not deliver that mail. - The acquisition completed on 1 April 2026. Qualified does not replace Marketing Cloud Engagement. No end date is given here for either product. - A conversation is not an email send. Do not migrate Engagement sends into Qualified. An Engagement send already goes to an audience, with a message and a suppression rule. - The choices are keep the send, use a conversation for a visitor on the site, or both. They are not ranked. No listing or shutdown date is invented. ## The guide A marketing lead switched Marketing Cloud Engagement off on the Friday after the close. Qualified had been acquired, so the journeys were called duplicates. The website conversation would become the only message. Around the table everyone already agreed one product was enough. On Monday a buyer who never visited the site missed a renewal. A buyer who had chatted received the same words by email as well, because a journey had been copied into the conversation and the send had not actually stopped. Two systems said the same thing, and one buyer heard nothing. The agreement is the problem. It is easy to reach, and it fits a close date, which is not a message anyone has named. A missed renewal is compatible with a send that already goes to an audience, a conversation with a person who arrived on a page, a lead or a contact that stores an email address and does not transmit anything, and a completion that does not list your journeys. Only one of those is a decision about a named message. The completion had been used as a product replacement. It was not one. What follows are the questions that separate those explanations. Each has a good answer and a bad answer, and the difference is whether the answer names something specific: a send, an audience, a suppression, a visitor, a person who owns the journey. A general answer at this stage is what switches a journey off and calls the silence a strategy. ::: warn Qualified does not replace Marketing Cloud Engagement. A conversation is not an email send. Do not migrate Engagement sends into Qualified. No end date is invented here for either product. ::: | Question | Who has to answer it | What a bad answer usually means | | --- | --- | --- | | 1. Which message is supposed to move | The person who owns the journey you were about to switch off | "Marketing" is standing in for a renewal, a welcome, or a chat | | 2. Who hears nothing if the send stops | The owner of that send | A buyer who never visits the site has been left out of the decision | | 3. What does an Engagement send already do | Whoever can pause the journey | A lead record is being treated as the transmission | | 4. What did the completion sentence retire | Whoever switched Engagement off on Friday | A date is being read as permission to delete a product | | 5. What must the plan refuse | Whoever copied the email body into the conversation | One person is about to be double-messaged and another missed | ## 1. Which message is actually in the room? The question is not whether to migrate Qualified. It is a renewal reminder, a welcome, or a conversation with someone already on a page. If you cannot say which, you are not ready to switch a product off. **A good answer sounds like** one message, named by the person who owns it, as either a send to an audience or a conversation with a visitor, and not both in the same sentence. **A bad answer sounds like** marketing, or the journeys are duplicates. You are ready to leave both running until the sentences exist. A programme that starts by disabling journeys has chosen the missed mail. Send that programme back. Qualified is a conversation with an inbound buyer on a website. Salesforce completed the acquisition on 1 April 2026. A person arrives. A conversation can greet them and follow rules you wrote. That is a different job from an email that goes out on a schedule or a trigger to a list. The product did not become Marketing Cloud Engagement. The close did not move the journeys. What it is now is that site conversation, under the name Qualified. What it is not is the place your sends live. "Qualified exists" is not a reason to stop a send. A buyer who never opens the site never enters the conversation. ## 2. What happens to the person who never visits? Stay on Engagement when the message is an email send to people who are not on the website. A journey speaks to an audience you chose. A conversation speaks to a person who arrived. Qualified does not replace Marketing Cloud Engagement. Turning the send off because the close happened will silence the buyer who never visited. That buyer is the Monday failure. Leave the send on until its owner stops it for a reason other than the acquisition. **A good answer sounds like** four lines from the send you were about to switch off: who receives it, what it says, who owns it, and what happens to a person who never visits the site if the send stops. If the fourth line is "they hear nothing", you have found the reason to keep it. **A bad answer sounds like** the conversation will cover them. A conversation cannot deliver a message to a person who is not there. Move nothing from a send into a conversation. Do not migrate Engagement sends into Qualified. A conversation is not an email send. If a visitor on the site needs a chat, that is a new decision about the page, not a relocation of the renewal. The renewal still needs the send, or it needs a deliberate decision to end that send. The completion is not the decision. Write two sentences. One for the conversation on the site. One for the send that stays. If the sentences match, you have not understood either product. They are not collapsed here to make a slide shorter. ## 3. What does an Engagement send already do? Name the native behaviour before you compare a conversation with it. Marketing Cloud Engagement sends email to an audience. A send has a message. It has the people it is allowed to reach. It has the suppression that keeps out people who must not receive it. A journey can run more than one send, in an order you already configured, to people who meet a rule. A person who owns the journey can pause it. The send goes to people whether or not they are on your website at that moment. That is what an Engagement send already does. A Lead or a Contact is the record side of the same picture, and it is not the send. The record stores who the person is: a name, an email address, a status. It does not, by existing, transmit the renewal. It does not hold the conversation. If you have not opened the send and the record as two different things, you are not ready to place a chat beside them. You will paste the email into the chat and call it one programme. **A good answer sounds like** the audience, the message, the suppression, and the owner, written by the person who can pause the journey, with the lead or contact named as a record and not as the send. **A bad answer sounds like** versus native, with no send named. That note is the Friday ticket. Send the ticket back. If the problem is the renewal mail, you are not migrating. The send already does that job. Leave it on. If the problem is a visitor on a page, the send is the wrong tool to replace with a chat, and the chat is the wrong place to store the send. Keep the send for the audience. Use the conversation for the visitor, with its own rules. The decision stops at the split. Qualified does not replace Marketing Cloud Engagement, so the close is not permission to pick one and delete the other. Do not copy the email body into the conversation and call that a migration. The visitor did not ask for the renewal text. The subscriber did not join a chat. You will double-message one person and miss the other, which is the Monday you already had. If you can only write one sentence, you only have one job, and it is probably the send that was already working. ## 4. What did 1 April 2026 complete? Do not migrate because the company was bought. The completion was 1 April 2026. That is a date. It is not an email design. The page cited here says the acquisition completed, and the sentence is quoted once: "Salesforce completed its acquisition of Qualified on April 1, 2026." The sentence does not list your journeys. It does not say a chat is a send. It does not retire Engagement. **A good answer sounds like** the completion left as a date, by the marketing lead who switched the journeys off, with Engagement still running the named send. **A bad answer sounds like** the close retired the send. There is no end date for Qualified in the material this decision is allowed to use, and there is no end date for Engagement either. Do not invent either. People who search for what the software is, after the close, deserve the narrow answer. It is the conversation on the site. It is not every message the company sends. Write that on the slide that tried to switch Engagement off. Marketing Cloud Engagement remains the product that sends the mail you already run, until you stop a named send for a named reason. The reason has to be something other than the acquisition. ## 5. What is the plan using instead of the two sentences? **A good answer sounds like** a refusal, written by the owner of the send, of four things: switching Engagement off because of the close, copying the email into the chat, a listing as the journey, and a ranked shortlist. **A bad answer sounds like** a listing, or a league table of message tools. No listing is invented here. An app that replaces a journey is not described. A catalogue page is not a decision. If a proposal cites a listing that was never named here, ask them to name the send and the visitor as two different people. Until they can, the listing is a rumour. The shapes here are not ranked. Keep the send. Use a conversation for a visitor who is on the site. Keep both, and write two sentences that do not match. Firms are not ranked. Listings are not ranked. Two options can be compared by whether the buyer who never visited still hears the renewal. A league table cannot. Stop after one message. The next message is the next decision. Cross out the journeys this decision will not touch. Read the two sentences to the person who owns the send you almost switched off. If they can only hear one sentence, you have collapsed the products again. Separate them before anyone disables a journey. ## What staying actually looks like All five answers are measured against an alternative, and the alternative is usually left unstated, which flatters a single product on the slide. State it. Staying means the named send keeps going to its audience, with its suppression, and a conversation is used only for a visitor who is actually on the site, under rules that are not the email body pasted across. The cost of a false move is the Monday you already had: one buyer missed, one buyer told twice, and a journey called a duplicate because a company was bought. There is a version of staying that is simply the correct decision. If the fourth line is silence for anyone who never visits, the send stays. An organisation that writes the two sentences first reaches any later connection with the renewal still arriving. **A good answer sounds like** the send, who receives it, what a conversation is for, the gap for the person who never visits, and a choice to keep the send, use a conversation for the visitor, or keep both, with a date and the owner of the journey. **A bad answer sounds like** we cannot keep Engagement after the close. The completion did not retire Engagement. It did not turn a chat into a send. ## Where the neighbouring questions live Cost and hiring sit on [the Qualified implementation page](/qualified-agentic-marketing). The purchase story sits on [what happened to Qualified](/what-happened-to-qualified). The connector sits on [integrating Qualified with Salesforce](/integrating-qualified-with-salesforce). ## Questions ### Should I migrate from Qualified to Salesforce? Do not migrate Marketing Cloud Engagement sends into Qualified. Salesforce completed the Qualified acquisition on 1 April 2026. Qualified does not replace Engagement. A conversation is not an email send. Keep the send, use a conversation for a visitor on the site, or keep both with two sentences that do not match. ### What is Qualified software now? A conversation with an inbound buyer on a website. The acquisition completed on 1 April 2026. It did not become Marketing Cloud Engagement, and it does not hold the sends you already run. No end date is given here for either product. ### How does Qualified compare with an Engagement send? An Engagement send goes to an audience, with a message and a suppression, whether or not the person is on the site. A conversation speaks to someone who arrived. A lead or a contact stores who the person is and does not transmit the renewal. Compare only after the send is named. ### What are the alternatives after the acquisition? Keep the send, use a conversation for a visitor on the site, or keep both. They are not ranked. No listing is invented. Copying the email body into the chat is not an alternative. ### Where are cost, the acquisition story, and the connector? Cost and hiring are on the implementation page. The purchase story is on the what-happened page. How a conversation writes to a lead is on the integration page. No price and no shutdown date are stated 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).