But I wouldn’t touch software that claimed to be able to do two-way synchronization between DT Pro databases with the proverbial 10-foot pole – although I’ll try out one suggested as experimental by Christian, on copies of my databases.
Yes, it may be possible. But the monolithic structure of the current database makes two-way synchronization a non-trivial problem. It’s easier to synchronize files stored in the database Files folder than in the database body. And it’s easier to handle file changes than database organizational changes.
DT Pro 2.0 will introduce a new database structure that will make many current synchronization problems go away, or become easier to resolve.
But I do in fact manually handle movement of DT Pro databases back and forth between my iMac and TiBook, when I take trips. Here’s how:
 The easy scenario. Copy the database package from the iMac to the TiBook. Or copy the database package from the iMac to a portable FireWire drive that I’ll hook up to the TiBook, and on which I’ll actually open and run the database (my current practice). Make content additions, deletions and edits as desired. On return from the trip, simply replace the database copy on the iMac with the database on the TiBook or the portable drive.
 A more complex scenario. I’ve transferred the database to the TiBook as above and made changes. Here’s a complication. Changes are also being made to the database on the iMac at the same time, either by me or by someone else. Here’s how I end up with a database that contains the new contents added to both databases. I choose the database on which the smallest number of changes was made, open Tools > History and select all the items that were added during the time interval of multiple use. In the Finder, I create a new target folder to which I will export those added documents. Back in DT Pro, I select File > Export > Files & Folders for the selected History items, and send them to my target folder. Assume this is the database on the iMac. Now I can replace it with the database copied over from the TiBook (or FireWire drive), and then do File > Import > Files & Folders into that database. Result: I’ve got a new database that contains all the added content made on both computers during a specified time interval.
Discussion: There could be other changes that couldn’t be handled by approach . Example: I totally reorganize the group structure and move contents around between groups in one database. Unless this is the database that I keep and import added content to, I would lose all that work invested in changing organization.
When version 2.0 is released, the database structure will be modified and many synchronization issues will be easier to handle. But that isn’t to say that I would immediately trust off-the-shelf two-way synchronization software to manage my database movements and consolidations. Misplaced trust can be dangerous.