# RelateIQ has no org left to implement

RelateIQ was acquired in 2014, rebranded as SalesforceIQ, and retired in 2020. There is no SalesforceIQ org to implement in 2026.

**Published:** 2026-02-11
**Canonical:** https://synconai.com/relateiq-salesforceiq
**Author:** SynconAI Architecture Team

## In short

RelateIQ was acquired in 2014, rebranded as SalesforceIQ, and retired in 2020. There is no SalesforceIQ org to implement in 2026. The acquisition note's price is not your project cost. A quote for an implementation is a quote for a product that is gone. Scope is whatever you can prove you still hold. This page will not print a build price.

## Sources

- **SalesforceIQ** (retrieved 2020-03-13)
  https://en.wikipedia.org/wiki/RelateIQ
  > Acquired by salesforce.com in 2014 for close to $400 million, the company's product was retired in 2020.

## What to take away

- RelateIQ was acquired in 2014, rebranded as SalesforceIQ, and the product was retired in 2020.
- There is no SalesforceIQ org to implement in 2026. A build quote is a quote for a product that is gone.
- The dollar figure in the acquisition note is not your implementation cost.
- A partner passes by refusing the implementation and by not pretending a current sales org is SalesforceIQ.

## The guide

A hiring plan for the year asks for a SalesforceIQ consultant. The requisition says implementation. The hiring manager wants an org configured, data loaded, and a team trained, and they want a quote from a partner who has done it before. There is no org to configure. RelateIQ was acquired, the product was rebranded SalesforceIQ, and the product was retired. A requisition cannot un-retire it. A partner who prices the requisition as written is pricing a system that does not exist in 2026.

The plan feels ordinary because the name still sits in an old architecture diagram, next to the sales process, as if it were a box you could staff. The box is a label from a product that ended. Staffing it recreates the label. It does not recreate the product.

## What the note actually says

The acquisition and the ending are in one sentence: "Acquired by salesforce.com in 2014 for close to $400 million, the company's product was retired in 2020." Acquired in 2014. Rebranded, in the history teams still repeat, as SalesforceIQ. Retired in 2020. This page uses those facts and does not add a month the sentence does not give. If you need a finer date for a contract dispute, you need the contract and counsel, not a finer date invented by a project manager.

The sentence contains a dollar figure for the acquisition. That figure is about the deal. It is not a budget for your work, not a rate card, and not a fraction you may apply to a statement of work. This page will not turn it into a price. Anyone who quotes you a percentage of that figure as "typical implementation cost" is inventing a commercial model from an acquisition note. Send that model back. Your cost, if you have one, is the inventory below. It is not a slice of someone else's purchase price.

SalesforceIQ is the name the product wore after RelateIQ. It is not a second product that survived the retirement. You do not migrate RelateIQ into SalesforceIQ in 2026. You would be migrating into a name that was retired with the product. A quote that still offers that hop has not read the ending. There is no SalesforceIQ org to implement. There is no sandbox of it waiting for a refresh. There is no consultant login that makes it current.

## What people try to substitute

A sales team still has to work. That fact does not resurrect SalesforceIQ. If the organisation sells with a CRM you can open today, name that CRM. If you cannot open it, you do not have a silent SalesforceIQ in the corner. You have a gap in your own inventory. This page will not tell you the old records moved into any particular cloud. It will not tell you they are waiting in an export you have not found. Found files are files. Unfound files are not a scope line called data migration.

Do not let a diagram heal the gap by drawing an arrow from SalesforceIQ to whatever you use now and calling the arrow a project. An arrow is a claim that someone should check. Who copied what, when, under what instruction. If nobody can answer, the arrow comes off. The current system stands on its own implementation, with its own objects, if you decide to change it. That decision is not a RelateIQ implementation. Writing RelateIQ on the purchase order so the old diagram looks finished is how the retired name starts invoicing again.

Krux is a different product with a similar procurement reflex: people still ask to migrate into something that has ended. The reflex is described in [the Krux guide](/krux-audience-studio-retirement). The dates are different. The refusal is the same shape. Do not let one partner sell you a bundle of retired names, RelateIQ plus a DMP plus a social tool, as a single legacy programme. Each ended on its own notice. Each inventory is its own short job. A bundle hides the fact that none of them is a build.

