Migrate from Vercel KV to Layerbase
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.
Pick Valkey as the target when you migrate: the Layerbase queue product runs on Valkey, which is wire-compatible with Redis. Plain key-value data works on either target.
Why switch
Why teams leave 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, daily backups, 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 it works
Four steps, one pass
- 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 is Upstash-backed Redis. In your Vercel project: Storage, then your KV store, then .env.local, and copy the KV_URL (a rediss:// string). 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.
Questions
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.
Ready to leave Vercel KV?
Sign in, and the migration wizard opens with Vercel KV already selected. Your source is read once and never modified, so there is nothing to undo if you change your mind.