MIGRATION KITS · 11 SOURCES IN PROGRESS

Bring your existing app.
Own the production version.

Already on Lovable, Bolt, v0, Bubble, Webflow + Xano, OutSystems, WordPress, or a legacy codebase? Migration Kits import your project, normalize it into the Weezzi application model, and regenerate it as a real production system you fully own — standard Java/Python/JS, free self-host on Docker or Kubernetes.

SOURCE MIGRATION KIT WEEZZI L Lovable REACT + SUPABASE B Bubble NO-CODE W Webflow + XANO O OutSystems LOW-CODE { } Legacy code NODE / PHP / JAVA EXTRACT NORMALIZE REGENERATE WEEZZI App Model Real Code REST + GraphQL Site Editor Self-host YOU OWN IT
Supported sources

If you built it somewhere else,
we'll bring it home.

Three families of source platforms covered. Each Migration Kit reads the source's own export, schema, or codebase — extracts what matters, drops what's vendor-specific, and rebuilds the app inside Weezzi.

AI app builders
L

Lovable

Pulls your React + Supabase project. Schema, auth, RLS rules, components — all become first-class Weezzi entities.

In progress
B

Bolt.new

StackBlitz exports parsed and replayed against Weezzi's app model. Frontend re-rendered, backend regenerated.

In progress
v0

v0 by Vercel

Vercel projects + shadcn components mapped onto Weezzi components, with data layers regenerated.

Planned
FF

FlutterFlow

Pages, collections, Firestore schema, and actions converted into the Weezzi model. Output: web + standard code.

In progress
No-code & low-code
B

Bubble.io

Database, workflows, pages, plugins replicated as Weezzi entities, queries, components, and servlets.

In progress
WP

WordPress (Elementor)

Content, taxonomies, custom post types, Elementor layouts — re-rendered as native Weezzi pages and components.

In progress
OS

OutSystems

Modules, entities, screens, and processes lifted out of the proprietary runtime into owned Java + JavaScript.

In progress
M

Mendix

Domain model, microflows, pages, and integrations regenerated as standard Weezzi elements with real code.

In progress
R

Retool

Internal tools turned into a proper backoffice — RBAC, audit, multi-tenancy, dashboards, all generated.

In progress
SF

Salesforce

Objects, fields, flows, and Lightning pages mapped into the Weezzi app model with full data import.

In progress
Z

Zoho Creator

Forms, reports, workflows, and Deluge logic translated to Weezzi entities, queries, and JavaScript handlers.

In progress
SB

SAP Build / Softr

Apps and tables imported through their export APIs and mapped to Weezzi's component-centric model.

In progress
Webflow stacks & traditional codebases
W+

Webflow + Xano

Webflow pages, CMS collections + Xano backend become a single Weezzi project with real code on both sides.

Planned
{}

Node / Express + Postgres

Existing schema and API conventions reverse-engineered into the Weezzi app model. CRUD regenerated.

Planned
PHP

Laravel / PHP + MySQL

Migrations, models, and routes parsed into the Weezzi model. Pages, forms, lists regenerated as components.

Planned

Something else?

Tell us what you're on. The kit catalog is driven by what users vote up — see the priorities section below.

→ Vote yours
How migration works

Three stages.
Same outcome every time.

A Migration Kit isn't a converter — it's a normalization pipeline. Source-specific knowledge in front; standard Weezzi production system out the back.

Extract STAGE · 01 Normalize STAGE · 02 Regenerate STAGE · 03 SOURCE-SPECIFIC PARSER WEEZZI APPLICATION MODEL
STAGE · 01

Extract

The Migration Kit reads your source through whatever it offers — export file, public API, repo, or DOM scrape. We pull what's actually yours.

  • Database schema, fields, relations
  • Auth users, roles, permissions
  • Pages, components, layouts
  • Workflows, business rules, content
STAGE · 02

Normalize

Source-specific concepts get rewritten into Weezzi's universal application model. This is where vendor-lock-in is broken.

  • Tables & entities · canonical schema
  • Pages · component trees
  • Workflows · servlets & rules
  • RBAC · security profiles
STAGE · 03

Regenerate

Weezzi emits a fresh production system from the normalized model. The output isn't a wrapped copy — it's a new app, generated, owned.

  • Frontend + backend code
  • REST + GraphQL + OpenAPI
  • Site Editor live on day one
  • Docker / K8s deploy bundle
What you get back

Not a wrapper. A new system you own.

After migration, the app you used to rent from a vendor becomes a Weezzi project: standard code, standard runtime, standard deployment. No proprietary lock-in. No black box.

01

The Weezzi application model

Entities, queries, pages, components, workflows, security profiles — your old app, redescribed as first-class Weezzi objects you can edit visually.

