I've just done a migration from sqlite to mysql. The only problem I had was when I exported the database from sqlite Date properties in one of my issue classes journal files were getting exported in the form <Date 2007-10-12....> i.e. the python class representation rather than a tuple. This was for actions of type "create".

When I tried to import that csv the eval fails on that. 

I fixed my immediate issue by modifying rdbms_common.py:export_journal.py and import_journal.py to output an eval'able value using the code already there for action type set.

Here's a patch:

--- rdbms_common.py     Wed Aug  1 10:28:17 2007
+++ /app/roundup/src/roundup-1.3.3/roundup/backends/rdbms_common.py     Tue Dec 19 03:00:29 2006
@@ -2509,7 +2509,7 @@
         for nodeid in self.getnodeids():
             for nodeid, date, user, action, params in self.history(nodeid):
                 date = date.get_tuple()
-                if action in ('create', 'set'):
+                if action == 'set':
                     export_data = {}
                     for propname, value in params.items():
                         if not properties.has_key(propname):
@@ -2542,7 +2542,7 @@
             l = map(eval, l)
             nodeid, jdate, user, action, params = l
             r = d.setdefault(nodeid, [])
-            if action in ('set', 'create'):
+            if action == 'set':
                 for propname, value in params.items():
                     prop = properties[propname]
                     if value is None: