Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

6.3 Upgrade to Cloud --

Hello,

i went through alot of the posts here but wanted to validate my understanding and limitations.

 

- To get from premise to cloud we are going to need 7.6 to use any migration tools (e.g. JCMA)

- my problem is we have Server core 6.3 on premise.  it is out of support so we don't have an option right now to get a free upgrade to 7.6. so support this.

 

What options do we have to drizzle data from this legacy instance so we can import it without having to pay another premise server license to get the ugpade?  

I looked at using "configuration manager for jira" add in but it wont install (we looked at the legacy version which was version relative). 

I am sure we can recreate all the instance data objects (users, groups, projects and re-assign).

 

thanks for any help or insight.

 

1 answer

0 votes

That version is pretty old! I think the way to go is to set up Jira Cloud as you really want it, and tell people to start using it. Make the old Jira instance read-only for most projects. After six months consider shutting the old instance down. The main downside is that reports are messed up for a few months. This problem is usually because an organization has not invested in keeping Jira to date, which is fine until they want to move to Cloud

the deprecation is part of the plan, but some projects need to come over … was trying to find a minimized solution here to get those which are active moved over.

Seems like one option is to create the new project, move some backlog issues over to a new sprint, leave the archive on the prem solution and then deprecate.

Any suggestion on a good export / import option which can minimize mapping onto the new project.  I am looking at export tracker right now which seems to get a good issues dump but field mapping is a problem, likely due to different versions of the agile template used previously.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

203 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you