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 Planner to Trello migration scenario?

  • M365 Group. This is translated to an Trello organization
  • Microsoft Planner Plan. This is translated to Trello board
  • Group / Plan members and owners
  • Planner buckets
  • Files
  • Comments
  • Tasks
  • Tasks checklists
  • Task details including title,  assignees description, start date, due date, comments, attachments, completion and tags / labels

What to consider?

Trello and Microsoft Planner are quite similar in shape. 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:

  • Planner allows one single checklist. Trello allows several checklists. This won’t be a migration limitation as Trello offers more flexibility in this case.
  • Labels and tags are different in color and number between Trello and Planner. Altosio will migrate as many equivalent labels as possible. 
  • Comments will be posted in Trello 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 a Trello 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.


        1. Planner

To access Planner, Altosio needs:

  • An admin consent to use the Altosio Azure Active Directory Application from your tenant. This requires a Global Admin account to grant the admin consent.
  • Your tenant’s domain. This could be either your commercial domain “” or your M365 vanity domain “”.
  • A migration account (email and password). This account does not need any admin privileges or roles. It simply needs a valid license that allows it to access Microsoft Teams. (an E3 license for example). We recommend that you create a dedicated user for your migration ( for example) that can be deleted after the migration.

    2. Trello

To connect to Trello, all what you need is to provide an App Key and Token that allows us to push data to your Trello 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 Trello board 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. The licenses are not refundable.
For any further inquiries related to licensing, please reach out to


  1. Sign up and create your first project

First off, please create an account under, validate it through the validation email and then login.
Once you login, you will land on a home page where you will have to 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 a Trello to MS Planner migration, we will create two connectors, the source being a Planner connector, and the target being an Trello connector.

         a. Create your Planner connector:

Under the connectors page, click on New Connector, choose Source and then Planner.
Provide the tenant name (your tenant name is the left part of your Sharepoint URL. If your Sharepoint URL looks like, then your tenant name is “mycompany”).
Provide the domain of your tenant.
Click on Grant Admin Consent. This will redirect you to a new page where you will have to login with your Global Administrator credentials and accept to install the Azure Active Directory Application on your tenant.

Please note that this application should be removed from your tenant after migration.


Please note that you can decline installing this application on your tenant. Instead, you can create your own Azure AD application, and provide the Application Id and Secret to Altosio. The tool will then use your own application credentials to connect to your M365 tenant.
Next on, you should provide an email and password of the migration account. This should be a licensed account with access to MS Teams application. This account does not have to have any admin privileges. (Standard user with no access to any admin portal).

The creation of a source connectors automatically triggers a discovery job of your Planners in your M365 tenant. This job will pull the list of Plans you have and will fill the mapping table with the usernames of the users in M365. To be able to pull the list of Plans, the migration account needs to have access to all of the plans. Altosio will automatically add your migration account as Member of your M365 Groups in the source in order to query each group and see if they have any Planners residing inside of them.

                b. Create your Trello connector:

Click on New connector, choose Target, then Trello. You should provide an AppKey and 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. In general, there are no limitations for this migration scenario.
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 Planner users already prefilled. You need to add the equivalent email addresses of these users in Trello. 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 assignees on each Planner 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 Trello, you can configure where you want to migrate.


Trello boards live inside a Trello Workspace, which lives inside a Trello Organization. Altosio does not create Trello Organizations. It can however create Trello Workspaces and boards.
You can eiher migrate to a new workspace/board or merge the data into an existing one.
If you would like to migrate into an  workspace/board, you need to provide the correct names of your workspace and board in the target fields.

  • Target Plan Name: This is the display name of the Trello board in the target. If you provide the name of an existing boardi n Trello, Altosio will migrate the data into it. It is necessary to have the Trello organization ready before the migration, with the users already invited to it.
  • Target Email Nickname: This field is not used for Planner to Trello migration scenario. It can be left empty.
  • Target Group NameThis is the name of the Trello workspace. If you want to migrate to an existing workspace, please provide the name of the workspace in this field. If no workspace is found with the value provided here, a new workspace will be created.
  • Target Channel Name: This field is also not used for a Planner to Trello migration scenario. You can leave it empty.
        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 Migration Actions then Migrate.
This action should prompt a selection of target connector. Select your target connector and click and hit migrate.



The board will remain in a Queued state 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 delete the migration account from your tenant and remove the Altosio Azure Active Directory (AAD) application.
To remove the application, please follow the steps detailed below:

  1. Go to your Azure portal via this link
  2.  Under Azure Services, click on Azure Active Directory as show in the screenshot.
        3. On the left-hand side menu, click on Enterprise applications.

        4. Among the applications, look for the Altosio application and click on it to open it.

        5. On the left hand-side menu, click on Properties, then delete and confirm the deletion.

Please do not forget to revoke the Trello access token as well.


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.