This should be in the "known issues" section, but it looks like one can't put anything in that category. I and at least one other person have observed that when security prices for a security whose prices have been manually entered are converted from QM 2007 to 2019 (5.12.3) Quicken adds a price for the date the conversion is taking place, presumably after having tried to find it from the quote server and failing to do so. It appears that the new price entered is either the last price entered or something completely different. It doesn't seem to matter much whether the security has been assigned a notional (non-existent) ticker symbol or not, although if not very few of the prices get transferred over. In any case, this is not a desired behavior: if Quicken cannot get a quote from the quote server, it should not attempt to guess what price might be appropriate — suppose prices are only available once a quarter or even less frequently, and never on-line, the last price in the file for a security may be a long ways off from the next one that will be available (say, in a statement.)
0