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

Evaluation near done: what is the right way to migrate existing Crucible data to new machine?


I am interested in purchasing a Fisheye/Crucible license; up to now I've been using an evaluation license. What is the correct workflow to migrating my existing Crucible data from an evaluation machine to a new machine and installing a license?

Here is my way of thinking:

  1. Perform a backup of the evaluation machine (add to zip file)
  2. Disable the evaluation machine
  3. Install the software on the new machine
  4. Restore the backup onto the new machine
  5. Install the purchased license on the new machine

Does this sound like the correct flow? Is there a more automated way to migrate to a new machine?

Thank you


1 answer

1 accepted

1 vote
Answer accepted

Hi Matthew,

The approach you have described should work without any issues. You could also apply the purchased license key to the existing evaluation instance of the application.

Alternatively, migrating the FISHEYE_INST directory should also work and would eliminate the need to backup and restore the database.

Kind Regards,
Richard Stephens

I went with just tarring up the data directory on the old machine and extracted it to the new machine in a different area.

I'm still having issues with the migration (the connection to Jira has not been instated on the new machine) but I see the code review activity so I think this worked properly.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events