RE: [EXTERNAL] Re: Old Remedy 6.3 data

Can’t speak to the other systems you mentioned, but as you said above the last line – it’s not unique to Remedy – ServiceNow also has the ability to build whatever tables / applications you want. From: ARSList On Behalf Of Jason Miller Sent: Friday, August 16, 2019 11:02 AM To: ARSList

RE: [EXTERNAL] Re: Old Remedy 6.3 data

Hi All, Our product, Meta-Archive , will produce html pages of all Remedy data, drilling down to any detail you’d like, with links to attachments - all through a configurable spreadsheet. Customizations and bespoke apps are

Re: [EXTERNAL] Re: Old Remedy 6.3 data

Regarding where to put the historical Remedy data... I once took an organization from Remedy ITSM to newly developed homegrown Remedy application. Similarly they needed to keep their ITSM Change Requests (Work Info, Audit, Tasks, etc.) for regulatory purposes. Like Carina suggested, in the

RE: [EXTERNAL] Re: Old Remedy 6.3 data

I’ve actually done a migration of the data using web services. Built a web service to get the records from Remedy and then built ‘read-only’ archive tables in the new system, pulled the data across into those tables. Attachments are a bit of a different story – used outbound email to

Re: [EXTERNAL] Re: Old Remedy 6.3 data

Regarding attachments, LJ built a tool for that :) http://remedylegacy.com/tools/db-attachments/ Jason On Fri, Aug 16, 2019 at 8:38 AM Kelly Logan wrote: > Going back to the original description, an archive system that is queried > a couple of times a year, I would agree with LJ LongWing that

Re: [EXTERNAL] Re: Old Remedy 6.3 data

Going back to the original description, an archive system that is queried a couple of times a year, I would agree with LJ LongWing that a good fit is to approach this from the database side and switch your Remedy queries to database queries. If you can keep the entire database intact that would be