Picture a familiar boardroom scene: Marketing presents their lead generation numbers, impressive graphs, conversion rates, and campaign performance. Then the sales director clears their throat. "Half these leads are garbage," they say. "We're wasting time chasing prospects who aren't even qualified."
The CMO fires back: "Our leads are scoring well in HubSpot. Maybe sales isn't following up fast enough."
Two teams, supposedly working toward the same goal, arguing over data that lives in completely different systems.
This disconnect isn't just annoying. It's expensive.
If you're running SAP's Cloud for Customer, you know about Version 2 by now. SAP rebuilt their platform architecture completely. Where Version 1 used one comprehensive system, V2 breaks everything into smaller, independent services.
Why should you care? Because if you're on V1, you'll need to migrate at some point. And if you're on V2, you're probably discovering that connecting it to other systems requires some new approaches.
Take HubSpot integration. With V1, you had established patterns, existing connectors, plenty of documentation. V2 introduced fresh challenges.
Elixir discovered this when Mondi, a global manufacturing leader, asked to connect their new C4C V2 system to HubSpot. Nobody had done it before. Not properly, anyway.
The Elixir technical team spent weeks digging into V2's architecture. Unlike the old system, where you could grab everything through one big data pipeline, V2 makes you connect to each piece separately. Accounts have their own API. Contacts have theirs. Opportunities get another one.
Sounds simple enough, right? Wrong.
The data structures don't match between systems. Even something basic like addresses gets stored completely differently in V2 compared to V1.
The team had to map out every single field, test every connection, and figure out how to handle errors when data doesn't sync properly. And they had to do it without any existing roadmap because, well, there wasn't one.
Carl Boden, Elixir's integration specialist, put it best: "It's like trying to connect two machines where someone changed all the plugs but didn't update the manual."
Getting accounts and contacts syncing took just seven weeks. In the integration world, that’s fast, especially when starting from scratch. No templates, no existing frameworks, just SAP knowledge and determination.
The breakthrough came when the team realized they needed to approach V2 differently. Instead of replicating V1 patterns, they built around V2's microservices model. Each business object became its own integration pathway.
Working with Mondi as the pioneering client, Elixir quickly synchronized accounts and contacts between the two systems. Data was flowing. The foundation was set for what would come next in Phase Two: leads, opportunities, and line items.
The technical achievement is nice for the engineering team's resumes. But what matters is what happens next.
Marketing teams can finally prove their work drives revenue. When they run a campaign in HubSpot and see those leads close as deals in C4C, the attribution stays intact. No more arguments about lead quality or campaign effectiveness.
Sales gets context they never had before. Instead of cold-calling prospects with just a name and company, they see the complete journey, which content pieces someone downloaded, how many times they visited the pricing page, what specific pain points they mentioned in forms.
Customer experience improves because people stop getting asked for the same information twice. The handoff from marketing to sales works.
Being first to solve the C4C V2–HubSpot puzzle wasn't just about proving capability. Every C4C V1 customer will face this migration at some point. The approach is now proven.
Phase Two is underway: leads, opportunities, and line items. The foundation from Phase One means this next stage builds on tested architecture rather than starting from scratch.
Companies are already asking about timelines. Manufacturing organizations, in particular, have been waiting for a reliable way to connect their C4C V2 systems to HubSpot. Now that the path exists.
You might wonder why SAP didn't build HubSpot integration into V2 from the start. Or why HubSpot hasn't created a native connector.
The answer is timing and the inherent complexity of SAP systems. V2 is still relatively new, and SAP's architecture requires deep expertise to integrate properly. Building connectors for enterprise SAP systems takes time and specialized knowledge, especially when the architecture is fundamentally different from V1.
Elixir had the advantage of deep SAP expertise and a client willing to pioneer this integration. Plus, the team has been navigating complex enterprise integrations long enough to know how to tackle uncharted territory.
If you're using C4C V2 and wondering how to connect it to your marketing systems, the patterns exist now. Elixir has documented everything, built reusable frameworks, and worked through the edge cases.
For companies still on V1 planning their migration, this integration capability changes the equation. You don't have to choose between keeping your marketing operations in HubSpot or moving everything to SAP. You can have both.
The next few months will be interesting. As more companies migrate to V2 and realize they need better marketing integration, demand for this expertise will grow.
Right now, if you need C4C V2 talking to HubSpot, Elixir has built the solution.