export from an anydbm-backed tracker produces .csv 
files with "is retired" set correctly.

import to a newly-installed sqlite-backed tracker 
completes, but on inspection through the web interface 
retired objects (users & issues are the two I have seen) 
have sprung back to life and are visible in lists & 
searches again.

import to a newly-installed anydbm-backed tracker 
completes correctly.

Bit of a bugger, because anydbm is starting to get a bit 
sluggish for us (and seems more so on Python 
2.3.2/dbhash than on the previous Python 
2.2.1/bsddb185) and sqlite is blazingly fast in 
comparison...

ActiveState Python 2.3.2 on Windows, with the current 
pysqlite (0.4.3 for Python 2.3) and sqlite dll (2.8.6).