Import lets you bring existing code or designs into Replit Apps and continue building with Agent.Documentation Index
Fetch the complete documentation index at: https://docs.replit.com/llms.txt
Use this file to discover all available pages before exploring further.
Supported sources
| Source | What you provide | Best for |
|---|---|---|
| GitHub | Repository URL or repository picker | Public and private repository imports |
| Bitbucket | Repository URL or repository picker | Bitbucket-hosted repository imports |
| Vercel | GitHub repository behind your Vercel project | Migrating Vercel apps |
| Figma | Frame URL | Turning designs into React apps |
| Bolt | GitHub repository exported from Bolt | Migrating Bolt projects |
| Lovable | GitHub repository exported from Lovable | Migrating Lovable projects |
| Base44 | GitHub repository exported from Base44 | Migrating Base44 projects |
| ZIP | .zip file upload | Importing local project archives |
| Spreadsheet | .xlsx, .csv file, or Google Sheets URL | Building an app from spreadsheet data |
| Previous Agent export | GitHub repository exported from a previous Agent App | Re-importing a previous Agent App |
| Empty | Nothing | Power users who want a blank project without Agent |
Replit validates compatibility before import starts.
Quick imports
Pick a source for step-by-step instructions:- Lovable
- Base44
- Vercel
- Bolt
- GitHub
- ZIP
⏰ Estimated time: four minutesImport a Lovable project into Replit by exporting it to GitHub, then importing that repository.Before you start
- A Lovable project you can export
- A GitHub account connected to Lovable
- A Replit account
- Export your Lovable project to GitHub.
- Open replit.com/import.
- Select Lovable.
- Connect your GitHub account.
- Select the exported Lovable repository.
- Select Import.
What gets imported
Replit imports the following from your project:- Code: Application logic and source files
- Design and styles: UI components and styling rules
- Assets: Images, icons, and static files
- Backend logic: Server-side functionality, if present
- Database schema: Table structure, if present
What is not imported
- Supabase data: Existing database records are not migrated
- Secrets: Environment variables and API keys must be added separately
Configure and run your app
During import, . If your app needs changes, use these Project Editor tools:- Agent: Refine features, debug issues, and make code changes
- Secrets: Add API keys and environment variables
- Workflows: Set the Run command for your app
Continue your journey
Now that you’ve imported your , explore these next steps:- Replit Agent: Get help with feature work, debugging, and refactoring
- Replit Deployments: Publish your app
- Database setup: Configure your database with Agent help
- Collaborate: Build with teammates
Other sources
Bitbucket
- Paste a Bitbucket repository URL, or connect your Bitbucket account to search your repositories.
- Agent support during the import may be limited compared to GitHub-hosted projects.
Spreadsheet
- Upload an Excel (
.xlsx) or CSV file, or paste a public Google Sheets URL. - Agent reads your spreadsheet structure and builds a full-stack app with a database seeded from your data.
- Includes a UI to view, search, and manage your records.
Previous Agent export
- Re-import a previously exported Agent App from a GitHub repository.
- Replit preserves Agent-specific structure (code, database schema, backend functionality).
- Database values and secret values are not imported.
Empty
- Start with a completely empty project — no Agent, no framework selection, and no scaffolding.
- Best for power users who want full control over project setup.
Limitations
- Existing database data is not migrated.
- Some complex or proprietary dependencies may need manual setup.
- Large projects can take longer to process.
Best practices
- Remove sensitive credentials before import.
- Keep your source project structure clean.
- Verify dependencies and run commands after import.
- Test core flows before publishing.
Troubleshooting
If import fails, check these areas first:- Compatibility errors: Verify required project files and supported frameworks.
- Access errors: Confirm repository or source permissions.
- Processing errors: Retry after simplifying project structure or reducing size.