Import a Git repository

Importing through the dashboard connects the project to a supported Git provider and creates an initial deployment from the selected repository.

Choose the personal account or team that should own the project, then verify the framework preset, root directory, install command, build command, and output behavior. Automatic detection is useful evidence, not a reason to skip review. In a monorepo, the root directory determines which package Vercel builds.

Ownership affects billing, domains, secrets, tokens, and who can recover the project. Select the durable team scope rather than whichever account happens to be logged in. Confirm the production branch and Git permissions before enabling automatic deployments.

Write down the detected settings before the first build. If the import fails, compare the repository root, install output, runtime version, and required build-time variables with the local clean-clone result. Changing several dashboard fields at once destroys that evidence; change one assumption and redeploy.

Import Field Notes, pause before deploying, and compare every detected setting with package.json and the repository layout.