Migration Remedy => ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2016 08:49 AM
Bonjour,
Un de mes clients souhaite migrer ces services de remedy í servicenow.
Son interrogation se pose sur la façon de procéder.
Y a t'il des outils qui permettent des migrations de service ?
Faut il redevelopper les services sous ServiceNow ?
Sachant qu'il souhaite créer de nouveaux services.
Ne faut il pas reprendre le projet depuis le début et concevoir une matrice cohérente avec l'ensemble des besoins.
Avez-vous un avis ?
Y a t'il des rapports d'expérience sur ce type de projet ?
Quelles sont les formations les plus adéquates pour le cadrage de ce type de projet.
Merci,
Nicolas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2016 09:00 AM
You may want to translate to English to you get a complete help.
I figured it out as migrating from Remedy to ServiceNow by title. If you could translate and repost, I can provide some help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2016 08:16 AM
One of my clients want to migrate servicenow to remedy.
His question arises on how to proceed.
Are there tools that allow service migration?
Should it redevelop the services under ServiceNow?
Knowing that he wants to create new services.
Should he not take over the project from the beginning and develop a coherent matrix with all requirements.
Are there any reports of experience on this type of project?
What are the most appropriate training for framing of this type of project.
Thanks

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2016 08:28 AM
The company I work for did this just over a year ago. We were on Remedy ITSM 7.6.3 but we didn't really migrate. We had just configured ServiceNow the way we wanted it and moved over. The only thing we migrated from remedy was open incidents and that was done by creating a button on the remedy incident form that pushed the data from that ticket into ServiceNow with a web service. Requirements were gathered from other departments and development in ServiceNow started. We began the project in October 2014 and went live on March 15 2015. The upgrade was very successful.
We also had the great people at Cloud Sherpas (now Accenture) help us with the upgrade.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2016 06:58 PM
Hi David,
can you explain it in more detail, what approach did you follow? was there any difficulties? What about SLA related to those records?