# Migrate from Upstash to Layerbase

> Move an Upstash Redis database to managed Redis or Valkey in minutes. Every key, type, and TTL preserved. Read-once, source never modified.

Canonical: https://layerbase.com/migrate/upstash
Generated from Layerbase source: 2026-11-17

Move your Upstash Redis to managed Redis or Valkey on Layerbase in one guided pass. Paste your management API key, pick a database, and we copy every key, type, and TTL. Read-once, your Upstash database is never modified.

## Key facts

| Fact | Value |
| --- | --- |
| Source platform | Upstash |
| Layerbase target engines | Redis, Valkey |
| How you connect | Connect your account with an API key |
| Source modified | No: read-once copy, credentials never stored |
| Message queues | Pick Valkey as the target: the Layerbase queue product (https://layerbase.com/addon/vqueue) runs on Valkey. Plain key-value data works on either target. |

## Why switch from Upstash

### Every key, type, and TTL comes across

The migration walks your database with a non-blocking scan and recreates every key with its type and remaining TTL. Strings, hashes, lists, sets, sorted sets: all preserved.

### Flat pricing, no per-command billing

A Layerbase Redis costs the same at 10 commands a day or 10 million. Free tier to start, then $5/mo Solo or $15/mo Pro. No request counters in your capacity planning.

### Redis or Valkey, your choice

Land on Redis, or on Valkey, the Linux Foundation fork that is wire-compatible with it. Same clients, same commands, one dropdown at import time.

### Queues have a home too

If you use a message queue on your Redis data, target Valkey: the Layerbase queue product runs on Valkey, so your queue workload and its data live together.

## How the migration works

1. **Create a free account or sign in.** Sign in with Google or GitHub. No credit card is needed to start, and the migration wizard opens with this platform already selected.
2. **Connect your account.** Paste your Upstash account email and a management API key (Upstash console, then Account, then Management API). We list your databases so you can pick one, then copy every key, type, and TTL.
3. **Pick what to migrate and name it.** Choose what to bring over, give the new Layerbase database a name, and start the migration. Progress streams live in the dashboard.
4. **We copy it in one pass.** The migration reads from Upstash once and never writes to it. Credentials are used for the copy and never stored. When it finishes, you land in your new database with a live TLS connection string.

## Common Upstash migration questions

### Will my Upstash database be modified?

No. The migration reads your database once with a non-blocking scan and disconnects. Nothing is written to it and it keeps serving traffic throughout.

### What credentials do I need?

Your Upstash account email and a management API key (Upstash console, then Account, then Management API). We use them once to list your databases so you can pick one, and they are never stored.

### Are TTLs preserved?

Yes. Every key is recreated with its type and its remaining TTL, so expiring keys keep expiring on schedule after the move.

### What about my queue data?

Pick Valkey as the target during the import. The Layerbase queue product runs on Valkey (wire-compatible with Redis), so queue workloads carry over cleanly while plain key-value data works on either target.

## Links

- [Migrate from Upstash](https://layerbase.com/migrate/upstash)
- [Redis on Layerbase](https://layerbase.com/db/redis) (markdown: https://layerbase.com/db/redis.md)
- [Valkey on Layerbase](https://layerbase.com/db/valkey) (markdown: https://layerbase.com/db/valkey.md)
- [Cloud migration guide](https://layerbase.com/docs/cloud/migrate)
- [Pricing](https://layerbase.com/pricing) (markdown: https://layerbase.com/pricing.md)
