How to transfer a project to another user?

[ldommer]

Select Topic Area

Question

Body

How do I transfer a project to another user? I started a repo and successfully transferred it to my client. The tied project I started remained in my account. How can I also transfer the project to my client?

[Anmol-Baranwal]

To transfer a repository to another user or organization on GitHub, you can use the "Transfer ownership" option in the repository settings.

Here are the steps to transfer your project to your client:

1. Go to your repository on GitHub and click on the "Settings" tab.
2. Scroll down to the "Danger Zone" section and click on the "Transfer ownership" button.
3. Enter the new owner's GitHub username or organization name in the "New owner's GitHub username or organization name" field.
4. Confirm the transfer by entering the name of the repository in the "I understand, transfer this repository" field and click on the "I understand, transfer this repository" button.
5. Your client will receive an email notification and will need to accept the transfer request within 14 days.

Note that you must be an owner or have admin access to the repository to transfer ownership. Additionally, if the repository has any forks, issues, pull requests, or releases associated with it, those will be transferred to the new owner as well.

[mdz-odoo]

adjustment to point (5), invitation shall expire within 1-day and at times it expires within few hours

[fnagel]

This comment has absolutely nothing to do with the actual problem described by OP.

[ldommer]

Hello and thanks for your answer. Not a repository, but a project. I already transferred my repository as this is well documented.

[Anmol-Baranwal]

I understood :)

As far as I know, there is no direct way to transfer a GitHub project to another user or organization.

If you want to transfer the contents of a project, one possible workaround is to create a new repository for the project and then transfer the repository to the other user as I mentioned earlier. Alternatively, you could export the project as a file and then transfer the file to the other user via email, cloud storage, or other means.

You can add collaborators with admin access.

[Anmol-Baranwal]

I just wanted to check in and see if you have any remaining questions or concerns about my answer. If not, would you please mark my response as accepted?

It would be greatly appreciated and it will also help other users who might be looking for a solution to a similar issue.

Since, there is no solution for this issue, it might be appropriate to close it.

[EnTerr]

is this still the case? i.e. Projects are not transferrable between user accounts or organizations?

[5rtecgit]

Nope! I transferred a repo to another user account, but the project remained and did not transfer. Is there any way? I need to do so as well.

[tahaani]

I did the same thing and was not able to transfer the remaining project either.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[MichaMican]

The classic Projects are moved with the Repository transfer. The new Project can only be copied to a new owner but in that case you can only copy draft tasks on the board but NOT the issues/PRs

Transfers & Copies can be started via a button in the Danger Zone in the according settings pages

[pombredanne]

@MichaMican you wrote:

The classic Projects are moved with the Repository transfer. The new Project can only be copied to a new owner but in that case you can only copy draft tasks on the board but NOT the issues/PRs

Thanks. It makes the new Project a PITA then. Is there a way to convert a new one back to classic?

[MichaMican]

I don't think there is a way back unfortunately. Classic Projects are deprecated and creation of new ones will not be possible starting 23.08.2024 (https://github.blog/changelog/2024-05-23-sunset-notice-projects-classic/#:~:text=GitHub.com%20Timeline&text=Creation%20of%20new%20classic%20projects,be%20migrated%20to%20new%20projects.)

I also wasn't able to find any feature request in this regard - so i guess the only way to migrate it for the future is either via script or manually

[pombredanne]

FWIW, neither https://github.com/orgs/community/discussions/8548 nor https://stackoverflow.com/questions/75967186/copy-github-project-including-items have an answer

[Asha31s]

Go to the project's settings, then scroll down to the "Danger Zone" section. Click on "Transfer ownership," enter the new owner's username, and follow the prompts.

[bisacciamd]

Currently, on Github, Repositories and Projects are not the same. Your answer refers to transferring a Repo not a Project

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[MarianCN]

Up please

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[rbuckland]

This is not dormant. We need a way to transfer a "project" to a new owner, preserving the issue meta-data a long with the transfer.

[pombredanne]

@rbuckland this may help https://gist.github.com/keshav-space/f0afa93cb6ec1b9a39299deef9d6858b by @keshav-space and we have used this to port projects boards between orgs nicely.

[pombredanne]

For instance CRAVEX moved to https://github.com/orgs/aboutcode-org/projects/8 (view) (now emptied) was moved to 03-CRAVEX (now closed and finished)

[fnagel]

Almost three years later and this is still an issue :-(

[fardarter]

@fnagel There are some imperfect solutions here: https://github.com/orgs/community/discussions/8548