I would recommend, leaving your old data behind - put it in read only mode and just reference it. Start clean. We did that back in 2009 when we migrated from an old custom app to ITSM.
Else you need to go through HPD:Help Desk and identify all the required fields, this isn't necessarily going to be straight forward, e.g. the customer name will need a people profile, unless you hard code this to the same person on all data imported, same would be true for owner or person assigned, etc... Then there's Companies, Vendor companies, Support Groups that are all going to reference their specific request/entry Ids on the foundation forms. So unless you're hard coding these on the data import, it could be a headache. Regards, Andrew C. Goodall Software Engineer Development Services [email protected] jcpenney 6501 Legacy Drive Plano, TX 75024 jcp.com -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mark Lyndle Johnson Sent: Tuesday, August 14, 2012 2:00 PM To: [email protected] Subject: Importing data from another source form into the ITSM Incident form Hello, My company recently purchased the ITSM suite 7.6.04 after running all of our ticketing processes on self-built custom-built Remedy forms. We're trying to import data from our old custom ticketing form into Incident, but we're running into a lot of errors in the process where some fields are not accepting the data and other fields (such as the customer info) are not displaying data at all after the import. Does anybody have a list of all of the fields that need to be populated in Incident in order for a data import procedure to function properly? Also, if the list had any recommended values for the fields, that would be great. Thank You, Mark _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
