ChatGPT
Claude
Google AI
Copilot
A plan for this year says migrate RelateIQ to Salesforce. The product was retired in 2020. There is no org to move into. On the same page, someone has pasted close to $400 million into the cost of the move. Around the table everyone already agrees both lines belong, because a plan feels unfinished without a destination and a number. The agreement is the problem. It is easy to reach, and it fits a budget, which is not a tenant anyone can open.
A retired name is compatible with a Sales Cloud design you might still need, an account that holds the organisation you sell to, and a figure that belongs only to an old acquisition. It is not compatible with a SalesforceIQ org in 2026. Sales Cloud is not the restore. The figure is not a licence. Putting them on the destination line and the cost line is how a history becomes a project.
What follows are the questions that separate a stop from a pretend cutover. Each has a good answer and a bad answer, and the difference is whether the answer names something specific: a year, a fenced figure, a person who tried the old login, an object that already exists. A general answer at this stage is what turns into a phase for a product that is not there.
| Question | Who has to answer it | What a bad answer usually means |
|---|---|---|
| 1. What does the plan still call a destination | The owner of the migrate line | A 2026 phase is standing in for an org retired in 2020 |
| 2. Where does the money figure belong | Whoever pasted it onto a cost line | An acquisition is being spent as a licence or a build |
| 3. What do account, contact, opportunity, and activity already record | The administrator who can open a deal | Sales Cloud is being described as RelateIQ with newer paint |
| 4. Is any current sales work still real | The person who hoped the old product would cover it | That work is being titled as a RelateIQ migration |
| 5. What must the plan refuse | Whoever offered a listing or a slice of the figure | A search is being funded as if the product could be bought again |
1. What is the plan still trying to open?
The question is not how to migrate RelateIQ. It is which line still names RelateIQ or SalesforceIQ as a system you will cut over.
A good answer sounds like the destination struck through, retired in 2020 written beside the name, and any later phase deleted, by the owner of the plan.
A bad answer sounds like we will open the old org next quarter. Do not migrate onto SalesforceIQ, and do not migrate RelateIQ into SalesforceIQ. Both names ended with the product in 2020. A plan written now that uses either name as a system you will cut over is late by years. Strike the destination. A phase after that line is for a product that is not there. Delete the phase. There is no org to open on Monday morning under the old name.
The cited page puts the purchase and the ending in one sentence, and the sentence is quoted once: "Acquired by salesforce.com in 2014 for close to $400 million, the company's product was retired in 2020."
Read it in three parts, and do not let the middle part travel. Acquired in 2014. The figure is close to $400 million, and it belongs to that acquisition alone. The product was retired in 2020. SalesforceIQ is the name the product wore after RelateIQ. It is not a second product that survived. The sentence writes the buyer as salesforce.com. That is the record's wording. It does not leave a separate company you can still buy the product from. What the software is now is nothing you can open. There is no SalesforceIQ org to implement. A bookmark that still says RelateIQ is not an org. Try it once if you must, write down what you see, and then stop treating the bookmark as a source system. A marketing page or an error is not a tenant.
2. Where is the figure allowed to sit?
Take the money figure off every cost line. Close to $400 million is what the cited page says was paid for the company. It is not your licence. It is not a budget you may slice into phases. It is not a percentage you may apply to a move. The move is not happening. The figure stays in the acquisition sentence and nowhere else.
A good answer sounds like a single note, written by the person who found the figure on the cost line: old acquisition, close to $400 million, not ours to spend.
A bad answer sounds like an exact dollar, or a fraction of the deal assigned to a build. Do not tighten "close to" into an exact sum. The cited sentence does not. You cannot buy the product back with the old figure either. The figure is history. Count the documents that still say RelateIQ or SalesforceIQ as a live destination. Each one is a correction. The count of orgs you can migrate onto is zero.
3. What do the sales objects already record?
On Sales Cloud, an account is the organisation or the person you sell to. A contact is a person related to that account. An opportunity is a deal. It has a stage and an amount. An activity is a task or an event a person recorded against a record. Those objects already do that work. They are how a sales team records parties, deals, and the work around them.
They do not contain a SalesforceIQ workspace. A stage is not a restored inbox. An activity is not the old product's history brought back by the acquisition. If the comparison starts from these objects, write what they already do before anyone compares anything. Otherwise the comparison becomes a claim that Sales Cloud is RelateIQ with a newer coat of paint. It is not.
A good answer sounds like an administrator who has opened an opportunity, named the stage and the amount, and said plainly that the record is not a restored workspace.
A bad answer sounds like pour the old product into the opportunity. Versus native does not mean that. It means you have seen what the opportunity already is, a deal with a stage and an amount, and you have refused to call that deal a restoration. No screens from the retired product are invented here, and they are not mapped onto opportunities one for one. You do not have the product in front of you. A sales design, if you need one, starts from accounts, contacts, opportunities, and activities. It does not start from a retired name.
Keep three lines apart. Native objects: account, contact, opportunity, activity. SalesforceIQ: retired in 2020. Money: close to $400 million, acquisition only. A plan that puts the money on a cost line has merged the third line into a budget. Take it off. There is no rank in which Sales Cloud wins as the alternative to RelateIQ. It is not an alternative in a list. It is the native sales product you may design separately. The retired product cannot be chosen. Nothing is ranked here, and no listing is invented.
4. What if the sales work is still real?
Ask whether anyone still needs sales work that they were hoping the old product would cover. If they do, the next sentence is a Sales Cloud design, which is a different product. Write that sentence somewhere else. Do not let it say "restore RelateIQ" at the top. If they do not, you are finished. No design is required by this retirement.
A good answer sounds like three sentences only: SalesforceIQ was retired in 2020; close to $400 million was the acquisition and is not a cost line; if sales work is still required, it will be named as Sales Cloud, elsewhere, and it will not be titled as a RelateIQ migration.
A bad answer sounds like the old org will be opened next quarter, or the figure is a budget, a licence, or a fraction of a build, or Sales Cloud already contains the retired workspace. Strike those lines and write the three sentences instead. A requisition that asks for someone to configure SalesforceIQ should be closed. There is nothing to configure.
A file rebuilt from memory, and titled SalesforceIQ, is not the product. Loading it into opportunities does not complete a migration. It creates opportunities. Call them opportunities if you create them, and only if a current sales process needs them. That need is a Sales Cloud question. It is not this cutover, and it is not priced at close to $400 million. A spreadsheet rebuilt from memory can be set aside with the same date on it. Memory is not a tenant. If a column in that sheet is still useful to a deal you are working this week, the column belongs on the opportunity or the activity you already use, under those names. If it is not useful, drop it. Either way, the column is not a migration.
Do not schedule a cutover weekend. The check, if you want one, is a single attempt at the old login, written down, and then abandoned.
5. What is the plan using instead of 2020?
The substitutes are a listing, a rank, and a slice of the acquisition used as a price.
A good answer sounds like a refusal, written by the plan owner, of a listing, a rank, and any use of close to $400 million as a fee.
A bad answer sounds like a link to a listing, funded with a slice of the figure. No listing is invented here. An app, a publisher, a review count, and a price would be an invention. The acquisition figure is not a price for an app. The product was retired. An AppExchange search will not bring it back. A listing is not SalesforceIQ restored. Do not treat a search result as a reversal of 2020, and do not fund the search with a slice of close to $400 million. Ask them to open SalesforceIQ. They cannot. The link stays outside. The figure stays on the acquisition.
Other sales tools exist. They are not named in an order, and they are not ranked. Close to $400 million is not a score, and it is not a budget for a winner. If a slide arrives with ranks, or with the acquisition figure as a price, take both off. The meeting can proceed from 2020 and from the fence around the figure. When the destination is gone and the figure is fenced, the decision is finished. Do not add a listing, a rank, or a percentage of the deal so the plan still has a number on it. The plan is allowed to end.
What stopping actually looks like
All five answers are measured against an alternative, and the alternative is usually left unstated, which flatters a destination and a large number.
State it. Stopping means the plan no longer migrates a retired system, and no longer spends the acquisition. Sales Cloud, if it is needed, gets its own name. The cost of a false move is a phase that configures nothing, priced from a 2014 deal, and a claim that an opportunity is the old workspace returned.
An organisation that fences the figure first can still design current sales work without pretending RelateIQ is in the org.
A good answer sounds like the destination struck, the figure fenced, and any Sales Cloud work retitled, written by the owner of the plan.
A bad answer sounds like we should keep the number so the plan still has weight. The number is a history. Weight is not a reason to spend it.
Where the neighbouring questions live
Notes that are still about the old name sit on the RelateIQ implementation page. The purchase, the rebrand, and the retirement as history sit on what happened to RelateIQ. There is no live product to connect. The page that says so is integrating RelateIQ with Salesforce.
