Transferring Projects & Automations After a Team Member Leaves

Transferring Projects & Automations After a Team Member Leaves

Hi! I’m looking for some guidance on the best way to handle transferring work from a team member who recently left our organization.

She was essentially our Asana manager/owner and had been in the middle of building out several projects and workflows for our team. A lot of what she created is still in the framework/building stage, meaning there are projects with tasks that haven’t been assigned to anyone yet because they were intended to be populated or assigned as the workflows were rolled out.

My main concern is making sure none of that work gets lost when we transfer/deactivate her account. Essentially, I’m trying to figure out the safest way to preserve everything she built without:

Losing unassigned tasks or partially built project frameworks
Breaking existing Rules/automations
Accidentally assigning a large number of tasks to the person receiving her work
Losing anything that may not be obvious because it was still being built rather than actively assigned

Has anyone dealt with a similar transition? Is there anything we should audit or document before deactivating/transferring her account, particularly around Rules, project ownership, templates, or unassigned work?

Thank you!

Welcome, @Katherine_Vernon,

I address this question here:

Thanks,

Larry