What Was Built
A global healthcare and diagnostics company had acquired multiple businesses and platforms across regions, leaving a fragmented MarTech ecosystem and a Marketing Cloud instance that had been paid for — but never fully implemented — since 2016. This engagement spanned IT operating model design, a full ecosystem audit, executive-level program design, a 14-person contractor team build, and end-to-end Pardot-to-SFMC migration and re-implementation — including the foundational Subscriber Key that had blocked full platform activation for five years.
CX Data & Insights Initiative — IT/Business Operating Model
The client had grown through a series of global acquisitions, leaving a fragmented MarTech landscape: multiple disconnected platforms, separate data clusters per business unit, inconsistent integration standards, and no centralized view of the customer. As Senior Business Relationship Manager embedded in IT, the role was to own the relationship between IT and the marketing business units — translating strategic needs into technical plans and holding both sides accountable.
The CXDI (Customer Experience Data & Insights) Initiative was established as the formal program framework — articulating why centralized CX data was critical to the business, how a connected CX platform ecosystem would be built, and what the operating model between line-of-business teams, IT/data engineering, and reporting/analytics teams would look like. The program also developed best-practice guidelines for onboarding new platforms and datasets — critical as the company continued to acquire new global businesses requiring technology integration.
MarTech Ecosystem Audit & Platform Fragmentation Analysis
The audit surfaced a complex, fragmented stack: Pardot, Salesforce Marketing Cloud (underutilized since 2016), Mailchimp, HubSpot, Social Studio, WeChat, WhatsApp, Line, and various regional platforms inherited through global acquisitions — all with varied integration processes, separate data clusters per business unit, and no unified reporting layer. Critically, the audit uncovered that the original 2016 Marketing Cloud implementation had never been fully completed: the Subscriber Key — Marketing Cloud's unique identifier enabling full CRM integration — had not been established, leaving the platform partially operational for five years.
The problem statement was formalized for leadership: every business unit was operating independently, with custom APIs bridging data to warehouses inconsistently, different insights tools creating reporting silos, and no central customer data environment across the enterprise. This became the anchor for the SFMC consolidation proposal — presenting both the opportunity cost of inaction and a concrete path to unification.
Marketing Cloud Pilot Proposal & IT/Business Leadership Alignment
Rather than immediately committing to a full Pardot-to-Marketing Cloud migration, a structured pilot was proposed: leverage the existing Neo campaign infrastructure to validate Marketing Cloud's end-to-end capabilities — lead nurturing, MQL generation, Salesforce CRM integration, Einstein optimization, A/B testing, and Tableau reporting — while keeping scope lean to minimize resourcing cost and validate assumptions before full commitment.
The pilot proposal was presented to executive stakeholders across Marketing, IT, and business unit leadership, outlining the problem statement, opportunity, executive summary, and specific asks of each leadership group. A separate IT POV was developed documenting the discovery findings, surfacing the 2016 roadblocks, and presenting two concrete decision paths forward — with tradeoffs, dependencies, and recommended next steps for leadership to decide between.
Pardot → SFMC Migration & 14-Person Contractor Team Build
To execute the migration at the required scale and pace, a dedicated team of 14 contractors was hired and managed under A. Bui Consulting — spanning Pardot architects, SFMC developers, Salesforce engineers, Tableau data developers, and data engineers — all embedded specifically for this engagement.
The migration scope was extensive: establishing the Subscriber Key (the foundational CRM integration blocked since 2016); migrating 100+ assets and system automations from Pardot to Marketing Cloud for the Neo and VetLab product campaigns; building new journey architectures in SFMC; enabling Einstein for send-time and subject-line optimization; activating Google Analytics tracking; establishing a new Snowflake data environment for unified data across SFMC, Pardot, CRM, and third-party datasets; creating new Tableau marketing dashboards; and building and delivering a full SFMC digital training program enabling the internal marketing team to operate the platform independently.
SFMC Capabilities Roadmap — Foundational to AI/ML Activation
The roadmap was structured across four stages: Foundational SMC Implementation (Q4 2021) — Subscriber Key, data sanitation, ring-fencing architecture, and Einstein readiness; Early-Stage SMC Adoption (Q1 2022) — pilot buildout, Pardot migration execution, Contact Sync, initial personalization, A/B testing, and Pardot contract renegotiation; Mid-Stage SMC Adoption (Q2 2022) — omnichannel journey orchestration, Contact-Based Marketing, Advertising Studio activation, and behavioral analysis; Late-Stage SMC Adoption (Q3 2022) — fully connected end-to-end AI-enabled campaigns, advanced personalization, Next Best Action decisioning, Datorama activation, and CDP readiness assessment.
Each stage was mapped across planned data outcomes, marketing program priorities, campaign development, platform enhancements, CRM integrations, and analytics buildout. A product-level roadmap for the 4Dx Plus use case was also developed alongside the enterprise roadmap — providing a concrete campaign-level illustration of how each platform stage would translate into real marketing programs.
Subscriber Key Implementation & Data Architecture Design
The Subscriber Key was the single most critical technical dependency blocking full utilization of Marketing Cloud. Without it, SFMC and Salesforce CRM could not share contact identity, campaign activity data could not flow into CRM for sales visibility, lead scoring and MQL workflows could not be activated, and the enterprise CX data vision was effectively on hold. A formal proposal was developed for this workstream — scoped at $69,000–$81,000 over 4–6 weeks — covering platform audit, technical feasibility analysis, ring-fenced implementation design, and execution.
Parallel data architecture work mapped the conceptual data flow across the full environment — including the Data Integration Hub (AWS), Snowflake, SAP, Lavastorm/Alteryx pipeline, Marketing Staging schema, and data engineering views — identifying where data feeds were broken or unscheduled and defining what a centralized customer data fabric would require to support omnichannel marketing at scale. The goal was to move from individual BU-specific pipes and custom APIs to a unified data layer that every marketing platform could consume, reducing the dependency on data engineering for routine campaign segmentation.