Title basically tries to capture the gist of the question. I have been asked (volunteer) to assist in the project of migration from a proprietary, more costly CRM solution, to an Odoo Community "product", to be architected, configured, deployed in a cloud service and operated by a specialized partner. My specialization is in infrastructure (architecture, ops and security), so I could certainly validate mapping the apps functionality into the right components, but I have zero knowledge on how good the CRM part is, and - crucially - how to keep its possible need for customization in time and operations cost low, if internal org volunteers have no technical skills. I am concerned about the integrator attempt to get the foot in the door with an acceptable one time cost, then slowly ramp up the price, if this solution requires a lot of babysitting.
Does anyone have any experience with this Odoo Community CRM product and model, to share some gotchas, in the light of the above described attempt to use? Users max 300. The hope is to also have the CRM integrate with needed office products (doc, spreadsheet, email, etc.)
Since you mentioned migration - the data import process is where most projects get stuck. Odoo's import tools are decent but you'll probably need custom Python scripts for complex data transformations from your current CRM.
One thing I learned while building automation tools is that many small nonprofits actually need something simpler than a full CRM - often they just need better task management and follow-up tracking from their existing email communications. I've been beta testing ungrind.ai which handles that specific piece (auto-creates tasks from emails/meetings), though it's designed more for individual consultants than organizations.
What's your current CRM and roughly how many contacts/complexity are you migrating? That would help determine if Odoo Community's data model limitations might be an issue.