## What a number could be made of

This page will not print a price. Implementation cost, for a product retired in 2020, is a phrase that should collapse when you say it aloud. If money is still at stake, it is because paper or habit remains, not because an org needs building.

Scope is what you can prove. Old contracts that say RelateIQ or SalesforceIQ. Invoices that, improbably, still mention them. Exports on a disk, dated, with a person who understands the columns. Logins attempted, and the result. Architecture diagrams that still show the box. The scope's main exclusion is an implementation. Write "no SalesforceIQ org" in the first line so a template cannot add environments, user licences, and a training plan. Training on a retired product is not enablement. It is a course in a system the class cannot enter.

Licences are any charge that still uses the name. Expect, in many organisations, to find nothing. Nothing is a result. Record it. If a reseller bundle still carries the words, the contract owner asks what the charge is actually for, in the current year, against the current paper. This page will not interpret the bundle for you. It will not tell you that you owe a migration fee in lieu of a licence. A migration fee for a missing org is not a licence. It is a mistake.

People are the person who wrote the requisition, the person who owns the diagram, and anyone who still keeps a spreadsheet they call the SalesforceIQ extract. They need a meeting that cancels the requisition. That meeting is internal time, and it is the real cost if the hiring process has already started. A partner can help find files. A partner cannot be the reason you hire a team to configure nothing. Stop the requisition first. Then see if any file hunt remains. Most of the time the hunt is an afternoon, and the afternoon does not need a statement of work.

Cutover is the wrong word, and it should not appear as a phase. There is no weekend when SalesforceIQ goes live, because it will not go live. There is no weekend when it "finally" moves, because this page does not name a destination for it. The ending is the requisition withdrawn, the diagram corrected, and the invoices checked. Done is a short list. A cutover plan with hypercare is a plan for a product you do not have. Hypercare on nothing is how a retired name gets a support retainer. Decline the retainer.

## The test, instead of a hire

The search for the best RelateIQ agency, or for a SalesforceIQ implementation partner, is a search for a role that the retirement ended. Do not rank SynconAI. Do not rank a CV that lists the product as a present-tense skill. A past skill can be real. It is not a current org. The test is whether they can say the product was retired in 2020, say there is nothing to implement in 2026, and say what they will not take on.

They will not take on an implementation. They will not take on a data migration into SalesforceIQ. They will not take on the acquisition price as a way to estimate your fee. They will not tell you your current sales process is secretly SalesforceIQ under a new logo. They will not sign off what you may do with old contact files. Old contact files, if you have them, are a question for the people who own privacy duties, with the file in hand. A delivery partner does not close that question by loading the file into a system that is not there.

If you need help, it is an inventory, capped, after you have cancelled the hiring plan. Call it an inventory. If the only firms who reply are firms who want to implement, you have learned that the brief escaped. Tighten the brief. You do not need a partner who fails a clearer test. You need the test written at the top, where a sales engineer cannot miss it.

## What to do with the proposal and the requisition

| Line they wrote | What it actually is | What you send back |
| --- | --- | --- |
| Implement SalesforceIQ | An org that was retired in 2020 | Withdraw the work. There is nothing to configure in 2026 |
| Migrate RelateIQ into SalesforceIQ | Two names for a product that ended | Delete the hop. Both names are history |
| Fee based on the acquisition price | A deal figure used as your budget | Refuse it. The figure is not your cost |
| Map it into the CRM you use now | An arrow nobody has evidenced | Ask who copied what, and when. If nobody knows, remove the arrow |
| One programme for retired products | Several endings bundled as a build | Split them. Each notice stands alone. None of them is this build |

::: warn
Do not hire anyone to implement SalesforceIQ in 2026. RelateIQ was rebranded to that name, and the product was retired in 2020. There is no org. A quote that provides environments, a load, and training is a quote for a product that is not there.
:::

