Migrate a project from another platform

Start in Projects, then Migrate a project. Opening the wizard alone does not create a project; creation starts when you submit the source.

Prepare the source

1. 1

   Choose the source

   Choose the original platform or the general source option. Follow the wizard’s code-export instructions.

2. 2

   Enter a link or upload a ZIP

   Use a public HTTPS repository URL from GitHub, GitLab, or Bitbucket, or a project ZIP. Check the upload limit shown for your plan. Private or unsupported links require a suitable export method such as ZIP.

3. 3

   Start migration and wait

   Click Start migration. Keep the page open during upload and processing; large projects can take minutes. Correct a rejected link or archive, or use Retry for the current adaptation step.

Enter required secrets

1. 1

   Review detected names

   After adaptation, the wizard lists names the project may need. Enter only values it actually uses from your service accounts. Raw credential files may be excluded from code import.

2. 2

   Import in the dedicated field

   Paste values into the Secrets step in the shown format, then click Import secrets. Wait for saving to succeed. Use Skip if none are needed. Do not paste values into chat.

Copy database data when needed

1. 1

   Review database status

   Automatic copying currently supports PostgreSQL. If another type is detected, the project needs conversion and a supported database; importing code does not prove data readiness.

2. 2

   Provide a reachable source

   In the old-database URL field, enter a URL reachable by the platform server or use a saved source if offered. A database address on your local device is not enough, and SQL dump uploads are unsupported.

3. 3

   Copy or explicitly skip

   Click the save-and-migrate action and wait for the step to finish. Copying reads the source without changing its data. You can Continue without copying data now when offered; that does not copy the old data.

4. 4

   Address errors before using the data

   If it fails, check the URL and reachability and retry the step. If you skipped copying, prepare the new database and return before using it; it must be empty to copy old data. The temporary source URL is removed when migration or skipping completes.

Review the result and conversion

1. 1

   Wait for project context

   Project memory is built after the earlier steps. If it fails, code and progress are kept; retry that step rather than uploading again from scratch.

2. 2

   Read the final state

   If migration completes, open the project and review notes about an unready database or uncopied data. Test the preview and features yourself.

3. 3

   Convert when required

   Preview and deployment support Next.js and React with Vite without a separate backend. If conversion is required, use Convert it for me now when available, or open the project and request it. Follow Codey’s task and migration report; this work can use credits.