In this article, we will review common errors and warnings for Monday.com -> Planner migration scenario.
Another object with the same value for property mail Nickname already exists
Error: Request_BadRequest: Another object with the same value for property mailNickname already exists.
Cause: This error may occur on creating Microsoft 365 groups in the target tenant while migrating to Microsoft Planner. The error indicates that there is already an existing target group with the same property mailNickname, i.e., the same primary email address (and name) as the group that is created during the migration. As each Microsoft 365 group should have a unique mail nickname in the tenant, the creation of another group with the already used mail nickname is not allowed.
In case the target migration account is added as a member or as an owner to the existing target group with the same mail nickname, it will be found and updated during the migration.
If the target migration account is not an owner or a member of the existing target group and has no access to it, the group migration will fail.
Possible solution:
1. Check if there is an existing Microsoft 365 group in the target tenant with the same mail nickname/primary email address and name as the group that needs to be created or updated during the migration.
2. If the existing group should be used, make sure to add the target migration user account as a member or an owner to that group in the target tenant.
3. If a new group should be created, change the primary email address of the existing target group, or change the name of the source group or Plan that is used for the group creation.
4. Restart the uncompleted migration.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
Unable to add user (user account). Insufficient privileges to complete the operation.
Error: Unable to add user (user account): Authorization_RequestDenied: Insufficient privileges to complete the operation.
Cause: This error may occur on adding users as members and owners to the Private target Microsoft 365 group. In case the migration is performed to an existing Private Microsoft 365 group and the target migration account is not a tenant admin, it should be added to the group owners as well as members to be able to add other users to the Private group during the migration.
In case the target migration account is a regular user and is only a member, but not an owner in the existing Private group in the target tenant, it will not have permission to add owners and members to the group, and the mentioned error will occur.
Possible solution:
1. Add the target migration user account as an owner to the necessary Private group in the target tenant or use another target account that is an owner and a member of the group.
2. Restart the uncompleted migration.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
The directory object quota limit for the Principal has been exceeded.
Error: Directory_QuotaExceeded: The directory object quota limit for the Principal has been exceeded. Please ask your administrator to increase the quota limit or delete objects to reduce the used quota.
Cause: The error about exceeding the directory quota may occur at creating new Microsoft 365 groups in the target tenant in case the target migration account does not have the tenant admin role. Maximum 250 Microsoft 365 groups can be created with a non-admin user account in the Microsoft 365 tenant. Only that number of groups will be created during the migration that will fit the limit of total 250 groups together with the existing groups previously created by that user. Other groups that exceed the limit will fail to be created with the Directory_QuotaExceeded error.
Possible solution:
1. Use another user account for creating the rest of the groups or use an account with the tenant admin rights as the target connection account for the migration, if it is necessary to create a great number of Microsoft 365 groups with one account during one migration.
Alternatively, remove the groups that were created during the migration in the target tenant, and relaunch the migration, selecting another Microsoft 365 Group Creation Mode, i.e. ‘Create all Plans in one group’ or ‘Create groups using source workspace names’, in the Migration Settings section to have a fewer number of Microsoft 365 groups created.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
MaximumProjectsOwnedByUser: The request exceeded allowed limits.
Error: MaximumProjectsOwnedByUser: The request exceeded allowed limits.
Cause: The error occurs on creating a new Plan in the Microsoft 365 group that already contains 200 Plans. There is a limit of maximum 200 Plans that can be created in one Microsoft 365 group.
If the ‘Create all Plans in one group’ migration setting is selected for the migration and the total number of projects to migrate is more than 200, only 200 projects will be created as Plans in a new Microsoft 365 group, and others will fail. If ‘Create all Plans in one group’ migration setting is selected and an existing Microsoft 365 group is specified, where there are already some Planner Plans, only that number of projects will be migrated which will fit the limit of total 200 Plans in the group together with the existing Plans.
Possible solution:
Restart the migration, selecting another Microsoft 365 Group Creation Mode that will lead to creating the rest of the Plans in different group(s), or migrate the projects to different groups in batches (in a few migrations). Make sure not to select more than 200 projects to migrate to one Microsoft 365 group.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
Invalid mapping for Title field
Error: Invalid mapping for Title field.
Cause: The error may occur on creating the target Plan tasks in case the Title task field has been mapped to a source text field different from the Name/Title field, and that field has no value in the source task(s). Consequently, the tasks could not be created with the empty Title.
Possible solution:
1. Select to restart the migration in Project Migrator.
2. Check which source field has been mapped with the Title task field in the Item Field Mapping section on the Restart Migration page. Change the mapped source field to the Title (text) field. In case another field needs to be mapped as the Task Title, make sure that the field is populated with values in all the items in the source Board(s).
3. Proceed with restarting the migration.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
Unable to update task fields/to assign users.
Error: Unable to update task fields: The attempted changes conflicted with already accepted changes. Read the latest state and resolve differences.
Error: Unable to assign users: The attempted changes conflicted with already accepted changes. Read the latest state and resolve differences.
Cause: The error may occur when there are items/tasks with the same names within one group/Bucket in the source project, and they have different field values set that may conflict during the migration.
Currently, items are differentiated by name within one group/Bucket in the source and target projects during the migration. Now, the items with the same names within one group/Bucket, that are migrated, are merged in the target project, and Project Migrator tries to merge their field values in one task as well. When the source field values are different for similar items, the conflict may occur that they could not be overwritten in the target item.
The errors ‘Unable to update task fields…’ and ‘Unable to assign users…’ indicate that the field values of the first migrated item have been set in the target task, but the field values of other items with the same name have not been set in the target project, overwriting the initial values.
Possible solution:
1. Check if there are items with the same names within a group/Bucket in the source project.
2. Change the item names a bit (e.g., add a dot to the end), or move the items with the same name to different groups/buckets in the source project, if possible.
3. Restart the migration in Project Migrator, selecting the ‘Create new and remove existing Plans before creating’ migration setting to create the target Plan and tasks from scratch.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
Failed due to the parent group "Group Name" fail
Error: Failed due to the parent group "Group Name" fail.
Cause: The project migration fails with such an error in case its group creation or update has failed, as the group is a parent entity to the project.
Possible solution:
1. Check with what error the migration of the project group has failed in the Data Migration Summary.
2. Try to resolve the cause of the group migration failure.
3. Restart the migration. In case the cause of the group migration failure cannot be eliminated, try to select another Microsoft 365 group creation mode in the Migration Settings at restarting the migration.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
Unable to create task: MaximumTasksCreatedByUser
Error: Unable to create a task: MaximumTasksCreatedByUser: The request exceeded the allowed limits.
Cause: All the Planner tasks are created by a migration account during the migration process. Planner has a maximum limit of 20,000 tasks that can be created by a single user account. As a result, if your source system has more than 20,000 tasks and you are using one account for migration, the error occurs.
Possible solution:
If your source system has more than 20,000 tasks you need to perform migration in batches using separate accounts (when the maximum number of tasks for one account is exceeded).
Unable to add/assign user: empty target user mapping
Warning: Unable to add user: empty target user mapping.
Cause: This warning indicates that a user has not been added as a member or/and as an owner to the target Microsoft 365 group and Plan since the source user had not been mapped to any target user in the User Mapping section before launching the migration.
Warning: Unable to assign user (user account): empty target user mapping.
Cause: This warning indicates that the user’s item assignments have not been set in the target tasks as the user had not been mapped to any target user in the User Mapping section before launching the migration.
Users themselves are not migrated from the source to the target system. Necessary users, that need to be added to the target groups and Plans, should already exist in the target tenant. The source users should be mapped with the target users in the User Mapping section for the correct group membership and assignment migration.
Possible solution:
1. Make sure that all necessary users that correspond to the source users already exist in the target Office 365 tenant.
2. In Project Migrator select to restart the uncompleted migration on the Data Migration Summary page.
3. On the Restart Migration page check the User Mapping section. Correct the user mapping, matching all necessary source users with the corresponding target users. Please see how to perform user mapping article for more details.
Also, the user mapping may be performed via an Excel file using the Export to/Import from Excel options.
In case the corresponding target user does not exist, and the source user’s group membership and assignments should not be retained in the target system, such warnings may be ignored.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
N assignments have been skipped due to limit of maximum 20 user assignments per task
Warning: 20 assignments have been added. N assignments have been skipped due to a limit of a maximum of 20 user assignments per task.
Cause: A warning of that type occurs if there are more than 20 users assigned to one item in the source project, or there would have been more than 20 user assignments in one task in the existing target Plan. As there is a limit of a maximum of 20 user assignments per task in Microsoft Planner, only users that fit the limit will be assigned to the target tasks during the migration, and others will be skipped with the warning.
Possible solution:
Check how many users are assigned to the items in the source project(s), and which users have not been assigned to the corresponding tasks in the target project(s). If needed, change the assignments in the target project(s) manually, or remove the unnecessary user assignments in the source project(s) and remigrate them with Project Migrator, selecting the ‘Create new and remove existing Plans before creating’ Plan creation mode in the settings.
If the skipped user assignments should not be retained in the target, the warning may be ignored.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
Unable to process attachment (name): invalid URI
Warning: Unable to process attachment (name): invalid URI.
Cause: The warning concerns the attachments of the Link type added to the source items. In case an invalid link or a link in an invalid format is added to the source item, it cannot be processed during the migration, and such an attachment is not migrated with the warning.
Possible solution:
1. Check the link attachment(s) in question added to items in the source project(s). Make sure that the link(s) is valid, and that the URL is provided in the correct format.
2. Restart the uncompleted migration for the necessary project(s).
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
Unable to process attachment: empty name
Warning: Unable to process attachment: empty name.
Cause: The warning indicates that the source item attachment, a file, or a link, could not be processed and set to the target task as the attachment name is empty in the source.
Possible solution:
1. Check the task attachments in the source project. Make sure that the attachment name, i.e., Text to display, is specified and that the attachment URL is valid.
2. Restart the migration for the uncompleted projects.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
N attachments have been skipped due to the limit of maximum 10 attachments per task
Warning: 10 attachments have been added. N attachments have been skipped due to the limit of maximum 10 attachments per task.
Cause: The warning of that type occurs if there are more than 10 file or link attachments added to one item in the source project, or there would have been more than 10 attachments in one task in the existing target Plan. As there is a limit of maximum 10 attachments per task in Microsoft Planner, only files and links that fit the limit will be added to the target tasks during the migration, and others will be skipped with the warning.
Possible solution:
Check how many attachments are added to the items in the source project(s) (in the Link and File type columns), and which files or links have not been set to the corresponding tasks in the target project(s).
If needed, replace the attachments in the target project(s) manually, or remove the unnecessary attachments in the source project(s) and remigrate them with Project Migrator, selecting the ‘Create new and remove existing Plans before creating’ Plan creation mode in the settings.
If the skipped attachments should not be retained in the target, the warning may be ignored.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
Unable to set value "N" to Priority field/ Unable to set value "N" to Progress field
Warning: Unable to set value "N" to Priority field/ Unable to set value "N" to Progress field.
Cause: The warning indicates that the field value has not been set to the target task, and the default field value has been used in the target system. That case may occur if the field has a set of custom values in the source project, and those values have not been mapped with the corresponding target values using the Custom Lookup option. If the field is of the Number type, its source values may be not valid for setting to a task in the target system.
Possible solution:
1. Check which values are added to the field in question in the source project. In case the field is of the Number type, make sure that the values are valid. E.g., the valid values for the Priority field that may be added in the target Planner Plan are 1, 3, 5, 9.
2. Select to restart the migration in Project Migrator.
3. In the Item Field Mapping section make sure that the source field is mapped with the corresponding target field, and that the advanced setting ‘Use Custom Lookup’ is enabled for that field if it has a few custom values (the field is of the dropdown or status type).
4. In the Custom Lookup section select the necessary source field values from the dropdown to map them with the corresponding target field values. Please refer to the article How to perform item field mapping for more details.
5. Proceed with restarting the migration.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
Due Date "M/DD/YYYY 12:00:00 AM" cannot be earlier than the Start Date "M/DD/YYYY 12:00:00 AM"
Warning: Due Date "M/DD/YYYY 12:00:00 AM" cannot be earlier than the Start Date "M/DD/YYYY 12:00:00 AM".
Cause: The warning may occur in case the date in the source field that is mapped with the target Due Date field is earlier than the date specified in the source field that corresponds to the target Start Date field. In this case, the target system does not allow setting dates that conflict with the task, only the Due Date is set to the task in the target Plan, and the Start Date value is skipped.
Possible solution:
1. Check which values are set in the date fields in the source Project items, correct them if necessary.
2. In case the dates are correct, i.e., the start date is earlier than the due date, make sure that the date fields have been mapped correctly for the migration. For this, select to restart the migration in Project Migrator, and check how the date fields are mapped in the Item Field Mapping section on the Restart Migration page.
3. Correct the field mapping if needed and proceed with restarting the migration.
If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.