I love SugarCRM but.....

**kporter** · 2006-09-12, 11:17 PM

This will be my first post to these forums. In the process of evaluating, testing, and setting up SugarCRM, it feels like I have read every post here. Know that I haven't though, I wanted to post my 2 of my major issues with Sugar and see if anyone has any input.

1) When importing leads, Sugar tells you how many were imported and how many weren't, but there is nothing to indicate what wasn't imported. This is quite unnervind and seems to make importing a real pain.

2) I still can't believe that Sugar doesn't offer some type of functionality to link custom fields from one account to another. I had to create about 15 custom fields as wells as the custom PHP code to allow those fields to carry from one module to another. This to me seems to be a major drawback. Especially since I imagine an upgrade means I will have to go back an MANUALLY tie all the modules back together again. I just can't believe that Sugar would be built to be so difficult have custom data moved from one module to another. Especially since CRMs usually only provide functionality and a framework. I don't know anyone that purchased a CRM because it had the exact data fields and workflows that are needed right out the box.

Any input would be appreciatted. I really like Sugar, but I can see where the process can become a little overwhelming.

**Scott_Savage** · 2006-09-13, 12:59 AM

Originally Posted by kporter

I just can't believe that Sugar would be built to be so difficult have custom data moved from one module to another. Especially since CRMs usually only provide functionality and a framework. I don't know anyone that purchased a CRM because it had the exact data fields and workflows that are needed right out the box.

Good call kporter, I agree with this as well. I think this is where Sugar's ability to be customised by a non-developer breaks down (I still don't believe that a decent implementation of Sugar can be made without some coding to tailor the software). I can see why this would be a pretty hard piece of functionality to implement however. The best way I can think of is by using a similar design method to the drop downs (ie. you add the field in the high level area and then apply those custom fields in each module). I guess if you could then define a group of high level fields and then just specify the module that would be what you are looking for?

longreach · 2006-09-13, 01:53 AM

I can't say I agree that clients purchase a CRM only expecting a framework. I do think this was true years ago - but the impact since 1999 of Salesforce.com as a ground-breaker, and nowadays with SugarCRM at the forefront of the revolution in CRM value have changed the game. I think the products are much better than they used to be - but more importantly - the customers are much less sophisticated, and have much smaller budgets. In order for CRM to penetrate the SME/SMB space - it has had to become much more shrink-wrapped. We sell exclusively to businesses or business units of 200 users or less - and nowadays about half of the sales get no more customization than by the client in the studio. But could the studio be better - of course - and I'm sure it will get better and better over the years to come. The improvements in 4.5 are a very nice step along the way.