We ran Momentum’s RevOps in 2025: a new Salesforce org, a clean HubSpot sync and attribution sales could trust. The work held up so well that when Salesforce acquired Momentum in 2026, Salesforce’s M&A team kept us on to run RevOps through the integration and carry that system into Salesforce.
Momentum, a conversational insights and revenue orchestration platform, brought JayOh in as its RevOps pod in early 2025. We moved Momentum onto a new Salesforce org with a Friday-to-Monday cutover, rebuilt the HubSpot–Salesforce sync (600 duplicates resolved, 2.9K opportunity sync errors cleaned up) and rebuilt attribution and lead scoring. After Salesforce signed a definitive agreement to acquire Momentum in February 2026, Salesforce’s M&A integration team kept JayOh on to run Momentum’s RevOps through the transition: day-to-day CRM management, revenue and finance reporting, and data migration into Salesforce’s systems.
Six workstreams across two phases. The first four made Momentum’s own go-to-market data trustworthy. The last two kept it running, and moving, once Salesforce owned the company.
Audited field usage, then rebuilt record types, custom fields, validation rules, flows, list views, roles and campaigns in a new org. New external ID fields kept every old record traceable to its new ID. Integrations paused for a Friday-to-Monday cutover, with the SDR and sales dashboards rebuilt first.
Backed up every deal, remapped deal fields after ID conflicts and replaced the inclusion list with a full sync rolled out in waves. Going live exposed 2.9K opportunity sync errors from record-type mismatches and 600 duplicates. Both were cleaned up.
Original and enhanced most-recent source fields from HubSpot into Salesforce, self-reported attribution captured from sales conversations, partner referrals tracked with a unique partner ID and pipeline split into marketing-, AE- and referral-sourced opportunities across three dashboards.
UTM parameters kept across pages and captured on multi-step forms, a web pixel audit, company size normalized between HubSpot and Salesforce, and a buyer-fit score on enriched HubSpot data that syncs to Salesforce as both a number and a tier.
When Momentum’s RevOps lead moved on, we took over day-to-day CRM management: keeping leads, pipeline and customer records accurate across both Salesforce orgs so sales never lost visibility. Every recurring process got a written guide and a video walkthrough.
Rebuilt revenue and retention reporting in the formats Salesforce’s finance team needed, with Momentum’s accounts mapped to Salesforce’s. Supported the program moving Momentum’s customer contracts into Salesforce’s systems.
Momentum was growing fast and needed a Salesforce org, a HubSpot sync and attribution data sales and marketing could both trust. A year later, Salesforce agreed to buy the company, and every lead, report and contract had to start flowing into Salesforce’s own systems.
Lead-source data was tagged inconsistently, the HubSpot sync covered only part of the database, and key processes lived in people’s heads. Then the RevOps lead moved on mid-integration. The work needed an owner who already knew the system.
Results as recorded in the engagement’s working sessions and project board. Where a before-and-after number wasn’t captured, the table describes the change.
| Metric | Result | Context |
|---|---|---|
| Salesforce org migration | Friday-to-Monday cutover | Integrations paused for the move; SDR and sales dashboards rebuilt first; old-to-new record IDs cross-referenced |
| Duplicate records | 600 resolved | Found and merged during the HubSpot–Salesforce sync cleanup |
| Opportunity sync errors | 2.9K cleaned up | Record-type mismatches exposed once the full sync went live |
| HubSpot–Salesforce sync | Full, bidirectional | Rolled out in test waves instead of a partial inclusion list |
| Lead source data | Rebuilt | Mis-tagged sources corrected; original, most-recent and self-reported source captured |
| RevOps after the deal | Kept running | CRM management and reporting continued across both orgs until the integration cutover |
| Contract migration | All active, eligible contracts in scope | Legacy contracts included alongside current ones |
Founders, investors and the buyer make deals. What we can speak to is the system Momentum carried into it, and the work of moving that system into Salesforce afterward.
| When | What happened | Why it matters |
|---|---|---|
| Jan 2025 | JayOh starts as Momentum’s RevOps pod | Attribution, Salesforce and HubSpot work on a sprint-based retainer |
| Jun 2025 | Momentum moves to a new Salesforce org | Friday-to-Monday cutover; remaining validation rules and notes migrated right after go-live |
| Jul–Dec 2025 | Sync, attribution and lead scoring rebuilt | A new RevOps lead onboarded onto documented workflows |
| Feb 2026 | Salesforce signs a definitive agreement to acquire Momentum | Salesforce cited bringing outside conversation data into Agentforce 360 and Slackbot |
| Jun–Sept 2026 | JayOh runs Momentum’s RevOps alongside Salesforce’s M&A integration team | RevOps management, finance reporting and contract migration support up to the integration cutover |
| Integration question | What was in place at Momentum |
|---|---|
| Can every account and opportunity be mapped to our IDs? | External ID fields from the org migration, plus documented mapping of Momentum’s accounts to Salesforce’s |
| Which contracts are active, and what type are they? | Active contracts identified and grouped by type for migration |
| Will leads keep flowing during the transition? | Daily CRM management with duplicate checks, so pipeline stayed accurate across both orgs |
| Who knows how the system works? | Written guides and video walkthroughs for every recurring process, run by a pod already inside the org |
Merging systems after a deal? See post-acquisition CRM consolidation.
Deal facts come from Salesforce’s public announcement. JayOh did not advise on the transaction.
Six checks we ran into on this engagement. Answer each one honestly and see where your CRM would slow an integration down.
Scoring: Yes = 2, Partly = 1, No = 0 on each check, out of 12, shown out of 100. Weak is under 50, acceptable is 50 to 79, strong is 80 and up. These bands are JayOh’s rule of thumb, not an industry standard.
Pause integrations, move the data, and bring back the SDR and sales dashboards before anything else. People judge a migration by Monday’s numbers.
A full sync turns on every hidden duplicate and mismatch at the same time. Rolling it out in batches let us fix errors in a few hundred records instead of thousands.
External IDs and documented mappings made every later step faster: the org move, the finance reports and the contract migration into the acquirer.
A new Salesforce org with migrated data, flows and dashboards; a full, bidirectional HubSpot–Salesforce sync with duplicates and sync errors cleaned up; attribution with original, most-recent and self-reported source; and a buyer-fit lead score synced to Salesforce.
We ran Momentum’s RevOps through the transition alongside Salesforce’s M&A integration team: day-to-day CRM management, revenue and retention reporting in Salesforce’s formats, and support for moving contracts into Salesforce’s systems.
Rebuild the metadata in the new org first, add external ID fields so every old record maps to a new one, pause integrations for a short cutover window and bring back the dashboards people use every day first. See Salesforce consulting.
Usually because it ran on a partial list, records were created on both sides, or fields like company size had different values in each system. A full sync rolled out in waves, with matching rules and normalized fields, shows the problems in small batches. See CRM deduplication.
Yes. We map records and IDs between systems, run RevOps while two orgs coexist and support the move into the acquirer’s systems. See post-acquisition CRM consolidation and our post-merger CRM consolidation case study.
No. Momentum, its investors and Salesforce made the deal. JayOh ran the revenue operations Momentum carried into it and supported the operational integration afterward.
See pricing for how our pods work.
We’ll review your IDs, sync, source data and contracts and show you what an integration team will run into in your CRM, before they do.
30 minutes with a GTM systems engineer. You leave with a read on where your system is breaking, whether or not we work together.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
