Skip to main content

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.

⏰ Estimated time: 10 minutes Use this guide when you already have code, a project from another tool, or a ZIP archive and want to continue building it in Replit. Importing is the first step. The real goal is to get the project running, understand what setup it needs, publish it, and verify that the public version works.

​
What you’ll achieve

By the end of this guide, you will have:
  • An existing project imported into Replit.
  • Agent’s summary of the framework, dependencies, commands, and missing setup.
  • A working Preview.
  • Any required Secrets or environment variables added in the right place.
  • A published URL that you have tested like a first-time visitor.

​
What you’ll learn

You will learn how to:
  • Ask Agent to inspect an imported project before changing behavior.
  • Identify run commands, build commands, dependencies, ports, and Secrets.
  • Fix setup issues in the smallest possible order.
  • Test the app in Preview before publishing.
  • Verify the published app after deployment.

​
Who this is for

Use this guide if you are importing:
  • A GitHub repository.
  • A Figma, Bolt, Lovable, Base44, Vercel, or ZIP project.
  • Code someone else started.
  • An older project you want to continue with Agent.
For source-specific import steps, see Import from GitHub or the Import overview.

​
Import the project

Open replit.com/import, choose the source, and follow the import flow. After the project opens in Replit, resist the urge to ask for new features immediately. First, ask Agent to inspect what you imported. Imported projects often need setup because local values, private credentials, and deployment settings do not always transfer from the original environment.

​
Get Preview working

Preview should work before you publish. If the app does not start, ask Agent to fix setup issues in order instead of rewriting the app. Check:
  • Dependencies install successfully.
  • The run command starts the app.
  • The app listens on the expected port.
  • Preview opens without a blank page or error screen.
  • The main app flow works.
If Agent suggests changing behavior before the app runs, ask it to pause and focus only on setup.

​
Add missing Secrets and settings

Secret values do not import from GitHub or most external sources. Add API keys, tokens, database URLs, and provider credentials through Secrets, not in code. Ask Agent to identify missing values without inventing them. If the app has a custom run or build command, check the relevant app setup docs for Workflows and Configuration.

​
Test before publishing

Open Preview and test the imported app like a first-time visitor. Check:
  • The homepage loads.
  • The main navigation works.
  • Forms, buttons, login, checkout, uploads, or API calls work if the app uses them.
  • Refreshing the page does not break the app.
  • Restarting the app still works.
  • Logs do not show hidden errors.
If something fails, describe the symptom to Agent.

​
Publish and verify

Publish only after Preview works. Add production Secrets and environment variables in the Publishing pane if the app needs them. Values used in Preview may not automatically exist for the published app. After publishing:
  • Open the public URL in a new tab.
  • Run the same main flow you tested in Preview.
  • Check production-only features like login callbacks, API calls, payment redirects, and database access.
  • Confirm the app still works on mobile if visitors will use phones.
If publishing fails, use Troubleshoot publishing.

​
You’re done when

  • The project imports successfully.
  • Agent has identified the framework, commands, ports, dependencies, and required Secrets.
  • Preview starts and the main flow works.
  • Required Secrets are stored outside code.
  • The app publishes successfully.
  • The public URL works when tested from a fresh tab.

​
Improve it next

Add a database

Save imported app data persistently.

Add login

Protect private pages or user-specific data.

Add integrations

Reconnect APIs, CRMs, email, analytics, or external services.

Add a custom domain

Give the published app a branded URL.

​
Need further help?

  • Import succeeds but the app will not run: check dependencies, run commands, ports, and missing environment variables.
  • Preview works but publishing fails: check production Secrets, database access, host binding, and port configuration.
  • Uploaded files disappear after publishing: use a database or storage service for persistent data.
  • Agent wants to rewrite the app: ask it to focus on setup first and preserve existing behavior.