All information in this article applies to the Project Online -> Planner (premium plans) (Project for the web) migration scenario.
General Limitations
Area |
Details / Description |
|---|---|
| Calendars | It is recommended to create a calendar on the target to correspond to the source to migrate data as accurately as possible. If a custom calendar is set for Planner Premium projects in the Project Parameters, it is also recommended to apply that calendar to the Bookable resources added to task assignments in the migrated projects. |
| Schedule Mode | Use the Fixed Duration schedule mode in Planner Premium for accurate migration. Although this setting is not available in the user interface, it can be configured through the Power Platform (Power Apps) environment settings. By default, Planner Premium uses a Fixed Duration scheduling model, but if a different calculation type is set at the environment level, it may affect how task data is migrated. |
| Summary Tasks | Not migrated directly, but calculated automatically from sub-tasks. If the source summary task has assignments, they will not be added to the target summary task, so the total effort may differ from the source total work. |
| Tasks with Missing Dates | (Start date = Start date; Finish Date = Start date + duration) If a source task has no dates but has: a) work values → migrated with today’s date. b) duration only → migrated without dates or duration. c) dependency → migrated with automatically calculated dates. |
| Milestones | Milestones that have a progress value greater than 0% but less than 100% while their duration = 0 are migrated as Not Started. |
| Dependencies | All dependency types migrate if token is generated for Planner Premium during the connection step. Without a token, only Finish-to-Start is supported. Dates of tasks with dependencies can be moved if it is not possible to set the dates as in the source. |
| Hierarchy Levels | Maximum: 10 levels. Deeper levels will be set to the last level. |
| Weekends | Task dates move to the next available working day according to the target calendar. |
| Maximum Total Tasks per Project | 3,000 tasks. Additional tasks will be skipped. |
| Maximum Total Duration per Project |
3,650 working days (10 years). If the difference between the earliest source task start date and the latest source task due date is more than 3,650 working days, then: a) Project Start Date will be set to 3,650 days from the Project Finish Date. b) Project Finish Date will be set to the latest source task due date. |
| Task Dates Outside Project Range (Start and Finish) | a) Both out of range → the dates will not be set. b) One out of range → the second date will be set to the one that is within the project range. |
| Maximum Task Duration | 1,250 working days. Tasks longer than this will have a Start date equal to the Finish date. |
| Supported Task Date Range |
1/1/2000 – 12/31/2149. If the source task dates are set to the dates that are out of the supported range, then the target task dates will be set to: a) if both dates are less than 1/1/2000, dates will not be set;
b) if one date is less than 1/1/2000 and the second date > 1/1/2000, both dates will be set to the date > 1/1/2000.
|
| One-Date Tasks | If only the Start or Finish date exists, both dates will be set to that value. |
| Buckets | All tasks from the Project Online Project will be migrated into one default bucket. |
| Labels | Max 25 Labels per project in Planner Premium. If there are more, only the first 25 will migrate; others will be skipped. Migration to Labels requires the Custom Fields and Attachments (PSS) token to be added during the connection step. |
| Lookup Values | Project Migrator does not transfer lookups; it only transfers their corresponding values to the Labels or custom fields of Choice type in Planner Premium when a token is added during the connection step and a mapping is configured (the fields can be created on the target during migration with the corresponding lookup values). A maximum of 25 lookup values can be added to the fields in Planner Premium. |
Assignments Migration
Area |
Details / Description |
|---|---|
| Users | Users are not migrated automatically. Required users must already exist in the target tenant. |
| User Mapping | Source users must be mapped to target users in User Mapping. Display Names and accounts can differ; a full match is not required. |
| Assignments | Task assignments migrate only for mapped users. Mapped users assigned to tasks will be added as: a) Members of the corresponding target Project, Project Team. b) Dynamics Bookable Resources. c) Project Owner → added to M365 group as a member. d) Sync account → added to M365 group as owner and member. |
| Generic Resources | Only Bookable Resources are displayed in the user/resource mapping. |
| Maximum Total Resources per Project | 150 unique assignments will be added. Others will be skipped. |
| Maximum Users per Task | 20 users can be assigned per task. Extra assignments will be skipped. |
Microsoft 365 Group and Project Creation
Area |
Details / Description |
|---|---|
| Existing Microsoft 365 Groups | Migration to existing groups requires the Project connection account to be a member or owner of that group. |
| Target connection account | The target connection account must be an owner and member of an existing Private M365 group to add members during the migration (in case the account is not a Global Admin in the target tenant). |
| New Groups Creation | If new M365 groups are created, the target migration account will be set as the group owner and member. |
| Group Creation Limit | Non-admin accounts can create a maximum of 250 M365 groups in the tenant. Only the groups created during the migration that fit the total limit of 250, along with the existing groups previously created by that user, will be added to the target. |
| “Create Groups Using Project Names” | If a group/project with the same name already exists → data will be merged into the existing one. |
| “Create All Projects in One Group / Create New or Merge with Existing Projects” | If existing projects have the same names → data will be merged into existing projects. With these settings selected, if there are existing Projects in the specified Microsoft 365 group with the same names as the migrated ones → data will be merged into existing projects. |
| “Create New and Remove Existing Projects Before Creating” | If there are existing Projects with names that match the selected source Projects names in the target Planner Premium, such target projects will be deleted (with tasks) before creating new Projects with the same names. |
| Project Team Members | All mapped source Project team members are added to the target M365 group if they are Graph users. |
| Group Visibility | All groups will be created as public. Existing groups keep their current settings. |