Migration guide
Move an existing Next.js app
Move the source, configuration, and domain in separate steps. Keep the existing host live until the new project works on its project URL.
Keep the current app live
Do not move DNS first. Leave the current host serving the public domain while you create and test the new project.
List the environment variables, external services, Scheduled tasks, and domain records that the current app uses before you start.
Connect the same production source
- 1Create an App Hosting project.
- 2Choose the GitHub repository that contains the app.
- 3Choose the branch that currently serves production.
- 4Add the production environment variables that the app needs.
Test the new deployment before the domain move
- 1Deploy the production branch.
- 2Open the Host Little project URL.
- 3Test the customer paths that depend on sign-in, forms, payments, APIs, or background work.
- 4Review build and runtime logs if a path does not work.
Move the domain after the checks pass
Add the domain in the project, then use the DNS records shown in the portal. Wait for managed HTTPS to become available.
Confirm that the public domain serves the new app. Only then turn off the old deployment.
Plan around current boundaries
Each project can have one persistent development environment with one selected branch and a stable URL. Pull requests do not create separate apps automatically.
App Hosting does not include backups, snapshots, or self-service exact-commit restore. Keep the source repository and the recovery processes for your external services available.