Migrating from Bolt

Re-prompting strategies and component reuse when moving from Bolt.new to vly.

Bolt.new and vly serve similar use cases — turning prompts into working apps. The migration is mostly re-prompting.

What ports

• The product spec — your original Bolt prompt is a great starting point in vly.
• Component code — paste any custom React you wrote.
• Integration keys — re-paste into vly’s secret store.

What changes

• Backend: Bolt typically uses simpler local state; vly uses Convex from the start.
• Real-time: vly’s reactive sync changes how you’d structure live features (no polling needed).
• Pricing: vly’s $3/mo tier vs Bolt's$25/mo entry point.

Steps

1. Capture the Bolt prompt and feature list

   Read the existing app. List the features you want to keep.

2. Start a new vly project

   Use Plan mode. Submit the high-level spec; review and refine.

3. Port any custom code

   Drop into Code mode; paste; adjust imports.

4. Re-set up integrations

   Stripe, Resend, etc. — paste keys into vly’s secret store.

5. Cut over the domain

   Update DNS to point at vly.

Tips

vly is opinionated on stack (React + Convex + Tailwind + shadcn). If your Bolt project used different tech, expect some translation.

Related

Quickstart

Five-minute build.

Compare

vly vs Bolt.

Convex overview

The new backend.