Implementing a new ticketing software for a helpdesk

Ticketing system change

Anyone have first hand experience of implementing a complete change in ticketing system

Best way to plan\implement etc
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Iamthecreator OMIT Admin/EE Solution GuideCommented:
Can you consider using a subscription based ticketing platform like Zendesk or Freshdesk?
I use Freshdesk for internal IT Ticketing ( around 60 Euros per month for a single seat )
It will save you a whole lot of hassle, designing, implementing and maintaining one.
You can try them out (trial available) and subscribe to it if you feel it meets all your requirements.
Indie101Author Commented:
I should have said we're changing to Autotask, would be great to see what planning is involved etc for any changeover from a project manager perspective but thanks for the comment :)
DevAdminSystem Engineer | .NET Developer | Microsoft MVP | Technical SpeakerCommented:
Take a look to GLPI
RobertSystem AdminCommented:
So first step I usually do is document how you want the new process to work then start building out a flow from there.

The last time I changed from Service now to MS Service Manager (with cireson portal) the biggest thing is planning out how you want it to work then building out the process and documentation behind the plan.

We spent several months planning and testing before the cutover.

Plan everything out from the process flow to when you want notifications to go  out and to whom.
Get the high level plan in place be sure to work with your helpdesk for process review to be sure it will work with their process or that their process can be changed to accommodate the tool.

Also consider if you are porting old tickets or if you will be finishing out the current open tickets in the old system. (as a transfer of data can cause other concerns such as data mapping etc.) We had to save the data due to audit reasons but didn't need it to be active in the new system.

Document everything including the reasons discussions were made as it will be helpful in the long run.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Indie101Author Commented:
Excellent thanks a million :)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.