Asana logo

Table of Contents


Altosio offers a great tool to migrate project management data from and to several vendors. It allows you to seamlessly switch from one software to the other, with a guarantee of no data loss. The migration software runs in the cloud, so you do not have to worry about installing anything. Everything is accessible from your web browser at The migration tool is reliable, secure and lightning fast.

What is migrated in an to Asana migration scenario?

  • Workspaces
  • Folders
  • Boards
  • Tasks and subtasks
  • Files
  • Comments
  • Custom fields are mapped to new custom fields in Asana

What to consider?

Asana and are quite similar in shape especially in the List and Kanban views. Your end users will not find any issue coping up with the changes as both tools look quite the same, and have almost the same functionalities. However, there are some small limitations that you might need to be aware of:

  • Asana APIs do not allow migrating any attachment that exceeds 100Mb in size. Any file attachment that exceeds this size will be ignored.
  • Some custom field types do not have an equivalent to them in Asana. They will be skipped.
  • Setting the Start Date on tasks in Asana requires a Premium Asana plan. 
  • Labels and tags are different in color and number between Asana and Altosio will migrate as many equivalent labels as possible. 
  • Comments will be posted in Asana under the name of the token holder. The metadata (real sender and real date-time of the comment) will be appended on top of the comment. This is an Asana API limitation.


The Altosio software runs in the Cloud and is hosted in Microsoft Azure data centers located in the Netherlands. Altosio is able to provide you with a static IP address from which the migration will run in order to secure your environments with Firewall access accordingly. Please reach out to to get it. You can also visit our security statement here.

It is also worth noting that the Altosio tool does not store anything internally. It reads data in chunks and pushes them in real time in the target. No data is cached or stored in the hard drive of the servers running the migration. Altosio does however store the unique Ids of files and tasks/cards that are migrated. This allows the customer to rerun the migration without duplicating data.
Altosio’s migration tool does not edit the source environment in any way. It copies the data to the target without altering it. Altosio needs a read-only access to the source.



To connect to, all you need is to install the Altosio application in your environment. Once installed, you need to consent to this application to read data from your Monday workspaces and boards

         2. Asana

To connect to Asana, all what you need is to provide a Token that allows us to post data into Asana environment. 



Each board migration consumes a Standard Planner migration license. The license is automatically allocated to the board and will get burnt as soon as the Asana project gets created in the target.
The license is board based and does not depend on the number of users, tasks or attachments there are in the board.
The migration supports delta passes, which means that you restart the migration several times and it would still consume the same license that was originally assigned to it.
For any further inquiries related to licensing, please reach out to


  1. Sign up and create your first project

First, please create an account under, validate it through the validation email, and then log in.
Once you log in, you land on a home page where you create your project. Click on New Project, give it a meaningful name, and then hit Create.
Click on the project name to open it.

       2. Create your connectors

The next step in the process is to create your connectors. Since this guide is about to Asana migration, we will create two connectors, the source being a connector, and the target being an Asana connector.

         a. Create your connector:

Under the connectors page, click on New Connector, choose Source, and then select

Give your connector a name and click on “Install Altosio App”. This will open a new window that asks you to install the Altosio Application in your environment.

Once you install the application, the window will be automatically closed. Please click on Connect to to authorize the use of this application in your subscription. This opens another window in which you have to click on Authorize.

Once authorized, the window is automatically closed and a code is generated. Finish the creation of your connection by clicking on “Create connector”.
The creation of connectors is followed by a test connection that ensures that your configuration is correct and that Altosio can connect to the source and destination. If your test connections are not successful, please check your token values and make sure you have authorized Altosio in Trello and

The creation of source connectors automatically triggers a discovery job of your environment, bringing the list of workspaces, boards, and users and populating both the Planner List section and the Mapping table. 

                b. Create your Asana connector:

Click on New Connector, choose Target, then Asana. You should provide an Asana Token. Please check this article that explains how to generate it.



Pre-migration assessment 

Before running the migration, Altosio provides you with a way to assess your migration. The Audit task allows you to identify on each board if you will hit the limitations that exist between the two environments. The limitations are listed above in this article.
For more information, please reach out to


  1. User mappings

Before running the migration, it is very important to visit the Mapping table section of your project. In this section, you will find entries for your users already prefilled. You need to add the equivalent email addresses of these users in Asana. If the email addresses are the same between the source and destination, you can leave the mapping table empty. Altosio will automatically map the users based on the source email addresses.
The mapping table allows Altosio to correctly map the users in the target. It allows a correct migration of the files metadata and the list of owners on each task.
With an empty mapping table, the migration would still run, but the list of assignees will not be migrated correctly.

        2. Understand the target fields

In a migration to Asana you can configure where you want to migrate.

  • Target Plan Name: This is the name of your destination Asana Project. This project does not have to exist. If the project exists, Altosio will migrate the content of the source Asana Project to this existing Asana Project. If it does not, Altosio will create a brand new Asana project with the name provided and will map the permissions.
  • Target Email Nickname: This is the Asana Workspace you are migrating to. The Workspace needs to exist in Asana before the migration. You need to provide the correct name of the Workspace you are migrating to, otherwise, the migration will fail.
  • Target Group Name: This is the name of the Asana team in which your Asana project will be migrated/created. This team needs to exist and have the list of your users invited to it. If the Team with the provided name does not exist, Altosio will provision the team for you. However, this is not recommended as a newly created team won’t have the team members added, and therefore the permissions will be lost. We recommend that your Asana Teams are pre-created in the target.
  • Target Channel Name: This field is not used for this scenario.
        3. Migrate

Once everything is configured, please get back to your Planner list page, select the board or boards you want to migrate and then click start.
This action should prompt a selection of target connector. Select your target connector and click migrate.

The board will remain queued until it finds a spot on the platform. Once the migration starts, it will show in a “Working” status.
You can click on details to check the logs and the statistics.

If the migration succeeds, the status will turn into Success. Otherwise, if there is an issue with the configuration, the migration will show an Error status. Please click on details to check the logs to see the reason behind the error. Eventually, please reach out to our support team at to seek help if needed.


Once your boards are fully migrated, it is important to revoke the Altosio access from your and Asana subscriptions.

Delete the App from

Once your boards are fully migrated, it is important to revoke the tokens. Please delete the Altosio application from your environment. Visit your subscritpion developer center, click on the application and then delete it.

 Revoke your Asana tokens

Once your boards are fully migrated, it is important to revoke your Asana tokens.
Visit this link in both your source and destination environments and revoke the created token.

 Delete your Altosio Project

If you are sure that your project is finished and that everything seems to be migrated correctly, you can go ahead and delete your project from the Altosio platform. Inactive projects will be automatically deleted after 3 months of inactivity as per the GDPR regulations.



Support is done by email at or over Teams calls.
Altosio support team will assist you throughout your migration project and will be pleased to help you run a successful migration.