Partner and D2C platform migration
Led the frontend product work and helped shape backend migration waves for a Drupal-to-Adobe modernization spanning partner journeys, APIs, insurance rules, validation, and operational readiness.
- My role
- Frontend product ownership, migration requirements, platform boundaries, gap analysis, and selected backend workstreams
- Timeframe
- Phased, multi-wave modernization program
- Evidence boundary
- The migration direction, requirements, and phased product work were delivered; the broader platform migration remains a multi-wave program. This case does not claim that all 14 sites have completed migration.
The migration challenge
The program covered 14 partner white-label sites plus one direct-to-consumer site moving from Drupal/Acquia toward Adobe. The goal was not to copy pages. It was to modernize the experience while preserving regulated insurance behavior, partner differences, system ownership, and operational continuity.
Portfolio scope
The white-label portfolio supported distinct brands, products, entry points, routing rules, and customer contexts across organizations including Marriott, Club Wyndham, WorldMark, Air New Zealand, Costco, and specialist travel partners. The D2C site covered a broader customer lifecycle: product discovery, enrollment, payment, policy service, documents, claims handoffs, customer content, and post-purchase support.
Representative public experiences:
- Costco Travel — partner white-label experience.
- Marriott Owner Advantage — partner white-label experience.
- Club Wyndham — partner white-label experience.
- Air New Zealand — partner white-label experience.
- Travelex direct to consumer — the public D2C experience.
These are selected public examples, not the complete portfolio or evidence that I personally designed every site.
Product approach
- Sequence the change. Move customer journeys and content first, then migrate backend capabilities in controlled waves.
- Design for reuse. Define shared white-label patterns for routing, configuration, validation, branding, and approved partner variation.
- Treat D2C as a lifecycle. Account for enrollment, authenticated policy service, documents, claims handoffs, content, and support—not only purchase.
- Protect system boundaries. Keep authoritative insurance decisions in the appropriate backend services while the frontend owns presentation, accessibility, and journey behavior.
Phased migration ownership
- Frontend migration — primary ownership. As the first phase, I led product discovery, journey definition, requirements, acceptance criteria, stakeholder alignment, UAT planning, and launch readiness. The work rebuilt customer journeys in Adobe while reconnecting them to the services that remained authoritative.
- Backend migration — supporting role, in progress. As the second phase, I support the comparison between current capabilities and the target platform, identify gaps, and translate selected gaps into implementation-ready requirements. One representative workstream assessed a multi-date-range capability, documented what the target system did not yet support, and defined the product behavior needed for implementation.
This public case intentionally omits proprietary business rules, system mappings, architecture, implementation details, and internal delivery artifacts.
Outcome and boundary
The work established a reusable product and requirements model across 14 white-label sites plus one D2C site. Frontend migration came first; backend migration is progressing through controlled gap analysis and implementation waves. This case does not claim every site is complete or that I personally implemented the backend architecture.