Table of Contents
Introduction
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 app.altosio.com
Key Benefits
The migration tool is reliable, secure and lightning fast.
What is migrated?
- Workspaces
- Teams
- Projects and personal projects
- Permissions and memberships
- Tasks
- Attachments
- Sections
- Task details including title, collaborators, assignees description, start date, due date, comments
- Subtasks and all their metdata
- Project and workspace level custom fields
- Portfolios could be migrated when the Asana projects are migrated
What to consider?
Important Limitations
There are some small limitations that you might need to be aware of. They are described below.
Moving projects from one Asana workspace to another has never been easier. While most of your data will be migrated, there are a few limitations that you need to be aware of:
- Asana APIs do not support migrating attachments larger than 100 MB. Attachments that exceed this size will be ignored.
- Asana APIs do not allow creating comments on behalf of users. The comments will be migrated and posted as the migration account.
- Asana descriptions formatting is limited to the Rich Text format provided by the Asana APIs.
- Workflows are not migrated.
- Formula custom fields are not migrated.
Security
Enterprise-Grade Security
The Altosio software runs in the Cloud and is hosted in Microsoft Azure data centers located in the US and the EU (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 support@altosio.com to get it.
No Data Storage
The Altosio tool does not store anything internally. It reads data in chunks and pushes them in real time to 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 that are migrated. This allows the customer to rerun the migration without duplicating data.
Requirements
Asana Requirements
All you need to connect to Asana, both in the source and destination, is an API token. This token can be generated by any Asana user, and will act on behalf of the user who generated it. It is important to note that the token will only see the projects that the user has access to. If you are not seeing a project in the Altosio list, this means that the user does not have access to this project in the source.
Licensing
Each Asana project migration consumes a Standard Planner migration license. The license is automatically allocated to the board and will get burnt as soon as the target Asana project gets created in the target.
License Details
- • License is board-based (not per user, task, or attachment)
- • Supports delta passes for multiple migration runs
- • Same license used across migration restarts
Configuration
1. Sign up and create your first project
First, create an account at https://app.altosio.com, validate it through the verification email, and then log in.
Once logged in, you’ll land on the home page where you can create your project. Click “New Project”, give it a meaningful name, and click create.
2. Create your connectors
a. Create your source Asana connector
- Click New connector, choose Source, then Asana. Click on Connect to Trello and follow the steps in the pop-up window, then click on Create connector.
- Follow this link to see how to generate your API token.
The creation of a source connector automatically triggers a discovery job of your Asana source environment, pulling the list of Projects you have access to, as well as source users emails.
b. Create your target Asana connector
- Click New connector, choose Target, then Asana.
Similarly, generate an API token from the destination Asana environment and create your connector.
Pre-migration assessment
Before running the migration, for larger migration projects, 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.
For more information about pre-migration assessment, please reach out to support@altosio.com
Migration
1. User mappings
Before running the migration, visit the Mapping table section of your project. You’ll find entries for your Asana users already prefilled. Add the equivalent email addresses of these users in Microsoft 365.
- If your users are using the same email nicknames, the mapping table won’t need to be filled out. The tool will know how to automatically map the users. However, if the users have different email nicknames (i.e source email is john@source.com and destination user is jdoe@destination.com), then the mapping is mandatory.
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
Target Project Name
- Display name of the project in the target.
Target Workspace name
- It is important to provide your correct destination Asana workspace name in this field. Altosio will connect to your workspace and create your project within this workspace.
Target Team name
- Name of the Asana team in the destination, under which the Asana project will be created.
3. Start Migration
Post-Migration
Revoke the Asana tokens
Once you are done with your migration, visit the Asana developer console and revoke your API tokens, both in the source and destination environments.
Support
Support is done by email at support@altosio.com or over Teams calls.
Need Help?
- Altosio support team will assist you throughout your migration project and will be pleased to help you run a successful migration.