Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

I want to know API or process to migrate from Clubhouse to JIRA. Can someone please help me?

I want to migrate from the clubhouse to JIRA with my all projects, EPIC and story points. 

2 answers

I built an application that does the job seamlessly. It will be available on the Jira App Marketplace shortly.

This is interesting.
We are migrating, but I've only migratet (manually...) a few ongoing projects.
An app to automagically migrate the entire project library from Clubhouse to Jira would be great.

Hi @Taiwo Ojo  - do you know when this will be available? It sounds like a great app

Like PucciG likes this

Any word on when you might release this tool?     If you have chosen not to release it, would you be willing to share the code?


Is this tool available? Not seeing anything in the Marketplace

We are also migrating a project out of clubhouse and have most of it, but comments aren’t included in the export. Has anyone gotten those to come out in any export? 

Thank you! 

@jay modi did you solve this?


We are too considering a move from Clubhouse to Jira, not because Clubhouse is bad but we need more features that Jira can offer but Clubhouse can't.

Would be good to do the move automatically or semi-automatically...

Hi Christopher,


I did the migration manually from the clubhouse to JIRA during the weekend. 


How? Just copy/paste manually? All text etc.?

I extract the issues from the Clubhouse in Excel. Map the field in JIRA and Import it. 

You run into a few issues doing it this way, it's a heavy manual overhead to try and mark up text, de-emojify, and align config. 

This is a process I have created a scalable solution for and will deploy an app to the app stores soon however happy to provide guidance and support to anyone that's currently migrating.

Like Aman Singh likes this

Hi @Taiwo Ojo. I'm about to embark on a Clubhouse to JIRA migration and am curious how far out you are from releasing your app?

Like # people like this

Same here @Taiwo Ojo is this released?

Any update on the APP for this migration ? I am still trying to find out how to migrate comments from clubhouse to JIRA.

@Taiwo Ojo Do reply, please. I have tried 4th time today to migrate the issue but it is anyway failing to throw this error



Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state: Caught PSQLException for insert into "public"."customfieldoption" ("customfield", "customfieldconfig", "disabled", "sequence", "customvalue")

values (?, ?, ?, ?, ?): ERROR: value too long for type character varying(255)


@Yashwardhan Pauranik : I'm seeing the same error exactly when attempting something completely different ... importing Jira Server project data to Jira Cloud. I'm not having any luck finding the culprit in the data. Did you ever learn anything regarding this error that might be helpful?

Thank you!

@Yashwardhan Pauranik  This error is caused when we have values that exceed the max character length.

While importing text fields (except Summary) the importer will import that record with a warning.

But when we try to import an option for a select list exceeding 255 characters, this error will be thrown.

(I figured it out when I was importing values for a multi-select field, but the data given to me had separated the values using semicolons, so all values were considered as a single string, and ran into this error.)

Suggest an answer

Log in or Sign up to answer