Replace the requisition with a paragraph. RelateIQ was acquired in 2014 and later called SalesforceIQ. The product was retired in 2020. We will not implement it. We will not treat the acquisition price as a project budget. We will look for contracts, invoices, and dated exports, and we will correct diagrams that still show the box. If you propose a build, you have not accepted the paragraph.

Then do the look. File what you find. Correct the diagram. Tell the hiring manager the role is closed because the product is closed. That is the whole delivery. It will not feel like a transformation, which is how you know it matches the facts. A transformation, sold on top of a retirement, is a way to spend the year configuring a name. You do not have the year for that, and you do not have the org.

If the sales team needs a change to the system they actually use, write that change without the words RelateIQ or SalesforceIQ in the solution. Those words can appear once, in a footnote that says the old product was retired and is not this project. A footnote is plenty. A workstream is too much. The partner you want, if a real sales system needs work, is a partner for that system. They pass a different test, on objects you can open this week. They do not pass it by remembering SalesforceIQ.

Leave the acquisition sentence in the folder so the next requisition dies faster. The sentence is enough. It has the year of the deal, the fact of the retirement, and a price that belongs to the deal alone. Anyone who needs more than that, before they stop, is asking for permission to build. Do not give it.

If a seller still has a login bookmark, try it once, with a witness, and write down what the screen actually does. A redirect, an error, or a marketing page is not an org. A password that nobody can find is not an org either. Record the attempt in the inventory so the next hiring manager does not repeat it. Then take the bookmark off the shared drive, or label it retired, so it stops looking like a system you support. Support implies a place to raise a ticket. There is nowhere to send the ticket. Saying that plainly is kinder than a quarter of workshops that end in the same error.

Do not rebuild the old relationship graph from memory in a spreadsheet and call the spreadsheet SalesforceIQ. Memory is not a migration. If a column matters to a live sales process, it belongs in the system you can open, under that system's name, with an owner. If it does not matter, delete the column from the conversation. The retired product does not get a shadow copy so that the old name can remain true. The old name stopped being a product in 2020. The spreadsheet would only pretend otherwise, and pretence is what the requisition already tried to buy.

## The other searches

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


## Questions

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

It should say RelateIQ was rebranded SalesforceIQ and retired in 2020, and that there is no org to migrate into in 2026. It should list contracts, invoices, and dated exports you already hold. It should exclude an implementation. It should not turn the acquisition price into your budget. Split scope, any remaining licences, people, and the stop.

### What is a RelateIQ or SalesforceIQ implementation cost made of?

Not a build. There is no SalesforceIQ org to implement. Any real cost is an inventory of paper and files, internal time to cancel a hiring plan, and a check that you are not still being billed for the name. This page will not print a figure, and it will not derive one from the acquisition note.

### Can a partner implement SalesforceIQ now?

No. RelateIQ was acquired in 2014, the product was rebranded SalesforceIQ, and it was retired in 2020. An implementation in 2026 has nowhere to land. Environments, loads, and training for that name are a quote for a product that is gone. Ask the partner to refuse the work.

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

Do not rank agencies, including SynconAI. A partner passes if they say the product was retired, refuse to implement it, refuse to price from the acquisition figure, and refuse to pretend your current sales org is SalesforceIQ. A present-tense case study does not pass.

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

Do not hire an implementation partner. Cancel that requisition. If files and contracts are hard to find, hire a capped inventory after the role is withdrawn. If your live sales system needs work, hire for that system under its own name. SalesforceIQ is not that name.

### Is relateiq owned by Salesforce?

It was. Salesforce bought RelateIQ in 2014. The full account is at https://synconai.com/what-happened-to-relateiq.

### When did Salesforce acquire relateiq?

2014. It was rebranded SalesforceIQ and the product was retired in 2020.

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

There is no SalesforceIQ org to implement in 2026.

### Should I migrate from relateiq to Salesforce?

Do not migrate onto SalesforceIQ. The work, if you still need it, is a Sales Cloud design, which is a different product.

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

The page this guide cites says the acquisition was close to $400 million. That is not a licence fee, and it is not a price you can buy today. The licence read is at https://synconai.com/relateiq-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: Sales Cloud (https://synconai.com/salesforce-sales-cloud-consulting).