Summary

Learn how to handle the error "We couldn't import Sprint/Board '<name>'. Reason: 403 Forbidden" when migrating projects from Server to Cloud.

Overview

Specific permissions are necessary to run a migration plan using the Jira Cloud Migration Assistant (JCMA). Namely, you must be an admin in your server and the destination cloud sites (site-admin).

Sometimes, an admin must alter their permissions on the server instance to bypass the 403 Forbidden error described below.

These import error messages below might surface if you're affected by the lack of proper permissions on the server (the error will happen on the project-import phase of the JCMA plan on the cloud site):

ERROR <project key> project-import We couldn't import Sprint '<sprint name>'. 
Reason: 403 Forbidden: "{"errorMessages":["You currently don't have access to perform this operation."],"errors":{}}".

ERROR <project key> project-import We couldn't import Board '<board name>'. 
Reason: 403 Forbidden: "{"errorMessages":["You currently don't have access to perform this operation."],"errors":{}}".

The potential cause for this error is related to any changes to the Permission Schemes of the affected projects on Jira Server.

This can cause the user running the JCMA plan not to have permission to manage the projects - thus, the necessary permission to create those entities on the cloud site.

Solution

If your JCMA plan fails with this error, make sure to:

1. Grant the Administer Project permission to the admin user running the JCMA plan.
2. Remove the affected projects from the Cloud site as they may have been partially migrated - and purge them from the Trash.
3. Run a new migration plan for the affected projects.

For reference: Managing project permissions