# Move in.Keep everything.

> Bring a website you made with ChatGPT or Claude, or an existing repository from GitHub or your computer — publish it and keep changing it by talking.

Bring an existing website or repository to Firelent. Your code, your stack and your structure stay as they are — from now on, you change them by talking.

What’s supported

[Made it with ChatGPT or Claude? Here’s how to publish it](https://firelent.com/guides/publish-your-ai-built-site)

you/storefront

branch: main

index.html

about.html

css/styles.css

js/menu.js

img/storefront.jpg

node_modules/skipped

.env

index.html

about.html

css/styles.css

js/menu.js

img/storefront.jpg

.env

Never imported

Storefront

Firelent project

index.html

about.html

css/styles.css

js/menu.js

img/storefront.jpg

Static siteEdit by chatReady to publish

node_modules/ · build output · skipped

No surprises

## Know what works before anything moves.

Firelent looks at your project first — framework, size, images — and tells you plainly what you’ll be able to do with it. Nothing is created until you confirm.

Before you import

you/storefront

Vite · React

142

files

4.1 MB

of code

38

images

Change it by chat — Firelent follows your project's conventions

Deploy — To your own Vercel account

Live preview in Firelent — Not yet for projects that need a build

Skipped: node_modules/ · dist/ · .env · .env.local

What’s supported

## Your stack, honestly.

| Project                                                 | Change by chat | Live preview | Publish                       |
| ------------------------------------------------------- | -------------- | ------------ | ----------------------------- |
| Static HTML, CSS & JSHand-written sites, exported sites |                |              | On Firelent, with your domain |
| Vite & ReactSingle-page apps                            |                | Not yet      | To your Vercel                |
| Create React AppOlder React projects                    |                | Not yet      | To your Vercel                |
| Next.jsStatic or client-rendered                        |                | Not yet      | To your Vercel                |
| Next.js with server renderingNeeds a running server     |                | Not yet      | Not yet                       |

After you move in

## Your codebase, with a colleague who never sleeps.

Change it by talking

Ask for a new section, a fix or a redesign. Edits follow the conventions already in your code — and never add dependencies behind your back.

Reads what it needs

Firelent searches your project and opens only the files that matter, so even large codebases stay fast and focused.

Every change saved

Each edit is a version. Go back to any earlier one whenever you like.

Your code, in view

Browse and search every file, download what you need, and point the chat at a specific file.

You’re here

Migrate — keep your code

For sites and apps you’ve built or paid for, and want to keep developing as they are.

[Or start fresh](https://firelent.com/rework)

[Rework — keep your content](https://firelent.com/rework)

[Paste the link to your live site and get a brand-new one, built from your texts, photos and details.](https://firelent.com/rework)

FAQ

## Frequently asked questions

What people ask before they move a project to Firelent.

### Where can I import from?

From a GitHub repository — you pick the repository and the branch — or by uploading a folder from your computer. ZIP files aren’t supported yet.

### Does importing change my original repository?

No. Firelent copies your files into a new project. Your original repository and branch stay exactly as they are.

### What about my secrets?

`.env` files are never imported — they’re skipped before anything is stored. Dependencies and build output (`node_modules`, `dist` and similar) are skipped too.

### How big can my project be?

Up to 3,000 files and 25 MB of code. Images and fonts come along separately — up to 10 MB each and 200 MB per project.

### Which frameworks work?

Static sites, Vite, Create React App and Next.js. Firelent detects your setup and shows what will work before anything is imported.

Static sites can be previewed and published on Firelent. Projects that need a build can be changed by chat and deployed to your own Vercel account. Server-rendered Next.js apps can be changed, but not published from Firelent yet.

### Should I migrate or rework?

Migrate if you want to keep your code. Rework if you’d rather start fresh: Firelent reads the content of your live site and builds a new one from it.

### Can I keep my domain?

Yes. Published static sites run on your own domain with SSL. Projects deployed to Vercel keep whatever domain you use there.

## Ready to move in?

Connect GitHub or pick a folder. You’ll see what works before anything is imported.

---

Source: https://firelent.com/migrate
More pages: https://firelent.com/llms.txt
