Bulk moving Asana projects from one team to a different one

English Forum Developers & API
, ,
1

I realize how the new sharing/membership works among teams, with the ability to share a project to multiple teams, remove from a previous team, etc. That’s great.

But this doesn’t actually change the team that shows in the “Project details” UI, or within the API response for the project’s team GID.

I’m hoping to bulk move 100 projects from an old “Team” in Asana, so that we can then delete that team (since Option To Archive Teams or Move multiple projects from one Team to another at once hasn’t happened yet…)

I can manually go in and update the sharing/membership and the project details > team of each project, but that’s cumbersome and time consuming.

Is there a way to update the team GID associated with a project via the API?

Otherwise, if we adjust the membership settings only (which we can do via API), but the actual “team” value associated with the project remains the same (to the old team), what will happen if we delete the old team from Asana?

Will those projects be deleted too? Or will they continue to exist in the new team they were “shared” to?

If the latter, when will the UI be updated to more accurately reflect this, since the Project Details > Select a Team (and thus the API result) is confusing compared to the share/membership settings.

2

Hi @FreshyJon,

For now, you can update the team property of a project to “move” it to a different team.

However, please realize that this will only be true for another 3-4 months or so, as Asana is moving to a different model where teams are no longer viewed as containers for projects but rather are viewed as groups of users who can have project memberships. When that happens, the team property of a project will be obsolete. See [Change] Teamless Projects.

2 Likes
3

Hi @Phil_Seeman , I’m guessing this is the team set in the project properties.

When updating that in the interface, you get the choice to also update the access.

Would changing this through the API do this automatically? Otherwise it’d still be a manual operation to update the access.

4

@Jan-Rienk,

Good point - because updating the team property on a project is a “legacy” API action that predates the concept of a team membership on a project, it doesn’t touch or alter the membership of the project; so one would need to update the project membership independently if appropriate.

2 Likes
6

Hey @FreshyJon , it will also delete all projects that have that team as the ‘owning’ team in the project details (the team property) So do NOT do it!

This will likely no longer be the case after the update that @Phil_Seeman mentioned above.

1 Like
7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.