Integrating RelateIQ with Salesforce

A diagram still has a box called RelateIQ, with an arrow into the CRM the team uses now. The arrow is labelled integration, as if the retired product were a feed you could turn back on. SalesforceIQ was retired in 2020. Do not integrate a retired product. Sales Cloud is not a restore of it. The arrow cannot land, because there is no SalesforceIQ org to receive or to send the call. The diagram is a poster of a product that has been gone for years. Taking the arrow off is the integration work. Drawing it more carefully is not.

The seller who still has a bookmark has not produced an org. A bookmark is not a system. This page says what you do with the connector request. You refuse it. You do not price it from the old acquisition.

#The app

There is no app. The sentence this page cites holds the purchase and the ending, and it is quoted once: "Acquired by salesforce.com in 2014 for close to $400 million, the company's product was retired in 2020."

Read the ending before the figure. The product was retired in 2020. SalesforceIQ is the name it wore. RelateIQ is the earlier name. They are not two apps you connect. A search for a Salesforce RelateIQ app is a search for a product that was retired. It is not a search for Sales Cloud. Sales Cloud is not a restore of RelateIQ. If your organisation sells with a CRM you can open today, that CRM has its own name. Write that name if you must draw it. Do not write SalesforceIQ underneath as if the old box were still inside.

The figure in the quoted sentence is the old acquisition. It is close to $400 million in that sentence, and that is the only way this page cites it. It is not a licence. It is not an integration cost. It is not a budget for a connector, a fraction you may apply to a statement of work, or a rate for "typical" work. Anyone who prices the arrow as a portion of that figure has used an acquisition note as a rate card. Send the rate card back. This page will not repeat the figure as a fee, because it is not a fee.

There is no sandbox of SalesforceIQ waiting for a refresh. There is no consultant login that makes 2020 current. Try a bookmark once, with a witness, if you must kill the rumour. A redirect, an error, or a marketing page is not an app. Write what the screen did. Then take the bookmark off the shared list, or label it retired, so it stops looking like a system you integrate.

#The connector

Do not integrate a retired product. The connector people still request is a sync of contacts, messages, or a relationship view from SalesforceIQ into the CRM they use now, or the reverse. Both directions need an org that can take the call. The org was retired in 2020. The call cannot land. Building the sync "so the old relationships are not lost" assumes a store you have not shown. Unshown stores do not get connectors. They get a search of the files you actually have, and that search is the other page.

Sales Cloud is not a restore. Pointing the arrow at Sales Cloud does not revive SalesforceIQ inside it. It proposes a load into a different product, under a false history. If Sales Cloud needs a change, that change is scoped as Sales Cloud, on its own objects, with its own failure, and without the retired name in the solution. A footnote may say the old product was retired and is not this project. A connector may not.

This page does not name an API, a daily cap, a middleware SKU, or an integration price. The cited sentence does not name them. The only money in the sentence is the old acquisition, and it stays there. Do not turn it into a connector licence. Do not invent a call pattern so the retired org looks reachable. Reachable is a claim. Open the org or withdraw the claim. You will not open it. Withdraw the connector.

Write one line. We will not integrate RelateIQ. We will not integrate SalesforceIQ. We will not treat Sales Cloud as a restore. Put the line on the diagram in place of the arrow. A blank line is how the arrow returns at the next steering group. The refusal has to be visible.

#The architecture

The architecture is a retired box and no arrow. A Salesforce RelateIQ architecture diagram that shows data moving in 2026 describes a call that cannot land. Cross the box out. Write the retirement year. If Sales Cloud is on the same page for a current sales process, draw it as itself, with no line from the dead box. A line is a claim that someone should be able to name the object and the failure. They cannot name a live SalesforceIQ object. The line fails the test. Remove it.

A guide book is not a map of the old relationship graph. People search for a Salesforce RelateIQ integration guide book because the product was once a story they heard. This page will not invent the book, and it will not reconstruct the graph from memory. Memory is not a connector. A spreadsheet of remembered relationships, labelled SalesforceIQ, is a shadow copy. Do not build the shadow so the old name can remain true.

