ChatGPT
Claude
Google AI
Copilot
A people-operations lead sees a headline that sounds like a purchase and opens a migration ticket the same day. The ticket says to move Moonhub onto Salesforce, because that is what you do when Salesforce buys a tool you might have used. The headline is not the record this page stands on. Moonhub was not acquired. There is no hiring product to move onto. Do not tell anyone to migrate Moonhub onto Salesforce.
The ticket feels responsible. It has a source system, a target, and a date. The target is a product this source does not contain. The date is a report date, not a cutover. Closing the ticket is the work. Writing a field mapping is how the mistake gets a project code.
Should you migrate
No. Do not migrate Moonhub onto Salesforce. A migration needs a destination that can hold the thing you are moving. Hiring data, if you have any, would need a hiring system. This page cannot name a Salesforce hiring product that received Moonhub, because the deal the headline suggested did not happen. Moving candidates, roles, or score notes into accounts and contacts would be a new design you invented in a CRM. It would not be a migration this acquisition failed to provide. There was no acquisition to fail.
If your company used Moonhub, the practical question is whether an export still exists, and who holds it. That question goes to the people who administered the tenant, if you can still find them. It does not go to a Salesforce implementation plan. An export, if it exists, is a file you keep under your own retention rules. It is not a load file for an object this page does not name.
If your company did not use Moonhub, there is nothing to move and nobody to notify. The report is news about a company and a correction. It is not an instruction to your org. Do not create a sandbox "in case the data turns up". Data that turns up later can be discussed then, against a system you have chosen on purpose. A sandbox created from a headline will be filled, because empty sandboxes attract spreadsheets.
The walkthrough is a stop. Confirm the report. Confirm you are not buying a hiring SKU as a result. Confirm you are not mapping candidates to contacts. Then close the ticket. A walkthrough that continues into a data load has left this page.
What the report actually says
This page quotes the report once, unchanged: "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 the definition clause. Not acquired, by the company's definition of the term. A headline that says "buys" is not the definition the spokesperson gave. Use the spokesperson's sentence in the steering pack. Do not soften it into "a sort of acquisition" or "an acquihire you should migrate". Those phrases are how a correction gets undone by a project plan.
The report is dated 2 June 2025. That is the date of the article. It is not an acquisition date, because there was no acquisition. It is not a date this page will treat as the day a product was switched off. The sentence says the company is shutting down. It does not give a calendar day for the last login. Do not invent that day. If you need to know whether a tenant you held still opens, ask the person who held the password. You cannot read the answer off the article.
Only some of the team were joining Salesforce. Not the whole team. A team joining an employer is employment. It is not a product moving house. Do not brief the room that the people brought a hiring application with them. The sentence does not say that. People and software are different nouns. Keep them apart.
What the software is now, on this source, is a company that was shutting down, not a Salesforce module. There is no Moonhub screen inside Salesforce established here. There is no licence. There is no purchase price, because there was no purchase. A reported commercial figure, if you have seen one elsewhere, is not used on this page.
There is no hiring product to move onto
Salesforce, in the org you administer, holds accounts, contacts, and the other objects your contract includes. Those objects can be bent into a hiring tracker by someone determined to avoid buying a hiring system. Bending them is a design. It is a poor one if the only prompt was this headline, and it is not a migration from Moonhub. Candidates have consent, retention, and access rules that a contact record does not satisfy just because both have a name and an email address.
Do not load resumes into files on contacts. Do not create a custom object called Candidate and call it the destination. Do not ask an implementation partner to "receive the Moonhub data" into Sales Cloud. Each of those sentences tells someone to migrate Moonhub onto Salesforce. This page is telling you not to.
If you already run a hiring system, that system is the place hiring data belongs. This page does not name it, and it does not rank it against anything else. The point is that the destination, if you need one, is a system you chose for hiring, under its own contract. It is not an object you create this week so a failed headline has a home.
The spokesperson's correction also limits the story you tell candidates and staff. Do not announce that their hiring tool is now Salesforce. That announcement is false on this source, and it creates a support burden you cannot meet, because there is no product to log into. Say the quieter thing. The company was not acquired. If we used the tool, we are asking whether an export exists. Salesforce is not the new front door.
Versus native features
Native Salesforce features do the jobs your org is configured for. They do not, on this source, include a hiring product that replaced Moonhub. There is nothing to compare feature by feature. A comparison table that lists "Moonhub sourcing" beside "Salesforce contacts" has already decided to migrate. This page will not draw that table as if the columns were equivalent.
What native features do well is keep a customer and a deal, under permissions a sales or service team understands. A candidate is not a customer merely because you might one day sell to them. Mixing those records corrupts both. The salesperson sees a person who did not agree to be in a pipeline. The candidate's data sits in a system whose retention was written for buyers, not for applicants.
This page does not rank a dedicated hiring system against Sales Cloud, because that ranking is a product decision this source does not contain, and because ranking would pick a winner. The only comparison on offer is categorical. Hiring work stays in a hiring process. CRM work stays in the CRM. A headline does not merge the categories.
| Job | What this record says | What native CRM features do | What you still write |
|---|---|---|---|
| Treat the headline as a purchase | The spokesperson said it was not an acquisition | Nothing in the org changes because of a headline | A correction in the steering notes |
| Move candidates into Salesforce | No hiring product to move onto | Contacts are not a hiring system | A refusal. Do not load them |
| Find a Moonhub menu in the org | Not established by this source | Your menus reflect what you bought | Do not file a ticket to reveal a hidden app |
| Keep an export if you were a customer | The article does not describe your tenant | Files you store are your retention problem | Ask the old admin, outside this project |
Leave the CRM column alone. Adding a build task to it is the migration in disguise.
Alternatives, with no order
The AppExchange search assumes a product you are replacing. This page does not name a listing, a publisher, or a rank. It will not recommend a hiring app. Recommending one would tell you where to migrate, which this page refuses to do. The options are administrative. They are not ordered.
If you never used Moonhub, close the ticket and do not buy anything as a consequence of the article. That option fits the majority of readers. The article is not a gap in your stack.
If you did use it, ask whether an export exists, and store that export under the retention rule you already apply to applicant data. That option is housekeeping. It does not include a Salesforce load.
Keep hiring in the system you already use for hiring, if you have one. That option fits a team with a live process. This page does not name that system and does not compare it with others.
Pause any Salesforce build that was justified only by this headline. Pausing is a decision. The build can be reopened later under a hiring requirement you wrote yourselves, with a vendor you chose for that requirement. It should not be reopened under the Moonhub name.
A partner who arrives with a ranked shortlist of hiring tools, and a mapping into contacts, has brought both a rank and a destination this page will not endorse. Ask them to take the mapping away. If they still have a useful question about your CRM, it will not depend on Moonhub. If every slide depends on Moonhub, end the conversation.
What the walkthrough contains
The walkthrough is the opposite of a cutover.
Write the correction at the top. Moonhub was not acquired. Use the spokesperson's definition, not the headline. You do not need to paste the whole article into the pack. You do need the room to hear that the purchase did not happen.
Write the date of the report, 2 June 2025, and label it as a report date. Do not relabel it as a shutdown date or a migration date. This page does not invent a last day.
Write the destination as none. There is no hiring product to move onto. The line "target system" stays blank on purpose.
Write the export question, only if you were a customer. Who administered it. Whether a file exists. Where applicant data is allowed to sit. If you were not a customer, write that, and skip the rest.
Write the prohibition. No custom object, no contact load, no file of resumes on accounts, no announcement that staff should log into Salesforce to continue hiring. Each of those is a way of migrating. All of them are out of scope.
There is no price on this page. There was no purchase price to report as yours, and there is no implementation fee this guide will guess. A quote for a Moonhub migration is a quote you can decline without a counter-offer.
Where the other pages fit
The implementation page says there is nothing to implement: Moonhub was not acquired, and there is nothing to migrate. Go there when a statement of work still lists deliverables. The deliverables should come off.
What happened, including the correction, is on what happened to Moonhub. Stay there when someone is still arguing with the headline. Leave it when they accept the correction and need the migration refused in writing.
The integration page is the diagram you do not draw: integrating Moonhub with Salesforce. Read it when a slide has an arrow from a hiring tool into the CRM. Remove the arrow. There is no product at the start of it for this story, and no hiring product at the end.
| Question | Where it belongs |
|---|---|
| Should we migrate? | This page. No. Do not migrate Moonhub onto Salesforce. |
| What is it now? | Not an acquisition. A company the report said was shutting down. |
| Versus native? | CRM objects are not a hiring product. No comparison, and no winner. |
| Alternatives? | Close the ticket, keep an export if you have one, or pause the build. |
Put the headline in the bin and keep the correction in the pack. A project that survives this page has some other justification, written in your own words, for a system you chose. That project must not be called a Moonhub migration. The name is a distraction from a deal that did not occur. Use the name only to explain why the ticket was opened, and why it is now closed.
