**TL;DR:** There is no auto-upgrade from regional to global. Export from the regional database and import into a new global one, then cut over. Create the global database with the right primary region (where your writes happen) and the read regions you need. Verify: key counts, spot-checked values, TTLs.

## The fix

1. Create the global database with the right primary region (where your writes happen) and the read regions you need.

2. Export from the regional database. RDB export or key-by-key DUMP/RESTORE both work; pick by data size.

3. Import into the global database.

4. Verify: key counts, spot-checked values, TTLs.

5. Cut over writes first, then reads. Keep the regional database around until the global one has served clean traffic for a full TTL cycle.

6. Reads get faster worldwide; writes now travel to the primary region, so measure write latency from your app region.

7. Reads become eventually consistent across regions. If any flow assumed read-your-writes, add the primary-region read or client-side hold for just-written values.

8. Billing changes: replicated writes count as commands, and fixed plans add per-read-region charges.

## When to use this

- This covers exactly what the title says: Regional to global Upstash upgrade.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.

## When not to use this

- You are doing a different workflow with Regional; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.

## Compatibility

- Not pinned to a specific version; follows current Regional behavior.