← Back to work

Cross-Company Promotions Platform Migration

Program lead — migration strategy & growth-platform delivery owner

7 teams · 8 promo types · 3 quarters

The problem

The growth platform had to migrate onto the group's central promotions backend — the one other brands already ran on — without disrupting live deals. It looked like a data migration and was not one: the central platform did not yet support some of the promotion types being migrated or the EU price-transparency rules the markets require, so those capabilities had to be added there first, and every consumer surface (catalog, storewall, store view, pricing, checkout) was affected — spanning roughly seven teams across two companies.

What I did

I owned the program end to end and led a four-engineer team that migrated the promotion data and adapted the BFF services to consume the new backend. I turned an ambiguous "migrate everything" mandate into a phased, vertical-by-vertical plan — nothing moved big-bang, each capability migrated behind a fully working system and rolled out market by market. In parallel I drove the central-platform team to add the capabilities the migration needed — including EU Omnibus price-transparency compliance, the regulatory blocker gating every European market — as additive features that did not disturb the brands already live on it. I ran a weekly lead sync across all seven teams, aligned PMs and EMs on both sides, and traveled on-site to unblock the hardest cross-company dependencies. We migrated eight promotion types across grocery and food and rolled out across every market with zero disruption to live promotions — surfacing and re-baselining each dependency delay transparently along the way.

Stack

Cross-org programPhased migrationBFFEU OmnibusStakeholder alignment