We currently have a function to let you Cut/Copy and then Paste a project from one account to another, but it’s starting to look like this is a bad idea because it is very difficult to implement cleanly.

The underlying problem is that a project is more than a collection of cards: it is also part of a network of people relationships, connections to other projects, etc., and these can’t all be moved cleanly from one account to another.

For example, consider a series of projects that are organized as Scrum Boards, linked to a shared Backlog within one account. If we copy and paste one of these projects to another account, what exactly should happen to that Backlog? It’s not an easy matter to simply copy the entire Backlog over as well, to the new account — that may not be the most sensible outcome in all, or even most, circumstances.

Consider an even more basic problem: a project has a bunch of folks working on it today. If you copy and paste the project to another account, what should happen to this team? These folks may not have previously been part of the new account’s team: they would have to get invited to join projects in that account, and very likely the new account’s owner would have to upgrade her account to support the larger team size.

There a bunch of conundrums like this to work through, and it’s not clear that this is even worth the considerable effort it would take to create a bullet-proof solution – how often, after all, do people need to move a project from one account to another?

If the answer is “not very often”, then it’s probably better for us to remove this functionality, rather than leave users with a less-than-great experience…