FluentPro Help Center

What do you need help with?

Asana -> Project for the web migration supported entities

In this article, we will review the Asana -> Project for Web migration supported entities. 

Please note: All information in this article also applies to the Asana-> Planner (premium plans) migration scenario.

Source System Entities

Supported

Target System Entities

Notes

Workspaces/Teams (for Organization)

+

Microsoft 365 groups

Microsoft 365 groups are created with the source Workspace/Team names if the corresponding Group Creation Mode is selected in the Migration Settings

Workspace/Team members

+

Microsoft 365 group members

Source Workspace/Team members are added as members to target Microsoft 365 groups if the option ‘Migrate all source workspace/team members’ is selected in the Migration Settings. The corresponding users should already exist in the target tenant and be mapped 

Users

Users

Users themselves are not migrated but mapped with the target users. Necessary users should already exist in the target tenant

Projects: Public to Team, Private

+

Project for Web projects and Microsoft 365 groups

New Microsoft 365 groups are created as Public ones. Microsoft 365 groups are created with the source Project names if the corresponding Group Creation Mode is selected in the Migration Settings.

Archived Projects

+

Project for Web projects and Microsoft 365 groups

 

Project Sections

 

+

Project Buckets

 

Project Tasks

+

Project Tasks

 

Project Subtasks

+

Project Subtasks

Project subtasks are migrated as subtasks, the hierarchy will be preserved.  

Milestone tasks

+

Project Tasks

Milestone tasks are migrated as regular tasks

Approval tasks

+

Project Tasks

Approval tasks are migrated as regular tasks. 

Task and Subtask field values

+

Task field values

Please refer to the list of supported source and target task fields below.

Task Custom Field values

+

Task field values

Please refer to the list of supported source custom fields below.

Task user assignments

+

Project task user assignments, Microsoft 365 group members

Mapped users, assigned to tasks in the source Project, will be added as members to the corresponding target Microsoft 365 group and assigned to tasks.

Project members (with Edit and View access) 

+

Microsoft 365 group members

The corresponding users should already exist in the target tenant and be mapped 

Project owners

+

Microsoft 365 group members

Mapped users that are source Project owners are not added to the target group owners, but to the group members.

Task Collaborators

+

Microsoft 365 group members

Mapped users, that are added as Task Collaborators in the source Project, will be added as members to the corresponding target Microsoft 365 group

Project Details, Views, Forms

 

 

 

Supported Source and Target Item Fields

Source Task Fields

Supported

Target Task Fields

Notes

Section name

+

Bucket name

 

Name field

+

Title field 

Notes field

 

Assignee field

+

Assignments field 

Mapped resources assigned to tasks in the source Project will be added:

  • As members of the corresponding target Project, Project Team
  • Microsoft 365 group, if a source user assigned to a project task is mapped with a target user that is an AD user.
  • Dynamics bookable resources

Start Date field

+

Start field

 

Due Date field

+

Finish field

 

Completed checkmark

+

Progress (% Completed) field

By default:

  • Yes – 100%
  • No – 0%

Can be remapped

Description field

+

Notes field

4000 characters max + links to attachments if the Attachments token is not provided for the Project for the Web connection

Attachments

+

Attachments 

Attachments are migrated to the Attachments task section if the Custom Fields and Attachments token is provided for the Project for the Web connection. If the token is not provided, all attachments will be added as links to the task Notes. In both cases, all file attachments from the source task will be migrated and added to the task folder on the group SharePoint site in the target tenant.

Comments

+

Notes

Comments are not migrated automatically. However, they can be transferred to the Notes target field if the task mapping is set up accordingly.

Tags

+

Labels

Tags to Labels can be migrated if the Custom Fields and Attachments token is provided for the Project for the Web connection.

Cover image

+

Attachments


Task Updates (history)

̶

 


Projects Task field

-



Task Dependencies

+

 Task Dependencies

Only supported Dependencies, other will be skipped, e.g.:

  • Dependencies from another project
  • If summary depends on its child or child on its summary.
  • If a task has more than 20 dependent tasks

 

Supported Task Custom Field types for mapping

Source Task Custom Field Type

Target Task OOB Field

Name 

Title

Notes

Date (Start and Due dates)

Start

Finish

Notes

Boolean (Completed)

Progress (Percent Complete)

Assignee 

Assignee

Attachment

Attachment

Single-select (Drop-down) field

Progress (Percent Complete)

Notes

Title

Priority

Labels

Multi-select (Drop-down) field

Progress (Percent Complete)

Notes

Title

Priority

Labels

Text field

Notes

Title

Priority

Number field

Progress (Percent Complete)

Effort

Effort Remaining

Priority

Notes

Comment

Notes

Tag Label
Date field

Start (Date) field

Finish (Date) field

Notes 

Title

People field
Assignments (Assigned To) field

 

Supported Target Custom Fields 

Source Task Custom Field Type

Target Task Custom Field type

Notes

Text

Single-select (Drop-down) field

Multi-select (Drop-down) field

Name

Date (only Start and Due date fields)

Date custom field

Number

Text

 

Number

Single-select (Drop-down) field

Multi-select (Drop-down) field

Number

 

Date (Start and Due date fields)

Date custom field

Date

Notes

 

Single-select (Drop-down) field

Boolean (Completed)

Yes/No


Text

Single-select (Drop-down) field

Multi-select (Drop-down) field 

Choice

 

 

 

 

Was this article helpful?

Table of contents

    Back To Top