ChatGPT
Claude
Google AI
Copilot
A sales leader wants the calls moved into Salesforce before the quarter ends. The plan says every recording will become notes on opportunities. Nobody has said which opportunity. The same slide has a win rate in the corner, marked expected. The close notice contains neither the notes dump nor the rate. Both are inventions sitting on top of a real date.
This page answers whether you should migrate, what the software is now, how that compares with native Sales Cloud activity, and what the alternatives are. Nothing here is ranked. Nothing here is priced. There is no AppExchange listing and no end date.
Should you migrate
A call recording is not a CRM record. It is a file, or a stream, with speakers, a time, and a grant about who may listen. An opportunity is a named sales record with an owner. Writing text from the first onto the second is a migration only when you have already chosen the opportunity. Do not migrate notes onto an opportunity you have not named.
If the brief says "migrate Momentum" and the opportunity field is blank, the answer is no. You would be filing other people's words against a guess. A guessed opportunity is how a note lands on the wrong deal, gets read by the wrong team, and becomes the story finance uses. You cannot unring that.
A narrower yes is available. After a call, a person who was in the room confirms the opportunity, and a short note they approve is saved on that record. The recording stays where your retention rule says it stays. The note is a decision, not an automatic paste. That is a write-back with a human. It is not a bulk migration of every transcript.
The walkthrough people ask for cannot be a tour of a screen this notice does not describe. It can be a rule. No note is written until the opportunity has a name and an owner. No win rate is copied from a slide. No recording is retained past the period privacy has agreed. If a step skips the name, strike the step.
What Momentum is now
The sentence this page quotes from the close notice is: "Salesforce completed its acquisition of Momentum on March 2, 2026." The date in Australian order is 2 March 2026. Same day. Momentum is conversational insight from video and calls, aimed at Agentforce and Slack.
Aimed at is a direction. It is not a statement that every Sales Cloud org, every Slack workspace, or every Agentforce agent gained a call product on the morning of the close. If you cannot find it in your org, that absence can be consistent with this source. Look at the contract before you brief a rollout.
There is no win rate in the announcement. A before-and-after on your pipeline is a study you have not run. A borrowed percentage is how a programme gets funded on a claim you cannot defend when finance asks for the working. This page will not supply a rate, and it will not bless one you brought with you.
What the software is now stops at insight from calls and video, aimed at those two products. The notice does not describe a Momentum database you load into opportunities. It does not say recordings become activities by default. It does not publish a purchase price, a licence fee, or a shutdown date. Your order form is the commercial record. This page is not.
Name the opportunity first
The failure is a note on the wrong deal. A tool hears a customer name, matches two opportunities, and writes the summary onto both, or onto the one with the nearer close date. The seller who owns the other deal reads a commitment they did not hear. The customer later sees it in a recap someone generated from the record. The recording may have been accurate. The filing was not.
Stop before the write. The person who confirms the opportunity should be someone who can open that record today. A service account that can edit every opportunity is the wrong identity for an automatic note. If you would not let a new starter edit every deal on their first afternoon, do not let a transcript do it.
Consent and retention sit beside the name. Who may listen. How long the recording is kept. Whether a transcript is kept after the note is approved. What happens when the speaker did not agree to a recording. Those rules come from your own policy and your own contracts. They are not in the close notice. A migration that ignores them is not a CRM project. It is a privacy incident with a project code.
Do not let a Slack recap become the record either. Aimed at Slack means a person may see insight in Slack. It does not mean the channel replaces the opportunity. If the note matters, it belongs on the named record, written by someone who will stand behind it. A message in a channel is easy to forward and hard to correct.
Versus native features
Sales Cloud already has an opportunity, an owner, tasks, and a place to write what happened. A seller can log a call. They can attach a file they are allowed to attach. They can @-mention a colleague who already has access to the record. That native activity is slow in a way that is useful: a person chooses the record before the words land.
Momentum, on this record, is insight drawn from video and calls, aimed at Agentforce and Slack. The insight might suggest a next step. The suggestion is not the opportunity. Native activity does not become obsolete because a recording can be summarised. A summary does not become activity until someone names the record and accepts the text.
This page does not rank the seller's own note above the generated summary, or the other way around. Some teams will keep writing by hand because their deals are few and the risk of a wrong filing is high. Some teams will accept a draft summary on a record a human has already opened. Both can be careful. A bulk paste onto unnamed opportunities cannot. The comparison is there to show the gap, not to score the products.
| Job | What this record says about Momentum | What native features already do | What you still write |
|---|---|---|---|
| Record what a seller did | Not a replacement for logging a call | The seller writes on the opportunity they opened | Nothing, until a recording is in scope |
| Turn a call into text on a deal | Insight from calls and video, aimed at Agentforce and Slack | The opportunity must already exist to receive a note | The name of the opportunity, and who approves the text |
| Prove a higher win rate | Not in the close notice | Reports show the pipeline you already have | A study, if you need a rate. Not a footnote |
Leave the rate column empty. A footnote that says expected is not a study. If a partner's walkthrough includes a percentage, take the percentage off before you discuss the opportunity rule.
Alternatives, with no order
The AppExchange search wants a listing and a rank. This page will not invent either. The options are ways to handle calls. They sit side by side. None is first.
Keep native activity. Sellers log the call on the opportunity they already have open. That option fits a team that can spare the minute, and whose risk is a wrong automatic filing. You do not need a new object to store a sentence a person typed.
Approve a short note on a named opportunity, and leave the recording in the store your retention rule already names. That option fits when summaries save time and a human still picks the deal. The human is the control. The product name is not.
Use Slack for a recap that is explicitly not the system of record, in a channel whose members can already open the opportunity. That option fits a huddle. It does not fit a public channel, and it does not replace the note on the record if the note is what legal will rely on.
Do nothing with recordings until you can name the opportunity and the listener. Waiting is a decision. It is the right one when the slide has a win rate and a blank lookup.
A firm that ranks these, or that leads with a rate, is answering a different question from the one you asked. Ask them to name an opportunity from your org and show the approval step. If they cannot, they are not ready to talk about a migration. This page will not order the options for them.
What the walkthrough contains
Write these before anyone moves a transcript.
The opportunity rule. No text is saved until the record is named and the namer can open it. Ambiguous matches stop. They do not pick the nearest close date.
The listener. Who may play the recording, and which identity any automatic step uses. That identity must not be able to edit every opportunity in the org.
The note. Who approves it. How long it may be. Which phrases are banned from being written automatically, including price promises and legal terms a speaker did not confirm.
The retention. How long recordings and transcripts are kept, agreed with the person who owns privacy. A migration that copies everything into Salesforce and deletes the policy has not migrated. It has duplicated a problem.
The refusal. Five cases that must not write a note. No named opportunity. Two matches. A speaker who did not consent. A call about a different customer heard in the background. A request to "update all open deals from this account" from a single recording.
The rate. There is a line on the plan that says no win rate will be claimed from this work. If someone needs a rate later, they design a study. They do not borrow a number.
There is still no price on this page. Scope is the list above. A single number in a proposal, with the opportunity rule still blank, is a number for a different project.
Where the other pages fit
The implementation page is the place for consent, retention, and fields: Momentum, call insight, and what the acquisition does not prove. Go there when the opportunity rule exists and you are writing the fields. Do not go there for a win rate. That page will not invent one.
What happened, the owner, the date, the missing price, and the missing end date are on what happened to Momentum. Stay there when the argument is about the acquisition. Leave it when the argument is about where a note is allowed to land.
The integration page draws the path from a recording to a record: integrating Momentum with Salesforce. Read it when someone asks for a connector. The connector still stops when the opportunity has no name.
| Question | Where it belongs |
|---|---|
| Should we migrate? | This page. Not onto an opportunity you have not named. |
| What is the software now? | Call and video insight, aimed at Agentforce and Slack. |
| Versus native? | Sellers can already log activity on a named opportunity. No winner is declared. |
| Alternatives? | Hand logging, approved notes, a Slack recap, or a wait. No order. |
Pick the claim you can check. The close was 2 March 2026. The work is call and video insight. The note needs an opportunity with a name. The price, the end date, the listing, and the rate were not published. That is the whole story this source will support. Anything fuller belongs in a test you run on your own calls, with your own consent rules, on records you can point at.
