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

Jira Cloud to Server move blocker

I am attempting to migrate our company from Cloud to Server.
I have the installation set up and the database (on a different server) is able to be connect and build Jira normally just fine.
When I try to do the import existing data I get this error:error3.PNG

We thought it was collation since we are going from Cloud to a Microsoft SQL Server 2016, so we changed the collation, but still this error. Gotten it three time now.

Huge blocker.

Any help is appreciated.


1 answer

0 votes
KellyW Atlassian Team Oct 21, 2018

Hi Aaron,


It seems that you may be have encountered a known bug reported here -- Import from Cloud to Server fails: value too long for type character varying (60).


The issue is related to the recent update to the username field. 


Please update the column maximum length with following SQL query and let us know how it goes:

ALTER TABLE os_historystep ALTER COLUMN caller TYPE character varying(255);



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events