I offer a fixed price data migration service using Meta-Update. Other companies have implemented their own migrations using Meta-Update. In one example, a customer's off-shore team developed their own scripts to migrate a heavily customised multi-tenanted ITSM 5 to an OOTB ITSM 7. This after a one-hour ppt presentation for three of their on-shore managers. To quote: "We had a mammoth task of migrating 400+ companies from ITSM 5.5 to ITSM 7.1. Initially this task looked very complicated as the 5.5 system was highly customized and the migration into mismatched schemas looked impossible. 1500 SLAs for these customers added to the complications.
"But when we started evaluating Meta-Update, we saw some light. We can now migrate SLAs, implement complicated transformation rules, stamp mapping values by looking up external configuration files, read from multiple servers, etc. Best part is that once Meta-Update scripts are done and tested, you can repeat it for any number of times. I recommend Meta-Update for all those who want the flexibility of a scripting language to handle bulk ARS data." The fixed price migration service covers all aspects of a migration which include data cleansing - a requirement of valid ITSM 7 data - mapping sessions (ie value, class, transformations). All diary fields are handled, all attachments, all tickets, changes, CIs or assets. No ARS server changes are required at all. The final production migration happens on a weekend. Monday morning, all open changes and tickets are there (as well as historical data) assigned to the right groups, with their attachments, work logs, associations, etc, ready to be worked on. If interested in finding out more, please contact me off-list, or please request a fact sheet. ( Attachment rejected.) Cheers Ben Chernys Senior Software Architect Software Tool House Inc. Canada / Deutschland / Germany Mobile: +49 171 380 2329 GMT + 1 + [ DST ] Email: <mailto:[EMAIL PROTECTED]> mailto:[EMAIL PROTECTED] Web: <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com A free notepad for Diary fields: <http://www.softwaretoolhouse.com/downloads/DiaryFieldEditor.htm> http://www.softwaretoolhouse.com/downloads/DiaryFieldEditor.htm An ARS API scripting tool used for migrations, integrations, imports, reports, extracts, batch jobs: <http://www.softwaretoolhouse.com/products/SthMupd> http://www.softwaretoolhouse.com/products/SthMupd _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Ivan Runions Sent: November 13, 2008 4:00 PM To: [email protected] Subject: Re: ITSM 7 Data Migration Approach (not configuration) ** I concur with Lisa. While we've only done it once, option #1 is exactly what we did. Despite the client initially "needing" all the data in the new ITSM application, there have been no problems with all the old data existing only in the read-only form (people never need the old data as much as they think they will). We chose this method based on cost. -ivan- LisaD wrote: I have also used flavors of option #1 4 out of 4 times, successfully. initially, client's thoughts are of course to migrate data into the new version obviously. however, that option has not proven to be cost effective to date, and they ended up being perfectly satisfied with holding it somewhere for reference only. incidents thata are not closed out by X date are required to be entered into the new form. Roger Justice wrote: I have used the first option more than once and the customers were satisfied with the result. -----Original Message----- From: Jon Chau <mailto:[EMAIL PROTECTED]> <[EMAIL PROTECTED]> To: [email protected] Sent: Mon, 10 Nov 2008 6:40 pm Subject: ITSM 7 Data Migration Approach (not configuration) ** Hello Listers, I am working on a migration to ITSM 7 from ITSM 5.5 applications and was wondering how most of your clients or organizations decided to handle the migration of historical and archived data (primarily the Help Desk form).? The plan of course is to migrate any existing open cases in the new system. Some of my options appear to be: Make a copy of the old HPD:HelpDesk form that users can search, and just move everything that is closed there. Attempt to map the old CTI structure into the new one to migrate the data into the new ITSM 7 HPD:Help Desk form (seems extremely difficult given the fact that we will be attempting to restructure categorization into the Operational and Product offerings -- although we will have to do this for the open cases). Thanks in advance! Jon __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ----- Lisa D -- Ivan Runions Information Technologies University of Calgary Calgary Alberta Canada (403) 220-4437 __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
