This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How do I export a Basecamp database so I can import it into another Basecamp database with the folder structure intact?

I was away from home for a while and thought I'd take the time to clean up many years of my "organically evolved" Basecamp folder and list organization. I made a copy of the database on my laptop, deleted the extraneous folders and cleaned up the important stuff. I was hoping to export as a GDB and import that back to my home database. No luck. It comes in as a flat list. I can't find a way to export or otherwise transfer from one db to another while maintaining the folder and list structure.

Is there a way or do I need to redo my work on my home Basecamp db?

  • I do this frequently. Everything is identical to the way it is on the original computer. Basically it's a backup from one computer to a centralized location

    This places the .Backup file in a place where both computers can get to it, such as a NAS or USB drive, etc.

    Then from the other computer restore from that same centralized location.

  • My experience with backup and restore is that it does not merge databases. That is what I am looking to do.

  • Gotcha, different scenario then.

  • According to my experience with BC, there is no easy way to merge two databases and I would really discourage of using the database format (*.gdb) at all. You can export to the gdb-format, but you cannot import without loosing all structure (folders, lists). That's almost useless for big databases. You would have to export every single list seperately. After re-importing all these lists to another DB you will need to manually rearrange your desired folder structure. That's a big mess! Unfortunately, there is no easy save and open option for databases included in BC.

    I have tried to find a way on how to work with a BC DB that is stored in the cloud (OneDrive) and can be accessed by all my computers remotely and consecutively. The only way of working that seems to be feasible for me is to manually backup the DB after every single modification and to store that backup file back to the cloud. First step with a different computer is then to restore the backup file and after work is completed to backup again. Following this inconvenient procedure allows at least to keep the structure. Nevertheless, big DBs take some time for backup and restoring, unfortunately.

  • This is off topic, closing this old thread