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

SMAX to JSM migration


i am currently an intern at a company where i am asked to make a presentation about the pros/cons of migration from SMAX to JSM. i would love if the community share their experience about this migration, and what key features in JSM that made you choose the solution . Thank you so much in advance 

1 answer

0 votes

@Meriem Naim 

I hope to be able to help with this question as I have worked in a Micro Focus environment using OES. This is a little different than their directory solution but I think I can shed some light on migrations. 

Migration with Atlassian take time. One of the things I have done is build out JSM to provide a better experience then the system they have come from. 

If you tried to create a JSM project before to see how it would work for your team?

If you want to migration issues from one service to another if your able to do a CSV export you can import them to JSM. Another thing you can do is use a middleware software like UNITO to connect both sites and run issues sync. I am not sure if UNITO would support SMAX but I am sure there is something out there that does. Other wise you would want to do a CSV migration. 

One of the issues is that to get the issue form the old system to the new system you have to be able to provide the same data points in both systems to map the fields and values. 

This can't always be easy and why I say sometimes migrating ITSM platform is not always easy. It might be better to work from JSM and see how it works and not migrate issues. Typically a fresh start works better. 

Hope this helps. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events