A couple of people have asked me about where I am with this, so I'll post an update.
I decided to go with Podio.
Here are some of the positives and negatives that I have seen with it.
Positives:
- I am able to import a list from Excel and specify the mapping of columns to fields that I've set up in Podio.
- I am able to specify fields on import that are "key" fields, so that duplicates will not be imported.
- I can re-export a sub-selection of my Podio database to Excel, which I can then submit to a mailing service.
- Podio automatically logs a history of every change that is made, along with who made the change and a time/date stamp. I can see exactly what was changed for each edit and revert the change if I want.
- When I search for an entry, it shows me results as I type (kind of - it's a web interface, so there is a delay, but it's fine)
- I can attach files to entries in Podio, such as pictures of the property, contractor bids, rehab analysis, or whatever.
- The Podio database is in the cloud, so both my partner and I can access it from any web browser and also from a mobile phone App.
- There is some task creation functionality, which looks like it might be cool (similar to ZoHo), but I haven't used it yet.
- Their forums have a lot of information.
- It's free if you only have a few users (I think 5 or less)
Negatives:
- It's a little tough to figure out what's going on initially. The developers chose not to use standard database nomenclature, so there is an extra unnecessary barrier to entry. Also, their introduction tutorial isn't very useful, and the interface is often unintuitive.
- I can't save a default mapping of Excel columns to Podio fields for importing.
- When duplicates are detected on import, the original entry is updated with "new" info from the duplicate and there isn't an option to have it just ignore the duplicate.
- I can't choose which fields to export to Excel, so I have to remove columns after export.
- The Podio database is in the cloud, so if the Internet is down or slow, accessing it can be frustrating.
- There is no built-in functionality to back up the Podio database, either automatically or manually.
- It would be nice to be able to specify one or more fields and have Podio search for duplicates using those fields.
- On import, if Podio sees what it thinks is a date, it converts it to its internal date format, which is annoying because it also adds a time to that field, like this: 2014-05-29 00:00:00.
- It strips out comma separators from numbers when importing from Excel.
- A number of little annoying/frustrating interface issues.
Overall, Podio working okay for us so far, but some things have me concerned. A built-in backup system seems like a crucial bit of functionality, especially for a database in the cloud. I can manually export each table to an Excel file, which is fine for me because I only have one table so far, but this doesn't seem like a good solution. Another global issue is that the developers seem to ignore requests for some really basic functionality (especially interface functionality) that ought to be very easy to implement. They are probably focusing on larger systems, but I have seen simple requests from people made a few years ago that still haven't been implemented.
Anyway, that's where I'm at. As a free system (for now), I can only grumble about Podio's rough edges. But now that I have it set up, it seems to be working okay and does what I need. And my partner and I both have easy access to one central database.