Migrate LiquidPlanner to Asana

Has anyone migrated from Liquid Planner to Asana?

Any tips?

Thanks

Hi @Richard_Getz1,
welcome to Asana, I’ve migrated from LiquidPlanner too.

I don’t know what strategy are you using for planning with packages in LiquidPlanner, but I can suggest you a way to replicate the most common LiquidPlanner’s behavior in Asana.

image

The Premium plan is required at minimum.

There are several strategies for Asana, depending about how many clients you have, the project size and type of collaborators. I’m just showing you a base system where LiquidPlanner’s packages are used for weekly sprints.

The setup

Create a template project named like “Week 2020” then assign it the white color (it is the color I use for templates) and set it as a template.

Enter into the template project and sort it by Assignee or just leave the default to sort manually.

Create the two custom fields “Est. Min” and “Est. Max” for best case and worst case estimations. Set them like the image below.

If you use activities for billing, create a new drop-down custom field “Activity”, then create the activity types you like.

For time tracking I suggest to use Everhour integration, or you can choose another one from the integrations page.

Asana does not have an On Hold functionality, so create a custom field “Issue Status” as drop-down with the following options that I suggest: On Hold and Progress.

For the LiquidPlanner’s Delay Until and Deadline fields use the task’s due date.

Tags and dependencies are already like in LiquidPlanner.

How to use it

Duplicate the project template and create several projects, one for each next week, like the image below.

image

Now you can plan the tasks to weeks simply connecting them to the weekly project from other projects.

All task have to be created in their respective projects.

In LiquidPlanner it is possible to nest a task into several folders, but in Asana it’s better to keep projects as flat as possible. I suggest to use only three levels: projects, sections and tasks. Sub-tasks are better just for activities, like Checklists in LiquidPlanner. If you need to break down a task, I suggest two options: create the sub-tasks then link them to the parent project, or replace the task with more tasks.

Further details

Asana’s workspaces can be used in place of LiquidPlanner’s clients, if you have few clients. With more than a dozen of clients I suggest to create a workspace that just keeps clients as projects and only a single workspace for all related projects.

I’m really missing the automatic planning feature of LiquidPlanner, even the Instagantt integration can’t match that functionality, so I’m thinking about creating a tool to make the gantt chart in real time. If somebody is interested, please reply with a message to this conversation.

I can be more specific if you tell me more about how you use LiquidPlanner and for what type of projects.

1 Like

Hi @Davide_Muzzarelli I’ve been on Asana for years and my current employ since I started with them in September. They continued with LP as it has good time tracking, something Asana lacks.

It is in fact that time tracking that is the largest holdover. Sure, there is Harvest, but this is only on a task, not subtask level. I will review Everhour. Thank you!!

How did you migrate or backup the current work in LP?

1 Like

You are welcome @Richard_Getz1 :slight_smile:

I have many projects for many clients. I did it in three steps:

  1. Create new projects in Asana only.
  2. Create new phases of old LiquidPlanner projects in Asana.
  3. Leave old phases and projects end in LiquidPlanner.

This took few months but without interruptions and no time lost in migrations.

1 Like

oh, so manual only. No automation in bringing LP over to Asana.

Thanks @Davide_Muzzarelli much help here.

I could migrate using API, but the job was not worth it since most tasks are completed, the team had to get used to Asana and data is more useful as exported into Excel.

1 Like