Support mapping users to different email domains

[Steven Grimm]

Use case: Splitting off a separate organization from an existing one, such that people get email addresses with a different domain name and no longer have access to the original organization. (Think spinning off a subsidiary from a parent company.) You want to move the Asana projects to the new organization and have the tasks assigned to and followed by the right people, but the Asana user IDs aren’t the same.

This patch is what I did to solve that problem. It may or may not be suitable to include in the public version of the tool. The basic idea is to prefer an exact match on email address if the same email address is in the user list in both the source and destination workspaces. (In that case, the behavior is the same as the existing tool.) But in cases where a user doesn’t exist in the destination workspace with an exactly-matching email address, fall back to matching on the local part of the address, ignoring the domain name.

This allows tasks assigned to [e-mail] to be assigned to [e-mail] in the new workspace.

Obviously this isn’t a very sophisticated solution, but it solved the problem for me and may be useful for others.

[Mike Houston]

This is something that has been a frustration for a lot of people, so thank you for the patch.

My goal in the long term is to provide several custom remapping options for users, tags and custom fields which would allow you to match up the old and new assignments for these values before the copy takes place. That most likely will be part of Ditto, which is a replacement for this tool, but I can’t say how long it will be before that is implemented.

In the meantime this is an excellent workaround. I don’t think I can turn it on permanently in the public version since it is a fuzzy match, but perhaps behind an option switch for those who it would help.