# Integrating Acumen Solutions with Salesforce Acumen Solutions was a services firm, not a product. There is nothing to integrate, and there is no licence. **Published:** 2026-09-07 **Canonical:** https://synconai.com/integrating-acumen-solutions-with-salesforce **Author:** SynconAI Architecture Team ## In short Acumen Solutions was a services firm, not a product. Salesforce closed the acquisition on 1 February 2021, and the firm became part of Salesforce Professional Services. There is nothing to integrate and no licence. The failure is a connector project that invents a system so a template has a left-hand side. ## Sources - **Salesforce Closes Acquisition of Acumen Solutions** (retrieved 2021-02-01) https://www.salesforce.com/news/stories/salesforce-acumen-close-updates/ > Acumen Solutions will become part of Salesforce Professional Services, which along with Salesforce partners, helps customers accelerate their time to value. ## What to take away - Acumen Solutions was a services firm, not a product. There is nothing to integrate. - There is no licence to assign, and no Acumen object to map. - The failure is a connector project. It invents a system so the statement of work looks familiar. - The right job is Salesforce delivery against systems you actually run, scoped in writing. ## The guide A partner sends a one-page architecture before the first workshop. Acumen sits on the left. Salesforce sits on the right. An arrow between them is labelled integration. The statement of work has a line for the connector, a line for field mapping, and a line for a licence. Nobody in the room can say what Acumen stored, because Acumen did not store it. The firm sold people's time. The arrow is a habit from a different kind of deal. Say that plainly, then keep saying it until the arrow is gone. There is nothing to integrate. There is no licence. A connector project would be the wrong job. This page is about why the job keeps getting sold anyway, and what to put in its place so the week is not wasted on a blank system. The delivery work that is actually in front of a Salesforce programme is [Acumen Solutions joined Salesforce services, not your data map](/acumen-solutions-salesforce-services). The close itself is [What happened to Acumen Solutions](/what-happened-to-acumen-solutions). Use those when you need the services scope or the corporate record. Stay here while anyone is still drawing a connector. ## What the cited page says The sentence this page quotes is the close notice: "Acumen Solutions will become part of Salesforce Professional Services, which along with Salesforce partners, helps customers accelerate their time to value." The close is 1 February 2021. Read the nouns. Acumen becomes part of Salesforce Professional Services. Partners are still in the sentence. The help described is delivery, from Salesforce's own services arm and from partners. A services firm is not a product. It does not become a product because a diagram needs a box. There is no Acumen system on the left of a responsible picture. There is no Acumen object to map. There is no licence to turn on, to assign, or to renew. If a seller offers an Acumen licence, ask them to show the order form line. This source does not contain one. A line invented so procurement has a SKU is the connector project in commercial clothes. "Will become" is the tense of the sentence as published. For a buyer now, the practical reading is that you do not engage Acumen Solutions as a separate firm with a product to implement. You engage Salesforce delivery, or a partner, for Salesforce work. Former staff, former methods, and a former client relationship are not a system. Employment history does not create an object you can sync. The sentence does not name a screen, an API, a daily cap, a price, or a connector. This page will not invent them to sound specific. Specific, here, means being exact about the absence. ## The system The system cell is empty, and the empty cell is the design. People hate an empty cell. A template asks for a source system. A workshop asks what you are migrating from. A partner's estimator asks for record counts. Each question assumes a left-hand side. When the left-hand side is a services firm, the honest answer is that there is no source system under this name. The template does not have a box for that answer, so someone types "Acumen" and the project continues. That typing is the moment the wrong job starts. Search your own estate before you argue from memory. Look for an Acumen tenant, an Acumen connected app, an Acumen line on a licence report, a login nobody can explain. The expected result, on this source, is that you do not find a product. Write the search down, including who looked and what they opened. A finding of nothing is a result. It is the system cell, filled in as "none". Do not replace "none" with a guessed platform because the search felt too short to justify the meeting. If you do find something with the word Acumen on it, read it before you celebrate a source system. A folder of old proposals, a contact, a logo on a slide from 2020, or a consulting statement of work is not a product to connect. It is paper. Paper can be filed. Paper is not an integration. If you find a real application that a project happened to nickname Acumen, that application has its own name and its own owner. Use those. Do not launder it through this acquisition so the connector keyword still fits. Salesforce is a system you may already run. It is not "the Acumen side, after the move". Nothing moved. There was no store to move. Your org is your org. Work you hire is work on that org, scoped to objects you actually have. ## The object The object cell is empty for the same reason. There is no Acumen object. A connector project will invent one so the mapping sheet has rows. You will see proposed objects with sensible-sounding names: client, engagement, consultant, timesheet. They look like a data model because every services firm has clients and timesheets in the ordinary world. Ordinary words are not a schema this source gives you. Mapping those invented objects into Salesforce accounts and projects is work you created by drawing the arrow. It is not work the close requires. There is no licence, so there is no entitlement to grant either. Nobody needs special access for an Acumen app, because this page cannot name an Acumen app. A security review that asks who can access the Acumen connector is reviewing a fiction. Answer the review by deleting the connector. Do not answer it by designing roles for a product you do not have. If your company was a client of the firm before the close, you may still have deliverables: a design, a configuration, a backlog. Those artefacts live in whatever store you kept them in. They are documents about Salesforce work. They are not rows in an Acumen database waiting for a pipe. Treat them as project history. Give them an owner. Do not promote them into a source system so a migration line can survive. The object you do have, if you have a Salesforce programme at all, is the Salesforce object you were already going to change. An account, a case, a custom object your org already uses. Name it from your org. If you cannot name it, you do not have an integration scope. You have a keyword. ## The failure The failure is the connector project. Not a failed sync. The project itself. It is the wrong job, and it fails by existing. Watch how it gets funded. Someone searches for an integration connector and an architecture diagram. The search results are full of pages that assume a product. A partner recognises the shape and replies with the shape. The reply has phases: discover the source, map the fields, build the connector, reconcile the rows, hypercare. Hypercare for a source that is not there is a calendar pretending to be engineering. Each phase has a fee. The fees look like a market. They are three firms pricing an object that is not there, which is the comparison you should stop. The project then consumes real things. Sandbox time. A mapping workshop. A middleware conversation. A login someone creates so the connector has a home. An error queue for failures that cannot happen, because there is no feed. A test script that loads sample rows nobody is allowed to have invented. Sample rows are the failure becoming data. If a sandbox already has them, treat them as made-up records, not as a head start. List who can see them. Stop further loads. Ask the person who owns data quality whether the sample should be removed. Nobody is served by a softer version of the same job. "A light connector." "A read-only connector." "A connector we might need later." Later does not create a system. Read-only does not create an object. Light still needs a source. If the source is empty, the connector has nothing to do, and the fee is for the drawing. ## The diagram A diagram that does not name the system, the object, and the failure is a poster. For this deal, a poster usually shows two logos and an arrow. That poster is the sales tool for the wrong job. The diagram you are allowed to keep names the absence. | Label | What this integration names | | --- | --- | | System | None. Acumen Solutions was a services firm. There is no system to connect. | | Object | None. There is no Acumen object and no licence. | | Failure | A connector project that invents both, so a template can be filled. | Pin this table to the front of any proposal. If a later page contradicts it, the later page is wrong. Do not "balance" the table with an architecture that puts the arrow back in for stakeholders who like pictures. Those stakeholders can read three cells. If they cannot, the picture will not save them. It will only give the connector a place to hide. There is no screen to redraw and no connector name to typeset in a corner. Adding either would be the failure, illustrated. ## Why the connector keeps looking like the job The keyword asks for an app, an architecture diagram, an integration, a connector, and a guide. Those words are a buying pattern for products. Acumen does not fit the pattern. The pattern does not notice. It sends the same brief it would send for a tool with an API. Your defence is to answer the brief with the empty cells, in writing, before anyone estimates. Field mapping is the most convincing part of the wrong job, because it looks like analysis. Two columns. Source field. Target field. Workshops love it. Refuse the sheet until someone can open the source field in a system they can name. If they cannot open it, the sheet is fiction, however neat the columns are. Target fields in your real org can still be discussed, as ordinary Salesforce design, without a fake source. That discussion is delivery. It is not an Acumen integration. Licence conversations are the commercial twin. Procurement asks which SKU. The honest answer is that there is no Acumen licence. If the programme needs Salesforce licences you already know how to buy, name those products as themselves. Do not bundle them under an Acumen banner so the acquisition looks implemented. Implemented, here, would mean you hired people to do Salesforce work. It would not mean you connected a firm. ## What you write instead Write the refusal, then write the real scope, if you have one. The refusal. One paragraph. Acumen Solutions was a services firm. The close put that firm inside Salesforce Professional Services, alongside partners. There is nothing to integrate and no licence. This programme will not buy a connector. The search. Who looked for a tenant, a connected app, a licence line, and a login. What they found. "Nothing" is an acceptable finding. Date it. The real systems. The Salesforce org you run, and any other system you actually intend to change, each with an owner. If the list is only "we might want a partner", say that. A partner is not a connector. The decisions still open. Which objects you might change. Which reports are wrong. Who signs the scope. Blanks stay blank. A blank is cheaper than a fictional source that fills it. The commercial shape. Salesforce Professional Services, a partner, or both for different pieces, which is how the close notice is written. Ask any firm that employs former Acumen people to scope your org. The employment history is not a system, and it is not a reason to draw an arrow. Out of scope. A connector. A mapping from an Acumen object. A licence. Sample data created so a demo has rows. A win rate, a price, or a daily cap for an API this page cannot name. ## How the other two pages fit This page exists so the connector dies in the open. The neighbouring pages answer different questions, and they should not be asked to smuggle the arrow back in. [What happened to Acumen Solutions](/what-happened-to-acumen-solutions) is the close. The day, the owner, and what was not published. Send the corporate argument there. Do not let a timeline grow a cutover date. There is nothing to cut over. [Acumen Solutions joined Salesforce services, not your data map](/acumen-solutions-salesforce-services) is the page that turns the keyword into delivery. What a quote should list when the quote is for Salesforce work, and how to test a firm that still arrives with an Acumen source. Use it when this diagram is accepted and you still have a programme. If you do not have a programme, you do not need a connector to prove the acquisition was real. The acquisition was a services deal. It is already real without an arrow. :::warn There is nothing to integrate, and there is no licence. Do not start a connector project to give the architecture a left-hand side. A services firm does not become a source system because a template has a column for one. ::: ## A week that ends with an empty cell Spend the week on the search and the refusal, not on a prototype. Ask the licence owner, the integration owner, and anyone who was a client of the firm. Write what each of them can actually open. If the answer is a document, file the document. If the answer is a person who now works inside Salesforce delivery, that is a staffing fact. It is not a tenant. Then read the next proposal from the back. If it still has a connector, a mapping sheet, or a licence, return it with the diagram attached. You do not need a counter-design. The three cells are the counter-design. System, none. Object, none. Failure, the connector project. When those cells are filled, and the proposal has been sent back, the integration question is answered. The answer is that you will not build one. Any Salesforce work that remains is ordinary delivery, on systems you could name before this acquisition ever came up. ## Questions ### What do we connect when we integrate Acumen Solutions with Salesforce? Nothing. Acumen Solutions was a services firm, not a product. The close on 1 February 2021 put the firm into Salesforce Professional Services. There is no system, no object, and no licence. A connector would invent all three so a template looks complete. ### Is there an Acumen licence to assign? No. This source does not describe a product you turn on. If procurement asks for a SKU, the honest answer is that there is no Acumen licence. Buy Salesforce products you can name, as themselves, when you actually need them. Do not hide them under an Acumen banner. ### Why do proposals still include a connector? The buying pattern for an integration assumes a source system, a mapping, and a feed. That pattern does not notice when the acquired firm sold services. Phases and fees then appear for a left-hand side that is not there. Send the proposal back with the empty diagram. ### We were an Acumen client before 2021. What is the integration? There still is not one. You may have documents and a relationship. Those are project history, not a database to sync. Ongoing work is Salesforce delivery, from Salesforce Professional Services, a partner, or both. Ask the firm to scope your org. Do not ask them to connect Acumen. ### Which page covers delivery, and which covers the close? Delivery against a real Salesforce scope is the Acumen services page. The close is the what-happened page. This page is the diagram that refuses the connector: no system, no object, and the failure of inventing both. --- 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: Salesforce consultancy (https://synconai.com/salesforce-consultancy).