Work that speaks.

The client

A failure in data integrity is not a technical problem: it is an operational one. That is the reality of working with one of the largest social protection and private health groups in Western Europe, with over 6 billion euros in annual revenue and a national presence throughout France. The organisation managed a high-volume contact database in HubSpot, with automation workflows that depended on data quality and consistency to function correctly. In this context, a data error does not affect a campaign: it affects people.

The challenge

The HubSpot ecosystem had structural problems that prevented the correct functioning of the most critical business acquisition workflows. Two central automation flows, one focused on converting qualified prospects and another on first-visit follow-up, were failing intermittently without the client's team being able to identify the cause.

Added to this were data quality issues at the encoding level: accented characters and special symbols specific to French that the system was not processing correctly, generating corrupted records and segmentation errors. The third front was the integration with the external patient management system, which was not correctly synchronising contact statuses with HubSpot, causing some leads to enter incorrect workflows or none at all.

Three distinct problems, all with a direct impact on new policyholder acquisition.

Our work

Emovere took on the complete diagnosis of the ecosystem and the resolution of all three fronts simultaneously.

Diagnosis and correction of automation workflows. We identified the failure points in both critical flows: misconfigured conditions, logic branches that never executed, and properties that were not updating correctly in certain scenarios. We corrected the logic of each workflow and tested them with real data before reactivating them. The workflows returned to full reliability.

Resolution of encoding issues. We audited the contact database to identify records affected by encoding errors. We implemented a normalisation process that corrected the incorrectly encoded characters and established the necessary rules for new records to enter correctly from the source. Segmentation stopped producing errors from corrupted data.

Correction of the external system integration. We analysed the data flow between the patient management system and HubSpot, identified the fields that were not synchronising correctly, and reconfigured the data mapping to ensure contact statuses were transferred accurately. Leads began entering the correct workflows according to their actual situation.

The result

Before the intervention, the client's team was managing an automation ecosystem with invisible leaks: leads being lost, workflows failing without warning, and data that did not reflect reality. Afterwards, both critical workflows operated without interruption, the database was clean, and the integration with the external system was reliable.

For a corporation of this scale, regaining control over acquisition data has a direct business impact. Every lead that was previously lost to a system failure is now a potential policyholder entering the correct workflow. Emovere did not just resolve the technical problems: it delivered the data infrastructure the marketing team needed to operate with confidence.

The client

For a corporation of this profile, marketing automation infrastructure is not a support tool: it is part of the operational core. A German multinational group specialising in professional information, management software, and fiscal and legal solutions for businesses, with a presence in over 40 countries and tens of thousands of employees worldwide. The organisation serves law firms, consultancies, large corporations, and public administrations with tools that are critical to their daily operations. Its B2B marketing division managed a complex communications ecosystem: segmented campaigns, nurturing workflows, lead capture forms, and conversion-focused landing pages. Stopping that system, even temporarily, was not an option.

The challenge

The organisation had decided to migrate its marketing automation ecosystem from HubSpot to Pardot. The project began with an automatic email migration process that was supposed to simplify the work. In practice, the migrated emails arrived with formatting errors, broken button URLs, and missing text versions required by Pardot. What should have been an advantage became an additional problem to resolve while the rest of the migration continued.

The second front was structural. A change in the values of the central segmentation property revealed a critical Pardot limitation: two field options shared the same internal value, causing one branch of the workflows to never execute. Pardot also does not automatically update new property values in existing workflows and forms, requiring manual review and update of all previously migrated assets that depended on that property.

The third front was one of scale: a single high-traffic landing page concentrated a large number of variants, each dynamically modifying the header content based on campaign parameters. Pardot does not support this type of variation natively, making it impossible to replicate the original solution without custom engineering.

Three simultaneous fronts, all critical, all with active campaigns and live leads. That was the real scenario we faced.

Our work

Emovere took on full technical direction of the migration, from asset planning to resolving problems the destination platform could not handle natively.

Email migration: managing the shift in approach. When the client introduced the automatic process, we redirected the work towards a systematic review of all migrated emails: style verification, correction of button URLs that broke the design, and configuration of the text versions required by Pardot. We also identified and resolved inconsistencies in the footers that affected the correct functioning of communications. The result was a complete set of emails fully operational in the new platform, with no visual or functional errors.

