# Alchemist: Import an App from Base44

Move an app you built in Base44 into a new Chipp project: what to export, what moves over, what changes, and what you still set up by hand.

---

Built an app in Base44 and want it in Chipp? The guided Base44 import takes the export Base44 gives you and starts a new Chipp project from it. Before anything is created, Chipp checks the export. After the import, a migration report shows what moved, what changed, and what still needs you.

## What you upload

Chipp accepts the two things Base44 lets you export:

| What | How to get it in Base44 | Required |
| --- | --- | --- |
| **The code export (.zip)** | Open your app, then **More actions** > **Export project as ZIP** > **Download ZIP**. Base44 needs a Builder plan or higher for this. | Yes |
| **Your table data (.csv)** | In your app's dashboard, open **Data** and export each table as CSV. Name each file after its table, for example `Task.csv`. | No |

If your app syncs with GitHub through Base44's GitHub integration, you can also download the repository as a ZIP from GitHub (**Code** > **Download ZIP**) and upload that. It has the same layout.

Chipp only uses these exports. It never signs in to Base44 for you and never reads anything you did not upload.

## Start the import

1. On the Builder home, under **Start from something you have**, choose **Base44 app**. You can also choose **Import from Base44** in the new project dialog, next to the GitHub import.
2. Choose your ZIP, and add your CSV files if you want your rows too.
3. Click **Check export**. Chipp reads the export and shows you the migration report it will produce. Nothing is created yet.
4. Click **Continue**, name the project, and create it.
5. Chipp copies the export into the project and shows the final report, with a secure link for your secrets.

If the check finds a problem, you see exactly what is wrong (for example, which file is missing or which file is not valid JSON), and no project is created. If the import stops after the project was created, you can retry it or discard the project.

## What moves over

| Part of your app | What happens |
| --- | --- |
| Pages, components and other code | Copied into the project, under `docs/reference/base44/source`. Your AI engineer rebuilds them in your Chipp app. |
| Images, fonts and other assets | Copied with the code. |
| Tables (Base44 entities) | Each table's fields are translated into a Postgres table in `docs/reference/base44/schema.sql`: types, required fields, defaults, and allowed values. |
| Table data (your CSV files) | Checked against the tables and stored privately with the project. They are never put in the code repository. |
| Backend functions | Copied. Each one becomes an API route of your Chipp app during the rebuild. |
| Login settings | Email and password becomes email sign-in, and Google sign-in carries over. Other methods are listed for you to set up. |
| Secrets (environment variables) | Only the names are read. Each one gets a secure credential request, where you enter the value. |
| Domains | Your custom domain, if the export mentions one, is listed so you can connect it on the project's Domains page. |

## Secrets stay secret

Base44 keeps your secrets out of the export, and Chipp keeps it that way:

- Chipp reads the **names** your code uses (for example `STRIPE_SECRET_KEY`), never a value.
- A `.env` file in the export is read for names only and is never copied.
- Any other file that looks like it holds a key or token is not copied. The report names the file and the line, never the value.
- You enter each value in Chipp's secure credential form. It is encrypted and never shown in chat.

## The migration report

The report has three groups:

- **Imported successfully**: copied as it was, such as your code and assets.
- **Transformed**: carried over in a different form, with what changed. For example, a list of allowed values became a database rule.
- **Needs manual action**: something Chipp could not carry over, with the reason. Nothing is dropped silently: anything the import could not handle is listed here.

The same report is saved in your project at `docs/reference/base44/README.md`, so your AI engineer works from it too.

## Known limitations

The import moves what Base44 documents and exports. It does not promise a perfect copy of Base44's internals.

- **Your app is rebuilt, not run as-is.** Base44 apps call Base44's own services (its database, logins and functions) through the Base44 SDK, which does not run outside Base44. Your AI engineer rebuilds those parts in your Chipp app from the imported code.
- **Access rules do not carry over.** Base44 row-level and field-level security rules are listed under "Needs manual action". The rebuild enforces them on the server.
- **People sign in again.** Base44 does not export passwords or app users.
- **Data is loaded after the first build.** Your rows are stored privately at import time and loaded once the build has created the tables.
- **Some sign-in methods need setup.** Microsoft, Facebook, Apple and single sign-on are listed for you to configure.
- **Base44 integrations and connectors.** Built-in AI and file features map to Chipp equivalents. Email, SMS, connectors and Base44 agents are listed for setup.
- **Domains are not in the export.** Connect your custom domain yourself, then update its DNS.
- **Size limits.** The ZIP can be up to 100 MB, each CSV up to 25 MB, and up to 50 CSV files. Leave out `node_modules` and build folders.

## Related

- [Adding environment variables and secrets](/docs/guides/alchemist-environment-variables)
- [Deploys and domains](/docs/guides/alchemist-deploys-and-domains)