Hi,
At the Science Museum, we have legacy ticket data from our previous software, in v11 (and previous versions) in Ticket History. In testing the migration to v12 this valuable information is not longer readily available. While we like the greater detail in the v12 History, we don't want to lose ready access to legacy data. Have any other organizations encountered this? How are you handling it? Are there any alternatives for scripted "back filling"of this data into v12constituent records post migration?
Thanks.
Ray
Hey Ray -
Our legacy history didn't contain too many custom elements - and since the tables themselves didn't have to go away, I converted from the old ticket/sub history tables into the new ones. There were a couple of columns that didn't have spaces, and the plan is, if we need the information in those columns (which I doubt we will, but you never know) we'll refer back to the old history tables.
As for some of the required new columns, I made up some 'conversion' types of data for those - which is pretty similar to what we did when we actually converted.
It was pretty easy and smooth for us, but we had not highly customized our history already. So for smaller and/or less customized organizations out here, I'd definitely recommend making the switch. For you big beasties or highly customized people you might look at other options first!
- Heather
Heather,
do you recall how the old ticket/sub history tables were "converted" into the new ones? We're now dealing with this after finally upgrading to 12.5 and it's a little daunting having to recreated hundreds of lists and extractions with new keywords. Is it too late for us to do some kind of conversion of our tables?
Thanks in advance for replying.