Design a phased migration plan for Wallet without hurting users at global scale

Problem Statement Description

Product context: Uber is a mobility and delivery platform; its products include rides, Uber Eats, grocery and retail delivery, freight, driver and courier tools, and marketplace pricing.

Uber is planning a global migration of its Wallet experience and underlying wallet infrastructure for restaurant partners. This Wallet may support balances, payouts, refunds, adjustments, promotional credits, fees, taxes, and transaction history used by restaurants to reconcile their Uber Eats business. The migration must happen across many countries, currencies, payment methods, regulatory environments, and operational support models.

Your task is to design an execution plan for migrating restaurants from the current Wallet system to the new one without disrupting trust, payouts, reconciliation, or restaurant operations. Assume the migration affects both user-facing experiences and backend financial workflows, and that failures could create financial inaccuracies, delayed payouts, support spikes, or marketplace dissatisfaction.

This is not asking for a new Wallet product design. Focus on how you would plan, sequence, launch, monitor, and de-risk the migration at global scale while coordinating product, engineering, data, finance, legal, compliance, local operations, support, and communications teams.

The experience should consider:

- Migration scope: which restaurant segments, markets, wallet features, transaction types, and historical data are included or excluded.

- Phasing and sequencing: how to prioritize pilots, countries, cohorts, currencies, and restaurant types before broader rollout.

- Owners and dependencies: product, engineering, finance operations, compliance, support, local market teams, and external payment partners.

- Go/no-go criteria: payout accuracy, balance reconciliation, latency, support volume, restaurant complaint rates, and operational readiness.

- Rollback and contingency planning: how to handle incorrect balances, failed payouts, data mismatches, or regional payment partner issues.

- Communication plan: what restaurants, internal teams, and support agents need to know before, during, and after migration.

- Launch monitoring: dashboards, alerts, audit checks, cohort comparisons, incident response, and escalation paths.

- Global risks: regulatory constraints, currency handling, tax reporting, marketplace trust, local banking rails, and differences across mature and emerging markets.

The goal is to demonstrate how you would lead a high-risk, cross-functional migration where reliability, financial correctness, and partner trust matter as much as speed. Your answer should show clear operating discipline, thoughtful sequencing, measurable launch gates, and practical safeguards for protecting restaurants and Uber’s marketplace operations.