Keep your app choices open with Lovable's new import

Try a copy before choosing a new home

You can explore another way to build your app while your current version keeps running. Start with a copy of a project you own, then check one complete task before you consider moving real users.

Lovable added project and website imports on October 29. Its October 30 update added memory for preferences and decisions, followed on November 1 by a free downloadable list of the software parts an app uses. Together, these changes offer useful ways to examine an app and keep building with a clearer brief.

These are separate tools, rather than a promise that moving an app is effortless. We have reviewed the published guidance, not tested a migration ourselves.

Read the announcement: Lovable changelog: October 29 imports, October 30 memory and November 1 software inventory download.

A project file is only part of the move

Lovable's project import accepts a ZIP, a file that holds a collection of code files, from Replit, Bolt, Base44, v0, Manus or another tool. It is available on all plans to people allowed to create projects in their workspace. The ZIP can be up to 250 MB.

Lovable uses those files to rebuild the app on its own system. Your database records, user accounts and uploaded documents need separate exports. Passwords and active sign-ins do not transfer. Imported users must verify their email and choose a new password.

Keep passwords and private service keys out of the ZIP and chat. Lovable says it requests needed keys through a separate secret form. Treat the first preview as something to examine: the guidance distinguishes a code move from a complete move that includes the data and services your app needs.

A website import is different. It rebuilds the visible page from an address you provide. It does not automatically bring over the system that manages content, handles forms or signs people in. Use a site you own or have permission to copy.

Check what the free offer covers

The first build of your first eligible import is free. Follow-up messages, including adding your data or answering a question during the work, use normal build credits. Further imports use credits too, and running the imported app has its own usage costs.

The offer is shared between website and project imports, and counts against both your account and workspace. It is used when Lovable creates the project, even if you stop or the import fails. Your workspace still needs credits available to begin.

Keep the decisions easy to review

The new memory feature can carry stated preferences and business facts into later conversations. Project memory is shared with everyone who can edit that project. Personal memory covers how you prefer Lovable to work with you across projects. It is enabled by default on all plans, with settings to change or disable it.

Review those settings after a few conversations. Correct an old price or a decision that no longer applies. Keep confidential information out of messages: Lovable says its filter recognises some kinds of secrets, but can miss other private text. Memory is stored separately from project files, so do not assume a code download includes it.

The November 1 addition lets you download a list of the software parts your app uses while it runs, with known security issues from the latest check. This is called a software bill of materials. Find it in the project's Security view. Downloading it costs no credits. It can help someone reviewing the app, but it is not proof that the whole app is secure and does not include licence information.

Practise with one task you can check

For a learning exercise, choose a practice project with invented records. Write down what a person should be able to do from beginning to end, including what they should never be allowed to see. A working first screen is only the beginning.

1. Save the original project and list any records, files and connected services it needs.
2. Import a copy, then try creating, changing and finding one invented record.
3. Check the same task as another user and confirm private records stay private.
4. Read what Lovable remembers, review the security findings, and compare ongoing costs before deciding where to continue.

Let the outcome guide your choice

Our perspective is that easier imports may give builders more room to compare tools. The useful skill is knowing what must keep working, then checking it carefully. You can practise that without leaving the tool you already use.

If you are building alongside someone or planning training, bring the task, a practice copy and your questions about data, access and running costs. That gives the conversation a practical starting point.