One CRM across a roll-up: who actually does the work
The integration playbook says "standardize the CRM". It rarely says who sits there for six months doing it.
Integrations were the most asked-for skill in the 111 Salesforce admin and developer posts we tracked between 3 May and 5 October 2026, named in 66% of them. CRM administration itself came second at 46%. Companies hiring for this seat are mostly hiring someone to connect systems that don’t talk to each other yet, which is exactly the job that lands on a platform company after every acquisition.
Most roll-up integration plans we’ve seen cover the CRM in one line. Standardize on the platform’s instance, migrate the add-on, done by day 100. The line is fine. The problem is that nobody at the add-on owns a CRM, the platform’s RevOps lead is already full-time on the platform, and the migration becomes a project the VP Sales runs between calls.
What the migration actually involves
A CRM consolidation after an acquisition is four jobs that get called one.
Mapping. The add-on’s deal stages and custom fields have to be translated into the platform’s definitions, and about half of them won’t have an obvious match. Someone decides what “Qualified” meant at the acquired company and whether it survives.
Moving. Contacts, companies, deals and activity history come across with their owners and dates intact, or the sales team at the add-on loses a year of context in a week. This is where the integrations experience in those job posts earns its keep: the native migration tools get you most of the way and the last 20% is Zapier, Make or a script.
Cleaning. Every acquired database carries duplicates, plus dead contacts and fields nobody filled in since 2023. Data cleanup was named in 12% of the Salesforce admin posts we tracked and 17% of RevOps posts, and it’s the part that gets skipped when the migration is a side project.
Re-wiring. Billing, support, marketing automation and reporting tools were all connected to the old instance. They need to be reconnected to the new one, tested and documented, or the first consolidated board report is wrong in a way nobody can trace.
That’s three to six months of full-time work for a mid-sized add-on, longer if the platform has done two acquisitions in a year. Spread across the existing team, it takes twice as long and finishes half as well.
HubSpot or Salesforce, the job is the same
Platforms on HubSpot tend to assume the migration is lighter, and it usually is, but the shape of the work doesn’t change. In the 38 HubSpot admin posts we tracked, workflows came up in 58%, reporting in 55% and integrations in 45%. The HubSpot admin is doing the same mapping and re-wiring, with a friendlier interface.
Where it gets harder is the mixed estate: a Salesforce platform buying HubSpot companies, or the reverse. Then the person in the seat needs to have run both, and that narrows the candidate pool in the US considerably. It’s also the case where a CRM admin is the right seat rather than a RevOps manager.
What the seat costs
A US Salesforce admin or developer had a median base of $112,500 across the 13 posts with a salary that we tracked, which is a small sample, so treat it as directional. Loaded for benefits at the BLS June 2026 split of 68.5% wages to 31.5% benefits, that’s about $164,000 a year, or $13,700 a month. HubSpot admin posts ran lower, at an $83,750 median base across 8 posts, roughly $122,000 loaded.
Most sponsors won’t put a $164,000 person into a $20m add-on to run a six-month migration, which is why the migration becomes nobody’s job. We place a full-time Salesforce or HubSpot admin from $4,000 a month, embedded on the platform’s team, who runs the integration playbook for each acquisition and then stays on to own the consolidated CRM. The same person does the second add-on faster than the first.
When to hire in the US anyway
If the platform is a 200-person sales org on Salesforce with CPQ, a custom data model and an Apex codebase, you want a senior US Salesforce developer who has done exactly that, and the posts we tracked price that at the top of the range for good reason. Likewise if the CRM is wired into a revenue-recognition process that finance signs off on every month.
For a platform under about $100m in revenue, where the CRM is a sales and marketing system rather than a system of record, the admin seat is the same job wherever the person sits. The decision rule: count the acquisitions planned for the next 18 months. If it’s two or more, the CRM admin is a standing seat, not a project, and it should be budgeted like one.