Migration Guide

Safely migrate your existing projects from a personal GitHub account or another organisation to the corporate pandadoc-studio Enterprise environment while preserving all commit history, branches, and tags.

Preparation

Before touching the terminal, you need a destination for your code:

  1. Go to github.com/pandadoc-studio
  2. Click New repository
  3. Name your project — keep the original name for consistency
Do not initialize the repository with a README, .gitignore, or license. It must be a completely empty "blank slate."

Migration via Terminal

Open your terminal and run the following commands inside your project folder.

Step A — Navigate to your project

cd path/to/your/<project_name>

Step B — Add the new remote

Link your local code to the new home in pandadoc-studio:

git remote add new-origin https://github.com/pandadoc-studio/<project_name>.git

Step C — Push all data

Upload every branch and every tag to the new repository:

# Push all branches
git push new-origin --all

# Push all tags
git push new-origin --tags

Step D — Reset the primary remote

Make origin point to the corporate repo while keeping your old one as a backup:

# Rename your old personal repo to 'old-origin'
git remote rename origin old-origin

# Set the pandadoc-studio repo as the primary 'origin'
git remote rename new-origin origin

Verification

Verify that your local setup is now tracking the correct corporate repository:

git remote -v

You should see origin pointing to the pandadoc-studio URL.

Why Migrate to the Enterprise Org?

  • Centralized Access — much easier to connect your project to Dokploy when it lives in the official organization
  • Security & Compliance — your code is protected under Enterprise security policies and SSO
  • Collaboration — makes it easier for the rest of the team to find and contribute to the project
After migrating, check Settings → Collaborators and teams in the new GitHub repo to ensure your teammates have the correct access. See Permissions & Security for details.