Design a phased migration plan for Wallet without hurting users

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 migrating Wallet for restaurant partners in a global delivery marketplace. Restaurant owners, finance admins, and store operators rely on Wallet to see balances, track order earnings, reconcile commissions, manage refunds and adjustments, receive payouts, and understand promotional credits or fees. Any migration that causes incorrect balances, delayed payouts, missing transaction history, or unclear communication can directly affect restaurant cash flow and trust.

You are asked to design a phased execution plan for this migration, not the final product design itself. The plan should account for moving users from an existing Wallet experience or backend system to a new one while keeping day-to-day restaurant operations stable across markets, currencies, payment rails, and support workflows.

Your response should show how you would sequence the rollout, coordinate teams, detect issues early, and protect users if something goes wrong. Assume there are meaningful dependencies across payments, ledger/accounting, restaurant tooling, support, local operations, risk, compliance, data, and communications.

The migration plan should consider:

- Which restaurant cohorts, markets, or Wallet use cases should migrate first versus later

- Key owners, dependencies, and handoffs across product, engineering, payments, finance, support, legal/compliance, and local operations

- Readiness criteria before each phase, including data accuracy, payout reliability, reconciliation, support tooling, and communication preparedness

- Go/no-go metrics and guardrails such as balance mismatches, payout failures, support contacts, refund errors, latency, and restaurant complaints

- How restaurants are notified, educated, and supported during the transition without creating confusion or operational burden

- Rollback, pause, or remediation plans if balances, payouts, transaction history, or reporting are impacted

- Post-launch monitoring, incident response, executive updates, and longer-term prevention mechanisms

The goal is to present a pragmatic migration plan that protects restaurant trust and cash flow while allowing Uber to move to the new Wallet system in controlled phases, with clear accountability, measurable checkpoints, and a strong plan for risk mitigation.