I’m new to EspoCRM (been exploring it for a couple of weeks now) and I’m impressed with how flexible it is. I'm currently planning a custom CRM setup for a small logistics company and I'm at a bit of a crossroads.
I’m debating whether to create entirely new custom entities for things like “Warehouses,” “Shipment Routes,” and “Fleet Vehicles,” or to handle these more as related fields within a couple of broader entities.
Before I go too deep and make structural choices that are hard to undo later, I’d love to hear how more experienced users approach this. Specifically:
Would really appreciate any insights or “wish-I-knew-sooner” tips from the community!
Thanks in advance.
I’m debating whether to create entirely new custom entities for things like “Warehouses,” “Shipment Routes,” and “Fleet Vehicles,” or to handle these more as related fields within a couple of broader entities.
Before I go too deep and make structural choices that are hard to undo later, I’d love to hear how more experienced users approach this. Specifically:
- When do you decide something should be a standalone entity vs. just a related field?
- Any lessons learned from over-complicating (or under-building) your schema?
- Does performance get impacted when you create too many custom entities?
Would really appreciate any insights or “wish-I-knew-sooner” tips from the community!
Thanks in advance.
Comment