Classification: UNCLASSIFIED Caveats: NONE I have to make one assumption with regard to your question, and that is that your "new" and "old" systems are on different servers and use separate DBs. Our methodology for historical data access (versus "migration"):
- Only select tickets were "migrated"; that is, reproduced/rebuilt in the new system (mostly long-term projects, not "customer" issues). - SHR:ConsolidatedList is used as the basis for archive/reference data. We copied the form and about 1.5 years worth of data and use it for reporting and research of "old system" data. (We even improved the look of this form just for this purpose.) SHR:ConsList has much less "overhead" than HelpDesk. - Eventually, the old server is taken offline, but we KEEP the old ARSystem database on the SQL server (renamed to "ARSystem6"). NEVER throw away data! Even without an AR Server to present the data to the public, it's all there and accessible with SQL tools. Just some thoughts. Michael W. Luttmann Lead Remedy Developer Fort Carson DOIM 719.524.0514 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of LisaD Sent: Wednesday, November 12, 2008 3:33 PM To: [email protected] Subject: Re: ITSM 7 Data Migration Approach (not configuration) 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 <[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 -- View this message in context: http://www.nabble.com/ITSM-7-Data-Migration-Approach-%28not-configuratio n%29-tp20430545p20470958.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" Classification: UNCLASSIFIED Caveats: NONE _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
