# Migrate from Vercel KV to Layerbase

> Move a Vercel KV store to managed Redis or Valkey on Layerbase in minutes. Paste one connection string, every key and TTL preserved, source never modified.

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

Vercel KV is Redis underneath. Paste its connection string and we copy every key, type, and TTL to managed Redis or Valkey on Layerbase in one read-once pass. Your KV store is never modified.

## Key facts

| Fact | Value |
| --- | --- |
| Source platform | Vercel KV |
| Layerbase target engines | Redis, Valkey |
| How you connect | Paste a connection string |
| 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 Vercel KV

### One connection string is all it takes

Vercel KV is Upstash-backed Redis, so its KV_URL is a standard rediss:// string. Paste it, name the new database, and the copy starts. No API keys, no discovery step.

### Every key, type, and TTL preserved

The migration reads your store once with a non-blocking scan and recreates every key with its type and remaining TTL. Your store keeps serving reads and writes while it runs.

### A real Redis you can see

Standard clients, a web console, backups every 12 hours on paid plans, TLS by default, and flat pricing with a free tier. Not a platform add-on: a database with its own dashboard.

### Valkey if you need queues

Land on Redis or on wire-compatible Valkey. The Layerbase queue product runs on Valkey, so queue workloads and their data can 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. **Paste your connection string.** Vercel KV was sunset and existing stores moved to Upstash Redis. In your Vercel project: Storage, then the Redis resource, then open its Upstash dashboard and copy the TLS endpoint: rediss://default:password@your-db.upstash.io:6379. A legacy KV_URL works too, but the REST URL and token will not. We read it once with a non-blocking scan and 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 Vercel KV 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 Vercel KV migration questions

### Where do I find my connection string?

In your Vercel project: Storage, then your KV store, then the .env.local tab. Copy the KV_URL value, which is a rediss:// string, and paste it into the migration.

### Will the copy slow down or block my store?

No. The migration uses a non-blocking scan, so your store keeps serving your app while every key, type, and TTL is copied across.

### Will my Vercel KV store be modified?

No. The migration is read-once: we read the store, copy everything, and disconnect. Nothing is written to it.

### Can my app keep running on Vercel?

Yes. Migrating the data does not touch your deployment. Swap the connection string in your environment variables when you are ready and redeploy.

## Links

- [Migrate from Vercel KV](https://layerbase.com/migrate/vercel-kv)
- [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)
