This is sometimes easier said than done. We have a system that is made up of about 30-40 tables of associated data. The software itself allows many levels of

This is sometimes easier said than done. We have a system that is made up of about 30-40 tables of associated data. The software itself allows many levels of reporting on the data, and we take nightly snapshot backups of the data for restores. So, the customer need not worry about the integrity of their data or getting it back out in a meaningful manner. However, developing a system of export would not only be extremely expensive, but would be done so to allow our customers to leave. We are working on an API that would allow some interaction with the data, and I suppose someone could write a form of export tool from the API if they choose, but I don't think we are going to do this. I can see how important it might be to have export tools for a contact manager, or other small, single-use apps, but it's just not realistic, nor does it make good business sense when you have massive data sets and invest greatly into support and data backups/management.