Migration Guide

Migrate from Bolt.new to Fabricate

Full-stack apps without the credit anxiety

~20 minutes

Key takeaways
  • One meter instead of two -- Fabricate credits pay for the build, not for the traffic the live app serves
  • Get the backend, database, and auth as source in your own repository instead of a rented Bolt Cloud service
  • Keep the fast generation speed you love, with better full-stack output
  • Export your code anytime -- full ownership guaranteed

Why Switch from Bolt.new?

One Meter, Not Two

Bolt spends tokens while you build and Bolt Cloud usage while the app runs, so a busy app keeps drawing down. Fabricate meters only the AI work that builds the app.

A Backend in Your Repository

Bolt Cloud is a real first-party backend, but it is a service you rent: it bills for what the live app does and does not travel with an export. Fabricate generates a Hono API, a D1 schema and auth as ordinary source you keep.

Better Production Output

Fabricate plans the application before writing code, resulting in better-organized, more maintainable applications.

Verified in a Real Browser

Before an app can be published it is opened in a real browser and the render is checked. An app that crashes, never mounts or renders a blank page is blocked from publishing, rather than going live broken.

Step-by-Step Migration

  1. 1

    Document Your Bolt Projects

    List your existing Bolt projects and what each one does. Note what Bolt Cloud is handling and any external services you have connected.

    • Screenshot your current applications
    • Write down your Bolt Cloud tables, auth setup and server functions
    • Note any custom configurations
  2. 2

    Sign Up for Fabricate

    Create your account at fabricate.build. The free tier needs no card and includes a monthly credit allowance.

    • No credit card needed
    • Upgrade only when you need more capacity -- see fabricate.build/pricing
  3. 3

    Rebuild with Full-Stack Prompts

    For each Bolt project, describe the complete application including backend needs. What Bolt Cloud was hosting for you, Fabricate generates as source.

    • Include database requirements in your prompt
    • Specify authentication needs
    • Mention any payment processing requirements
  4. 4

    Iterate Within One Allowance

    Refine your application with follow-up prompts, drawing on the same monthly credit allowance rather than a second runtime meter.

    • Make as many changes as your credit allowance covers
    • No separate charge for what the deployed app serves
    • Queue multiple prompts during generation
  5. 5

    Deploy and Connect Your Domain

    Deploy to Cloudflare edge with one click. Connect your custom domain if you had one on Bolt.

    • Global edge deployment
    • Custom domain support
    • SSL certificates included

Feature Mapping: Bolt.new vs Fabricate

FeatureBolt.newFabricate
Frontend GenerationFast, good quality UIEqual quality with integrated backend
BackendBolt Cloud server functions (managed)Hono on Cloudflare Workers, in your source
DatabaseBolt Database or your own SupabaseD1 through Drizzle ORM, schema in your repo
AuthenticationBolt Cloud auth (managed)Built-in: bcrypt, signed JWT, revocable D1 sessions
PaymentsManual setupStripe built in
DeploymentBolt hosting or NetlifyCloudflare Workers for Platforms, at the edge
MeteringTokens to build, Bolt Cloud usage at runtimeCredits meter the build only
Error Correction CostConsumes creditsIncluded in plan

Common Pitfalls to Avoid

Expecting to transfer Bolt project files

Fabricate creates optimized new projects. Describe your application fresh -- it's faster than trying to import and fix existing code.

Assuming Bolt Cloud comes across with the code

It does not. Bolt Cloud is a platform service, so a GitHub export gives you the front end and application logic, not the running backend. Include your backend, database, and auth requirements in the Fabricate prompt so they are generated as source.

Comparing credit-by-credit

Fabricate's credit system is different from Bolt's. A single Fabricate credit goes further because the generation pipeline is more efficient.

Frequently Asked Questions

Can I import my Bolt.new project into Fabricate?
No -- Fabricate starts projects rather than joining them, so it cannot be pointed at an existing repository. Rebuild from a description instead. That is less painful than it sounds here, because the half of a Bolt project that matters most, the Bolt Cloud backend, would not have migrated anyway.
Will my apps look the same?
Fabricate produces equally polished UIs. You can reference specific design elements from your Bolt projects in your prompts. The visual output quality is comparable.
How much will I save compared to Bolt?
That depends on your usage, and the honest answer is that the structure differs more than the price. Bolt meters tokens while you build and Bolt Cloud usage while the app runs, so a busy app keeps drawing down. Fabricate meters only the AI work that builds the app. Current Fabricate plans and credit allowances are on the pricing page at fabricate.build/pricing.
Do I lose anything by switching?
Yes, and it is worth naming. Bolt imports from Figma and from GitHub, documents Expo through to app-store publishing, and lets you swap its database for Supabase or its hosting for Netlify. Fabricate does none of those. What you gain is a backend that is source in your own repository rather than a service you rent, and one meter instead of two.

Related guides

Fabricate vs Bolt

Detailed feature comparison.

Read guide

Bolt Alternatives

All Bolt.new alternatives compared.

Read guide

Best AI App Builders 2026

Complete AI builder comparison.

Read guide

Ready to Make the Switch?

Start building with Fabricate today. Free tier available -- no credit card required.

Start Building Free