02

Standard production code

Java natively, Python via GraalPy, JavaScript via GraalJS. CRUD, REST + GraphQL + OpenAPI auto-generated. No proprietary runtime. Read it, fork it, extend it.

03

The full operating layer

Site Editor, backoffice, dashboards, multi-language fields, A/B testing, scheduled publishing, heatmaps — already wired into the migrated app, ready for marketing on day one.

04

Self-host or stay on Cloud

Docker and Kubernetes bundles. No per-seat pricing. No workload tax. No vendor lock-in. Run it on your infrastructure forever, free.

04 · OPERATING LAYER Site Editor · Backoffice · Dashboards Multi-language · A/B · Heatmaps · Newsletter 03 · PRODUCTION SERVICES Auth · RBAC · Payments · Media · RAG Observability · Queues · Cache · Email/SMS 02 · GENERATED CODE & APIs Java · Python · JavaScript CRUD · REST · GraphQL · OpenAPI 01 · APPLICATION MODEL Entities · Pages · Workflows · RBAC The source of truth — generated from your migration YOU OWN IT
Roadmap · vote

Vote yours.
We build the most-wanted first.

Migration Kits ship in priority order — driven by you, not by us. Pick the platforms you'd migrate from, tell us a little about you, and we'll prioritise accordingly.

Select your platforms 0 selected
Live priority ranking LIVE
— votes total · — voters
Your details

So we can let you know when your kit ships. We won't spam you, and we won't share your details.

Your vote is in.

Thanks — your priorities are recorded and the migration team has your contact. We'll be in touch as soon as your top kit ships.

FAQ

Migration questions,
answered honestly.

Is migration lossless? Will my app behave exactly the same?
No migration tool that promises 100% lossless conversion is being honest. We aim for structural fidelity — your data, your schema, your pages, your roles, your business rules all come across. Visual styling and source-specific behaviors that don't have a clean Weezzi equivalent get reconciled — usually with you in the loop, sometimes by the AI, occasionally requiring a redesign. Self-serve handles clean projects; Accelerator and Portfolio tiers exist precisely because messy projects need a human migration architect.
Can I export my Lovable / Bolt / v0 project to real code via Weezzi?
Yes. The Lovable, Bolt, and v0 Migration Kits don't just import — they regenerate your app inside Weezzi's model and give you the resulting code (Java/Python/JavaScript) under your ownership. You can deploy on Weezzi Cloud or self-host on Docker or Kubernetes for free. There is no proprietary runtime. The output is yours.
How long does a Bubble migration actually take?
Self-serve: hours to a couple of days for small Bubble apps. Accelerator: 4–6 weeks for production-scale Bubble apps with custom workflows, plugins, and integrations. The biggest variable is plugin reliance — Bubble's plugin ecosystem is creative, and some plugins map cleanly while others need to be rebuilt as Weezzi components. We scope this honestly during the Accelerator kickoff.
What about my data? Where does it live during migration?
Source data is read-only during extraction. We never modify your live app. The normalized model and migrated app run in a Weezzi project of your choice — Cloud sandbox, your VPC, or fully on-prem. Production cutover only happens when you say so. Self-host means your data never has to touch Weezzi infrastructure at all if you don't want it to.
What if my source isn't on the supported list yet?
Vote for it above. The Migration Kit roadmap is shaped by real demand. For Portfolio engagements, we routinely build custom kits as part of the project — anything with an export, an API, or a queryable data layer is in scope. Pure no-export black boxes are the only hard "no", and we'll tell you that on the discovery call.
Do I have to migrate everything at once?
No. The most common pattern is a phased migration — start with the part of your app that's hurting most (usually the backoffice, content, or auth/RBAC), prove the new system works, then bring over the rest. For Webflow + Xano stacks, for example, a lot of teams start by migrating just Xano and keeping Webflow as the front-end until they're ready to swap that too.
What about my OutSystems / Mendix license?
Migrating off OutSystems or Mendix is one of the highest-ROI moves Weezzi enables — annual licenses on those platforms typically pay for an Accelerator engagement in the first year alone, and you exit a proprietary runtime entirely. Your apps run on standard JVM after migration. We've structured the Portfolio tier specifically for this kind of move.
Will my dev team still have a job after migration?
Yes — and a much better one. Weezzi generates the boilerplate (CRUD, REST, GraphQL, RBAC, scaffolding) so your developers focus on the differentiating logic. They write Java, Python, or JavaScript on top of generated elements, with full debugger access. Migration usually frees dev time rather than replacing it.
Ready when you are

Talk to the migration team.

Fifteen minutes. We'll look at your source app, tell you honestly which tier fits, and what a migration looks like in practice. No deck, no sales motion — just an architect who's done this before.