External Import Errors - ClickUp

[Tabee Evans]

Hi all

My company has some data in ClickUp we want to migrate across to Jira. I have been using the 'External Import' -> 'ClickUp' tool with inconsistent results.

I am an admin in Jira and an Admin in ClickUp. Our ClickUp plan is 'Enterprise' so there are no limits on exports.

My initial test on a small space was successful, however when I tried to import the larger space I started getting errors after I had selected my ClickUp space/List and completed the status and field mapping.

The import screen loaded for a couple of minutes before I was shown an error message 'We couldn't set up your project' which did not give me any code or explanation, neither did the email I received: 

The initial attempt was for 530 tasks, so I assumed it was the volume

After trial and error, reducing the list for import to 200 tasks worked.

Since this successful attempt, I have tried multiple times over the past 2 weeks to bring across the remaining tasks, splitting the lists in ClickUp to keep the volume down. I have not tried any import exceeding 200 tasks.

Randomly, an attempt for 80 tasks worked, however I have tried to import a list for 50 tasks within the same ClickUp space multiple times now and the same error is happening. 

 

I don't know if this issue is on the Jira side or ClickUp. I have read the troubleshooting documentation and I am not doing anything differently than I did for the successful imports I made.

Does anyone have any advice or suggestions? 

As a last resort, I can upload via CSV, however bringing across the historical comments and attachments is much easier via the import tool. 

Thank you

Tabee

[Jorge Luiz Lustosa Cammarota]

I am performing a migration from ClickUp to Jira, and the same problem appeared here. Here is how we managed to solve it by separating custom fields:

1. Create a copy of the list (or project/space) you need to migrate.

2. Right-click on the copied list (or equivalent feature in ClickUp) and remove the custom fields.

3. Attempt the migration with this version that has the custom fields removed.

4. If any error occurs, let me know (and we can look at migrating the custom fields separately later)."

[Tomislav Tobijas]

Hi @Tabee Evans ,

This import option from ClickUp is relatively new (together with the whole improved import experience).

Regarding some limitations, I believe they may be related to the large number of custom fields or complex field types in ClickUp. Reducing the complexity or splitting the import (as you've done) is recommended, but even smaller barchers can fail in some cases. 👀

If the system continues to throw an error, some next steps are to record the steps or screen captures of the import and reach out to Atlassian Support. The team there has some additional insights and potentially some resources that can help troubleshoot this further.

Cheers,
Tobi