How to transfer a site between Pantheon workspaces
Prepare your Next.js site for transfer between Pantheon workspaces by linking the VCS connection.
This documentation describes support for Next.js that is under active development and is available only to customers who have been individually approved as part of our Private Beta program.
To request an invite, submit this form.
If you are migrating an existing Next.js site from our Front-End Sites offering please see our guide on migrating from Front-End Sites.
This guide walks through transferring a Next.js site from one Pantheon workspace to another. When a site is transferred, the VCS connection (GitHub App installation) must also be linked to the destination workspace.
The actual site transfer between workspaces must be performed by Pantheon support. This guide covers the prerequisites you must complete before requesting the transfer.
Requirements
- Administrative access to both the source and destination Pantheon workspaces
- Terminus with the Terminus Repository Plugin
Step 1: Link the VCS connection to the destination workspace
Before requesting a site transfer, you must link the GitHub App installation to the destination workspace. Run:
Replace:
<destination-workspace>with the name, label, or ID of the destination Pantheon workspace<github-org>with the GitHub organization name where the app is installed<source-workspace>with the name, label, or ID of the source Pantheon workspace that has the existing VCS connection
If you omit --vcs-org or --source-org, the command prompts you to select from available options interactively.
You can verify existing connections by running:
Step 2: Request the site transfer
Once you have linked the VCS connection to the destination workspace, contact Pantheon support to request the site transfer. Provide the following information:
- The site name or ID
- The source workspace name or ID
- The destination workspace name or ID
Step 3: Verify
After Pantheon support completes the transfer, confirm:
- The site appears in the destination workspace.
- Push a small change to the repository and verify it triggers a build on the site.
GitHub User accounts
When the GitHub App is installed on a personal GitHub account (rather than a GitHub organization), the installation is only accessible to the user who created it. This means the user who originally installed the GitHub App must be the one to run the vcs:connection:link command.
If that user is unavailable, contact Pantheon support for assistance.