AI builder code export: what you actually take with you

Three meanings of “export”

Source export gives you editable project files, usually through a repository or download. Content export moves records such as text, images or CMS entries. A full migration gets the whole project working on another host, including data, services and configuration.

These are separate capabilities. A CSV of articles is useful, but it is not a functioning website. A repository is useful, but it is not necessarily a working backend.

Read our builder profiles for scoped, source-backed portability notes. The code-portability shortlist groups the relevant options.

Make an exit inventory

For the project you actually want to build, write down the following:

Source: application files, dependency versions and build instructions.
Data: database tables, CMS records, user accounts and any export restrictions.
Files: images, attachments and their storage locations.
Configuration: environment variable names, routing rules, domains and redirects.
Services: email, payments, authentication, scheduled jobs and external APIs.
Permissions: who owns each account and who can approve an export.

Keep secrets out of the inventory document. Record where authorized maintainers retrieve them securely instead.

The inventory is especially useful for agency work. A client should know which accounts and assets belong to them before the handoff, rather than discovering that all production services depend on a contractor’s personal account.

Test a clean rebuild

If source access matters, ask for a small proof before investing in a large project.

Retrieve the project into a fresh directory.
Install dependencies from the lockfile.
Supply a documented development configuration.
Build and run the project outside the original builder.
Exercise its main interaction and failure state.

Record what still points back to the platform. Keep that result distinct from a screenshot of a working preview.

A clean rebuild checks one layer of portability. It does not prove the app is secure, accessible or ready for heavy traffic.

Check the backend separately

Many migrations fail because only the frontend was considered. Make sure the replacement can handle your data model, account system and service calls.

Ask how records can be exported, whether identifiers stay stable, and whether uploaded files keep their URLs. Check how password or authentication-provider migration works rather than assuming user accounts move with database rows.

For an existing website, preserve important URLs and map changed paths to permanent redirects. Search traffic depends on continuity as well as on the new design.

Read limitations precisely

Lovable, Bolt and v0 document source or repository workflows. Their profiles explain the scope. Framer’s native HTML-export page states a limitation; conflicting migration guidance should be clarified before purchase. Wix’s external-hosting documentation describes a platform-dependent site.

Hostinger’s manual-mode documentation describes content export with exclusions. That is a different claim from exporting a complete application. These facts are checked against the linked sources, not against completed migration tests.

Avoid treating an unverified capability as “no.” It may be unknown, restricted to a plan or available in a different product.

Decide whether an exit path is worth the maintenance

Self-hosting adds responsibility. Someone must handle updates, backups, deployments and failures. If you have no plan for that work, a managed platform may be a better fit even when its exit path is limited.

Choose export because it serves a real need: a developer handoff, a client ownership requirement, a particular hosting environment or a long-term migration option.

Questions to ask the vendor

Does export include the backend? Ask which code, data and service configuration are included.

Can the exported project run without your platform? Request build and runtime requirements, plus known service dependencies.

Which plan allows this workflow? Confirm entitlement, billing conditions and any restrictions on existing projects.

Can I keep updating after export? Check whether the workflow is a one-time snapshot or a supported sync.