Resolving the logic failure in workflows and forms. We diagnosed the duplicate value conflict in the segmentation property and executed the manual review and update of all affected workflows and forms. A high-volume task requiring precision. An error in any of the updated assets would have broken the segmentation logic of the entire ecosystem. By resolving it, we ensured every contact entered the correct workflow according to their profile.

Custom engineering for landing page variants. We designed and implemented a custom solution that allowed the main landing page to manage all its dynamic content variants internally, replicating in Pardot a functionality that HubSpot handled natively but the destination platform did not offer. No variant was lost in the process.

Code cleanup and style unification. We carried out a systematic cleanup of the HTML code across all landing pages: separation of repeated style rules, removal of residual classes and IDs, and unification of footers to a definitive version. This was not just about order. It was the necessary condition for the next phase of the project: the integration of forms from an external content management system, which depended on clean and predictable code.

The result

What makes a migration of this type difficult is not the volume of assets to transfer. It is having to resolve, simultaneously, the problems generated by the migration process itself, the limitations of the destination platform, and the changes the client introduces while the work is in progress. All of that, without stopping the campaigns.

Emovere delivered a fully operational marketing automation ecosystem in Pardot: corrected emails, landing pages with dynamic content working through custom engineering, correctly configured forms, and segmentation workflows without logic conflicts. The system was left ready to receive the next planned integration, with no pending technical debt.

For a corporation of this scale, that level of operational continuity during a migration is not taken for granted. It is the result of rigorous technical work and the ability to adapt when the scenario changes.

The client

In the high-end property market, the website is not a digital brochure: it is the first and most important point of contact with a demanding buyer making significant investment decisions. A developer with two differentiated brands, each targeting a distinct segment of the luxury residential market, needed its digital presence to match its product. Impeccable design was not enough. The data had to be reliable, up to date, and accessible in real time: price, availability, and the characteristics of each unit.

The challenge

Both brands needed to relaunch their websites with an architecture that eliminated dependence on manual content updates. Every time a unit's status, price, or availability changed, someone had to intervene in the site. That was not sustainable for an active developer with several projects in progress.

The solution was to build the sites on HubSpot CMS using Custom Objects as the inventory database. In practical terms, this means each property unit, with all its attributes, lives in the platform as a structured record, and the website queries and displays it dynamically. This functionality requires an Enterprise HubSpot licence, which added a layer of complexity to the project management.

The challenge was not only technical. It was to build that data architecture while simultaneously developing two websites with the visual finish and user experience expected of the luxury segment. The actual scope of the development significantly exceeded the initial estimate for both projects.

Our work

Emovere took on the data architecture design, full web development, and the integration between the data layer and the front end for both brands.

Design and implementation of the Custom Objects architecture. We defined the data structure to represent the inventory: units, projects, and the attributes of each asset. We mapped the fields needed for the front-end modules to query dynamic information on prices, availability, and characteristics of each unit. When an interruption in the Enterprise licence temporarily blocked access to Custom Objects, we managed the transition with static content to avoid stalling development, and resumed the dynamic architecture as soon as the infrastructure was available. The client lost no project time.

High-finish web development. Both website relaunches delivered a number of modules significantly above the budgeted scope, reflecting the real complexity of the work. The development included advanced front-end visual effects, redesigns of key components (homepage, blog section, menu and contact modals), integration of web-optimised typefaces, and an interactive map module for visualising the location of each project. A night mode was also developed for both brands. Each module was built with the level of detail a luxury product demands.

Training and knowledge transfer. We documented and trained the client's team to update texts, images, and inventory data independently. The Custom Objects architecture implies a different way of managing content compared to a conventional CMS, and the client needed to master it without depending on technical support for routine operations. By the end of the project, the team could maintain and update the inventory on their own.

The result

What changed for the client was not just the design of the site. It was the way they manage their inventory and present their product to the market. Before the project, every catalogue update required technical intervention. Afterwards, the client's team updates prices, availability, and unit characteristics directly in HubSpot, and the site reflects it immediately.

Emovere delivered considerably more than was budgeted on both projects, without cutting corners on quality or finish. At Emovere, when scope grows because the real complexity exceeds the initial estimate, the answer is not to cut back. It is to deliver what the project needs.