What happened to Moonhub: it was not an acquisition
The room usually agrees Salesforce bought Moonhub, because a headline said so and a migration plan is already on the calendar. That agreement is the problem: a spokesperson said the company was not acquired.
ChatGPT
Claude
Google AI
Copilot
Platform & ArchitectureA talent leader sees a headline that Salesforce bought an AI hiring tool, and asks for a migration plan by the end of the month. The plan is supposed to move Moonhub data into "the Salesforce hiring product". Recruiting starts a spreadsheet of candidate fields. The room agrees the headline is close enough, and that legal can catch up. That agreement is the problem. The record says the opposite of the headline. Moonhub was not an acquisition.
The sentence to read aloud, and then stop, is the spokesperson's: "A Salesforce spokesperson told TechCrunch that Moonhub has not, in fact, been acquired (by the company’s definition of the term). Rather, Moonhub is shutting down, and only some of the company’s team, not the whole team, as MoonHub implied in its post about the news, will be joining Salesforce."
Read it in pieces. Not acquired, by Salesforce's definition of the term. Shutting down, rather than being folded in as a product. Some of the team, not the whole team. The company's own post, as the report describes it, had implied a fuller move. The spokesperson corrected that implication. The quote uses Moonhub and, once, MoonHub, because that is how the report refers to the post. Files may use either spelling. The spelling does not change the finding.
What follows separates a correction from a purchase. A good answer can say "not acquired" without adding a migration. A spreadsheet of fields is what a general answer becomes.
| Question | Who has to answer it | What a bad answer usually means |
|---|---|---|
| Was Moonhub acquired | The person briefing from the headline, reading the spokesperson | The headline and the denial are averaged into "sort of acquired" |
| Who owns Moonhub | Whoever maintains the acquisitions list | The name stays in the bought column because people joined |
| What is 2 June 2025 | The person drawing the chronology | A report date is filed as a completion |
| Where a price would have come from | Finance, if a number has been attached to the headline | A price is repeated for a sale the spokesperson denied |
| What is shutting down, and where would data go | Whoever is holding the candidate spreadsheet | A company shutdown is treated as a Salesforce product to migrate onto |
Was Moonhub acquired?
No. A spokesperson said Moonhub had not been acquired, by the company's definition of the term. The headline beside the report can still say buy. A headline is not the correction. A buyer who briefs from the headline, and skips the sentence above, will fund a migration the spokesperson's words do not support. If those two texts disagree in a meeting, read the spokesperson's sentence aloud and stop. Do not average them into "sort of acquired".
People joining a company is an employment fact about some of the team. It is not a product transfer. Some people moving across does not bring a hiring application, a tenant, or a data-processing contract with Salesforce. If the organisation was a Moonhub customer, the contract was with Moonhub. What happened to that contract is a question for those papers and for whoever can still answer at a company that was shutting down. It is not a question an implementation partner settles by creating objects.
A good answer sounds like the spokesperson's sentence, dated to the TechCrunch report of 2 June 2025, with the three limits kept intact: not acquired, shutting down, some of the team and not the whole team. The person briefing can say the company's post had implied a fuller move, and that the spokesperson corrected it.
A bad answer sounds like the headline is simpler, so the plan can proceed and the denial can sit in an appendix. Why Salesforce would have acquired Moonhub, and why Moonhub would have sold, are hypotheticals. The record says the acquisition did not happen. Do not write the motive for a deal Salesforce says it did not do. A case study of the purchase would be a case study of a headline. Do not commission one.
Who owns Moonhub?
Salesforce does not own Moonhub. "Is Moonhub owned by Salesforce", "did Salesforce buy Moonhub", and "who owns Moonhub" are one question, and the answer is no. That answer has to be this blunt because the searches assume a yes. An acquisitions list that adds Moonhub as a purchased company is wrong on this source. If such a list is kept, take the name off, or mark the line as not an acquisition and point at the spokesperson. Leaving it in the bought column will recreate the migration plan every time someone sorts the sheet.
Who owns the company, if anyone still does while it shuts down, is not answered by a Salesforce order form. Do not name an owner, a buyer, or a successor product. Name the correction. Some of the team joining Salesforce does not transfer the corporate entity, and it does not transfer candidate data.
A good answer sounds like "not Salesforce", said by the person who owns the acquisitions list, with the row either deleted or labelled not acquired in the same cell as any date. No order-form line is offered, because there is not one.
A bad answer sounds like some of the team joined, so Salesforce owns enough of it to take the data. Joining is not ownership. The report does not name a buyer. Impact on Salesforce customers is easy to overstate. If the organisation is not a Moonhub customer, nothing in the org changed because of this report. If it is a Moonhub customer, the issue is the shutdown of that company, not a new Salesforce hiring module. Do not let a headline convert a vendor shutdown into a Salesforce implementation.
What is 2 June 2025?
The TechCrunch report is 2 June 2025. It is not an acquisition date. "When did Salesforce acquire Moonhub" has no answer, because the acquisition did not occur. People will still type the search. The honest reply is the report date, labelled as a report date, plus the statement that it is not a close.
A good answer sounds like 2 June 2025 written as the date of the TechCrunch report, with "not acquired" in the same cell, and no second date for a product launch, a cutover, or a Salesforce retirement. The person who maintains the chronology can say the week contained a correction, not a release.
A bad answer sounds like 2 June 2025 on an acquisition timeline as a completion, because a date without a label will be quoted later as a purchase. If the name must appear in a chronology of rumours and corrections, the label has to travel with the day. There is no final day, in the sentence quoted here, for the shutdown process itself. Do not invent the final day so a project plan has an end. "Went live" does not apply. Nothing went live in an org on 2 June 2025 on the strength of this report. If a steering slide says the hiring tool landed that week, replace the slide.
Where a price would have come from
There is no Salesforce purchase price, because there was no acquisition. How much Salesforce paid, how much Moonhub was sold for, and the acquisition price are empty questions. Do not answer them with a number from a headline, a clip, or a memory of a different deal. A price implies a sale. The spokesperson denied the sale, by Salesforce's definition. Do not repeat a price even to disagree with it in the same sentence. The disagreement is: there is no price, because there was no acquisition.
A good answer sounds like finance told there is no purchase price, no licence inside Salesforce, and no free trial of a hiring product that was not bought. The person who brought a number can say which headline it came from, and can take it off the brief.
A bad answer sounds like a reaction video named a price, so the price can be minuted as disputed. A DVD, a Reddit thread, a YouTube video, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown. A one-minute explanation that repeats the headline is how the error spreads. A course or a study guide in the Moonhub name would be a curriculum for a product Salesforce did not buy. Do not invent that curriculum. A thread that argues the deal was a bargain is arguing about a sale the spokesperson denied.
There is no Moonhub licence inside Salesforce to look up. Do not send a recruiter to find a replacement and call it the one the deal failed to include. Worth, after a purchase that did not happen, is not a question to score. Correct the assumption. Then there is nothing to score.
What is shutting down, and where would data go?
The company was shutting down. That is not a Salesforce product retirement. A shutdown search mixes a vendor's end with a product Salesforce never put on a retirement list, because Salesforce never bought it. Do not open a change window in a Salesforce org for a Moonhub switch that is not there. Product decline after an acquisition needs both a product and an acquisition. What exists here is a company shutting down, and a denial of the acquisition. Users forced onto Salesforce is the wrong plot as well. Nobody on this source is ordered to move candidates into a Salesforce hiring product.
A good answer sounds like a named person who has looked for an export and can say either what the file holds, who may open it, and whether it should be closed under the rules already used for candidate data, or "none". An empty result is the end of the project. Do not keep a migration line in the plan in case a file turns up later. If a file turns up later, there is still no Salesforce hiring product to pour it into.
A bad answer sounds like migrate, integrate, licence, or hire Moonhub as a Salesforce product, because the headline needs a destination. Do not tell anyone to do those things. A partner who offers a destination object "where Moonhub data should land" is inventing the destination. Refuse the object. Ask, instead, whether any export still exists in the organisation's possession. A demo after an acquisition, a roadmap after an acquisition, and an integration guide would all be documents about a deal that did not happen. Do not draft them. The only employment fact in the quoted sentence is that some of the team, not the whole team, would be joining. Do not name those people, do not count them, and do not list vacancies. A profile is not a source here.
If the spreadsheet of candidate fields is still open, close it. Fields without a file, aimed at a product nobody bought, are a plan that can stop in an afternoon. Stopping it is the work this record supports.
What to do with the answers
Read the five as a set. Specific answers mean the room can say "not acquired" without adding a move. General answers mean the decision rests on a headline, which the spokesperson already corrected.
Whether an export still exists, and what to do with the file if it does, is set out in Moonhub was not acquired, and there is nothing to migrate. If anyone is needed, it is for the file actually held, or for a hiring process already run on tools that can be named. Those tools are not Moonhub.