The acquisition figure does not appear on the diagram as a cost, a licence, or a sizing input. If you mention it at all, mention it as the old acquisition, in the words the quoted sentence already uses, and then leave it out of the design. Design does not get more accurate because a deal was large. The deal is over. The product is retired. The picture should be small.

Do not add a middleware box "in case the org comes back". It will not come back on this page. A box held for a return is the connector, delayed. Delay is not a refusal. Write the refusal.

#When the call does not land

The failure is a call that cannot land. There is no degraded mode and no retry that brings 2020 back. If a job still attempts a login, an extract, or a push under the RelateIQ or SalesforceIQ name, stop the job. Write the retirement year as the cause. Do not retarget the job at Sales Cloud and call the retarget a successful failover. Failover into a different product is the restore. Sales Cloud is not a restore of RelateIQ.

If no job exists, the proposed call is still a failure you can name in advance. It cannot land. Record the proposal as refused so it does not sit in a backlog under "legacy integration". Legacy, in that heading, sounds like patience. It is a request to integrate a retired product. The heading has to go, not the date.

Do not invent an error code, a record count, or a match rate against an org you cannot open. If you tried the bookmark, write what the screen showed and who saw it. That note is the status. A count you estimated from the acquisition figure is not a status. The figure is not a volume, not a licence, and not an integration cost. Leave it in the quotation. Do not do arithmetic on it.

A seller who kept a personal export has a file. The file is not a landed call. It does not prove the connector should be rebuilt so the file can "stay current". Current ended in 2020. The file gets a date and a person, on the implementation page's terms, or it stays in a drawer. It does not get a schedule.

#An integration names three things

An integration exists only when the page can name the system, the object, and what happens when the call fails. A diagram that does not name those three is a poster.

This page cannot name a live SalesforceIQ system. It cannot name a live object the call would write or read. It can name the failure: the call cannot land, because the product was retired in 2020. Two gaps out of three means the integration does not exist. Do not fill the gaps with Sales Cloud and a contact record and call the result RelateIQ. That filling is the restore. Sales Cloud may have contacts. Those contacts are not a retired product's feed. They are Sales Cloud, if that is the CRM you actually open.

The same test rejects a priced connector. A fee, especially one derived from the old acquisition, does not create a system. The figure in the quotation is the purchase. You may not cite it as a licence. You may not cite it as what the connector costs. Once the quotation has carried it, you do not need it again on a slide.

Keep the table where the diagram was. A partner who draws the arrow back has failed, even if the arrow is dotted, even if it says one-time. One-time is still a call. The call cannot land. Dotted lines are how posters apologise. Take the line off, dotted or not.

#The other two pages

This page is not the implementation page, and it is not the page about what happened. The fact there is no org to implement is on the RelateIQ implementation page. The acquisition and the retirement as history are on what happened to RelateIQ. Stay here when the question is the app, the connector, the architecture, and the call that cannot land.

The implementation page is where a hiring plan gets withdrawn. This page is where the connector gets refused. They meet, and they do not become one project. Link them. Do not add a fee that uses the acquisition figure as the bridge. The figure stays in the quoted sentence, as the old purchase, on the history of the deal. It is not the cost of either page.

A partner who brings a guide book of sync jobs has brought the arrow. Ask them to open SalesforceIQ this week and show the object they will call. They cannot. If they open Sales Cloud instead, they are in a different product. Let them talk about that product under its own name, or stop. They do not get to call the visit a RelateIQ integration. Sales Cloud is not a restore.

Remove the arrow. Label the box retired in 2020. Stop any job that still uses the name. If the sales team needs a change, write it without RelateIQ or SalesforceIQ in the solution. Keep the quoted sentence in the folder so the next diagram dies faster. The sentence has the retirement and a figure that belongs only to the old acquisition. Anyone who needs more than that, before they stop, is asking to build. Do not give them the build.