1. Executive Summary
In global enterprises, running duplicate Tier 1 Marketing Automation Platforms (MAPs) across different business units creates immense, unnecessary overhead. The insurer’s Hong Kong B2B division was utilizing a local Salesforce Marketing Cloud (SFMC) instance alongside Oracle Eloqua, which served as the global standard across all other regional business units.
To eliminate dual-licensing costs and standardise operations, the insurer initiated a strategic platform consolidation, migration, and decommissioning project to sunset the local SFMC instance and safely migrate all active B2B operations into the global Eloqua environment.
I was engaged on a white-label basis via a premier partner agency to provide the high-level technical architecture, design, and strategic oversight for this complex migration. This was not a simple technical "lift-and-shift"; it required standardising a fragmented data layer, re-engineering key customer journeys, migrating legacy asset templates, and establishing a robust technical governance framework to empower the local marketing operations team.
2. Strategic Challenge & The "Why"
Migrating complex B2B customer journeys between two major enterprise platforms without a rigorous architectural blueprint introduces severe operational, legal, and financial risks. The primary business objectives for this consolidation included:
- ■ Commercial Rationalisation: Sunsetting a secondary Tier 1 platform to eliminate double-licensing overheads and standardise the global martech spend.
- ■ Data Integrity & Customer 360: Consolidating disparate data inputs from corporate website forms, AWS data lakes, and Salesforce CRM to construct a unified customer profile.
- ■ Operational Continuity: Re-creating high-value, active customer journeys without losing engagement or breaching compliance standards during the migration.
- ■ Local Enablement: Upskilling the regional Hong Kong marketing operations team to ensure long-term self-sufficiency and protect database health from day one.
3. A Comprehensive Approach
To ensure the migration delivered an immediate return on investment, I designed and executed the project through my structured, high-touch **Four-Layer Architectural Framework**:
A. Process Layer (Operational Governance)
A technology migration is fundamentally a change management project. To prevent the local team from falling back into legacy manual habits, I conducted structured training workshops to transition the Hong Kong team's mindset from SFMC's list-based model to Eloqua's segment-and-contact-based database architecture. I standardised campaign intake and execution workflows, establishing clear rules on template-creation permissions versus campaign execution.
B. Application Layer (Platform Configuration)
Rather than blindly copying outdated templates, I used the migration as an opportunity to clean and modernise the insurer's technical debt. I sunsetted bloated legacy SFMC HTML code, re-authoring modular, responsive, and brand-compliant email and landing page templates natively within Eloqua. Furthermore, I re-engineered business-critical nurture programs, translating SFMC Journey Builder paths into structured, multi-step Eloqua Program Canvases with built-in exit criteria.
C. Data Layer (The Customer 360 Foundation)
Managing complex customer profiles within B2B insurance requires robust relational data schemas. Guided by rigorous data cleansing protocols, I focused the database standardisation on three distinct sources:
- AWS Data Warehouse: Served as the central repository for the Customer 360 data model, managing complex policy holdings, corporate hierarchies, and customer tiering.
- Salesforce CRM: Acted as the sales system of record, housing lead, contact, and account objects.
- Website Forms: Served as the first-party transactional capture layer for inbound prospect interest.
I mapped these inputs into Eloqua, leveraging Custom Data Objects (CDOs) to house relational policy data without bloating the primary contact table.
D. Integration Layer (Secure Pipelines & Sync)
To secure the data pipeline, I architected an automated synchronisation framework between AWS, Salesforce CRM, and Eloqua to ensure real-time lead updates and prevent sync delays. I implemented precise matching logic using Email Address as the primary key, coupled with Salesforce Contact and Lead IDs to maintain single-record integrity. Strict subscription preference syncs were enforced to ensure that global opt-outs were respected across all systems, maintaining rigorous compliance with regional data privacy laws.
4. Key Project Milestones
Wave 1: Discovery & Audit (Technical Due Diligence)
Audited current-state SFMC journeys; defined the global marketing database data dictionary; aligned AWS and Salesforce schemas with the target Eloqua field dictionary.
Wave 2: Build & Migration (System Configuration)
Constructed native Eloqua integrations; migrated, modernised, and built modular responsive templates; configured Custom Data Objects (CDOs) for handling inbound AWS policy data.
Wave 3: Launch & Handoff (UAT & Local Enablement)
Conducted end-to-end data validation testing; rolled out hands-on Eloqua training for the local Hong Kong marketing operations team; completed a safe system cutover and decommissioned the SFMC instance.
5. Strategic Value Delivered
Direct Cost Savings
Sunsetting the redundant regional platform completely eliminated double-licensing overheads, immediately returning budget to the local B2B business unit.
Technical Debt Eliminated
Streamlining legacy template assets and restructuring data tables removed years of platform bloat, resulting in faster campaign turnaround times and cleaner analytics.
True Customer 360 View
Bridging the gap between the AWS Data Warehouse and Salesforce CRM provided sales and marketing teams with a real-time, consolidated view of corporate account engagement for the first time.
Operational Self-Sufficiency
Structured workshops and blueprints ensured that the insurer's regional marketing operations team was fully enabled to manage, optimise, and scale the new platform without being dependent on external contractors.
Architectural Outcomes
White-Label Delivery
This migration was successfully delivered under a strict white-label partnership model. I acted as the lead architect representing the primary agency partner, interfacing seamlessly with internal corporate enterprise stakeholders.
Explore Partnership Models