Can I transfer a project to another account?

No. TeleportHQ doesn't have a way to transfer a project's ownership to another account or to move a project into a different workspace. There are two workarounds. To hand a project over, set it to Can clone, send the link, and the other person clicks Clone to save their own copy in their workspace. To work on it together instead, invite them as a collaborator, while the project and its billing stay with you.

Choose the right option#

• Give them their own copy when the other person should own the site from now on, for example a client who will pay for their own plan. Follow the steps below.
• Invite them as a collaborator when you keep the project and they only need to view or edit it. See How to invite someone to a single project or How to invite people to your workspace.

Before you start#

• You need to be the workspace Owner, an Admin or a Designer to change who can access the project.
• The other person needs a TeleportHQ account and a workspace with room for one more project. A trial workspace holds 1 project. See How many projects can I have?.
• Anyone with a Can clone link can copy the project, not only the person you send it to.
• Your keys stay with you. A copy never gets the project's Secrets (the API keys and passwords in Project settings → Secrets), its payment provider set-ups or its reCAPTCHA keys. The other person adds their own keys in their copy.

Give someone a copy of your project#

1. Share a Can clone link#

1. Open the project in the TeleportHQ editor.
2. At the top right, click Share.
3. In the Collaborators window, under Public access, choose Can clone: "Anyone with the link can use as a template".
4. Click Copy link.

5. Send the link to the other person, for example by email.

2. The other person clones it#

Send these steps to the person who receives the link:

1. Sign in to TeleportHQ, then open the link.
2. At the very top of the editor, a blue bar says "You are inside a cloneable project. Clone the project to make your own changes." Click Clone.
3. In the Save public project to your workspaces window, choose a workspace in the menu.
4. Click Save project. The copy opens in their editor.

If they have only one workspace with room, TeleportHQ saves the copy there without asking.

3. Tidy up#

1. After they have their copy, open your project, click Share, and change Public access back to Can view or Private. Private needs a paid plan.
2. If you no longer need your original, delete it. See How to delete a project.

Check that it worked#

The other person sees the copy as a new project card in their workspace. It's theirs to edit, publish and pay for. Your original project stays in your workspace until you delete it.

Troubleshooting#

"Projects limit reached" The other person's workspaces have no room for another project: "All your existing workspaces have reached the projects limit." They need to delete a project or upgrade a workspace, then open the link again.

The other person doesn't see the Clone bar They're probably already a collaborator on your project, or they aren't signed in. The bar only appears to signed-in people who can't edit the project. Someone who isn't signed in sees "Register for free to save your project" instead. Ask them to sign in with an account that isn't a collaborator on the project.

"Could not clone project" The copy couldn't be created. Ask them to try again in a moment.

Good to know#

• What moves with the copy: pages, design, files, languages, the plugins that are switched on, and the database with the content you wrote yourself, such as products, blog posts, what can be booked with its opening hours, vouchers and the tables of a web app. Forms are copied as the other person's own forms: new submissions go to their copy, and notification emails go to the owner of their workspace instead of to your recipients.
• What never moves with the copy: Secrets, payment provider set-ups (each provider shows as not set up until they enter their own keys), reCAPTCHA keys, the AI assistant chat's provider key, and the data your visitors and customers created: your site's user accounts, orders, bookings, comments and subscriptions.
• Your addresses and accounts are taken out. In the copy, your workspace members' email addresses (for example on order alerts, workflow notifications or invoice details) are replaced with the other person's workspace owner's address. Your Google Analytics and Google Tag Manager ids are removed.
• The copy starts Private in the other person's workspace, whatever your Public access setting was.
• What stays with you: the published site, the custom domain, deployments, the GitHub connection, collaborators and any add-ons such as Web App slots. You keep paying for those until you cancel them.
• The other person publishes their copy themselves, and connects the custom domain to it. Remove the domain from your project first, so it's free to connect to theirs. See How to connect your own domain.
• Moving a project between your own workspaces isn't available. The Clone bar doesn't appear on your own projects, and Clone on the dashboard copies a project only inside the workspace you're in. To copy a project inside the same workspace, see How to duplicate a project.