G
Guest
Guest
In the past week I've received several private inquiries about using SugarCRM from this forum. I answered each and thought I'd combine the emails into a post as it might benefit someone, somewhere out there.
I want to run Sugar locally on my 4 computer workgroup?
As for Sugar, if you want to run it locally (which I do) you can download what is called their "stack" installer which contains MySQL, PHP, and Apache along with SugarCRM and it will install the whole mess on your local machine (see Download CRM Sugar Community Edition Free | Open Source Business & Social CRM - SugarCRM)
This is not a bad solution... however I've never used it on my local Mac.
How do YOU install Sugar on your local machine?
I recommend that people use the XAMPP package apache friends - xampp as I think it is a bit more flexible. You get Appache running first, then create a MySQL database using the included myPHPAdmin program that comes with XAMMP and make sure that is set up.
Then download SugarCRM and install it following the Sugar instructions (see Sugar Community Edition Documentation | Open Source Business & Social CRM - SugarCRM just as if you were doing it on your web host.
I like to test each component of the system one at a time instead of throwing the whole mess onto the computer. It's like washing the whites separately from the colored clothes... or something like that. (In 30 years of marriage I've never learned how to use a washing machine!)
You could put the XAMMP package on one of the machines in your workgroup and let all the others network to it or you could dedicate machine to it on the network. You can run the whole mess on a low-powered laptop... even an old one since you are going to have such low volume of "hits" with only 4 people.
Do you work locally or on the web?
Personally, I would run Sugar on your web server. That means people can hit it from anywhere they are. That's what I do. I also compress the database each hour and store that file on the server as well as transmit a copy of it to another server AND I have a script on my Mac that goes out and download that file, uncompresses it, and re-loads the copy of Sugar I have locally. I can help you with the scripts. They are easy... you can have mine.
I NEVER work locally. I only keep a somewhat updated copy locally in case I lose internet connection (never happens here.) Working on the web is just as fast for me and I can do it from my iPad in my car when necessary.
Sugar is not perfect for insurance but if your requirements are not too stringent, it works just fine. I use the free "community edition" version, but with four agents in the shop you might want to spring for the 5-seat paid version that has more whistles and bells. I've been using Sugar for about 5 years now and I keep it updated (easy to do) and I've never had a major problem with it.
What about vTiger?
Sugar has a huge user community that will help with questions you post on their forum.
I also have tried vTiger. Nice system. It is a "fork" of Sugar (they stole it fair and square!) It has some nice invoicing modules built in where in Sugar you have to install an add-on module (which I've not done.) I have no need of invoicing. vTiger has a large user base but it is run by a few guys in India. Sugar is a fairly large corporation in the US with a large development team. I'm just not trusting my system to two guys in India just yet!!! But lots of people like it so what do I know?
What about customization?
My suggestion is not to start doing any customization until you have your work-flow sorted out. I find that for most agents, they can use Sugar out of the box with very little change. I'll be happy to tell you how I use it when we speak. Basically, I keep it simple and don't try to get too fancy with the system. I never use "campaigns" or "projects" etc. but some folks do.
What is your workflow?
Everyone always gets entered as a lead. Usually I do not usually use Contacts. A Lead might be "Jones, Tom." If it is a group case it might be "Jones Company" and if I think necessary I'll use a Contact for "Tom Jones" but then it has to be an Account (see below) and I have a different "rule" for accounts. Most often I don't need Contacts I don't usually need to keep data on what policy each employee takes.
The most important field to me is the Description field because that is where I "log" the information about a case... like a diary. If she is accepted I "convert" the Lead to an Account using the Convert module (built in.)
I see no reason to keep policy info in my database but sometimes I will and if so I'll do it as a Note/Attachment.
I don't use the Sugar Email module too often because I find it cumbersome. A lot of my emails are "did you get the file" and I don't have to save that. I'll just make an entry in the "log" that I sent an email. Same for phone data, but some guys will keep a record of each call using the "Log Call" feature. When you "close" a call it will go to History for that Lead or Account.
One thing I also don't do is upload documents to Sugar... such as app PDFs or insurance flyers, etc. Why? Because when you delete them they are not erased from the database... they stay on the disk, but you can't get to them at all. I prefer to save this stuff to my web server and put a link to it in the Lead record Description. Yes, it takes a bit longer to have to upload to my server, but I like doing it that way. (I password protect all apps that I save on my server.) That said, if you have plenty of room you can upload all the documents you like.
What is the worst thing about Sugar?
One weakness I find with Sugar is that you can't create a Contact for a Lead, only for an Account.
I'll be happy to answer other questions. Contact me. I don't charge for answers, even if you offer to pay (lots of people do... which is nice. I tell them to make a donation here if they want to.)
Al
I am here... same house, same wife, 30 years... I have no life!
I want to run Sugar locally on my 4 computer workgroup?
As for Sugar, if you want to run it locally (which I do) you can download what is called their "stack" installer which contains MySQL, PHP, and Apache along with SugarCRM and it will install the whole mess on your local machine (see Download CRM Sugar Community Edition Free | Open Source Business & Social CRM - SugarCRM)
This is not a bad solution... however I've never used it on my local Mac.
How do YOU install Sugar on your local machine?
I recommend that people use the XAMPP package apache friends - xampp as I think it is a bit more flexible. You get Appache running first, then create a MySQL database using the included myPHPAdmin program that comes with XAMMP and make sure that is set up.
Then download SugarCRM and install it following the Sugar instructions (see Sugar Community Edition Documentation | Open Source Business & Social CRM - SugarCRM just as if you were doing it on your web host.
I like to test each component of the system one at a time instead of throwing the whole mess onto the computer. It's like washing the whites separately from the colored clothes... or something like that. (In 30 years of marriage I've never learned how to use a washing machine!)
You could put the XAMMP package on one of the machines in your workgroup and let all the others network to it or you could dedicate machine to it on the network. You can run the whole mess on a low-powered laptop... even an old one since you are going to have such low volume of "hits" with only 4 people.
Do you work locally or on the web?
Personally, I would run Sugar on your web server. That means people can hit it from anywhere they are. That's what I do. I also compress the database each hour and store that file on the server as well as transmit a copy of it to another server AND I have a script on my Mac that goes out and download that file, uncompresses it, and re-loads the copy of Sugar I have locally. I can help you with the scripts. They are easy... you can have mine.
I NEVER work locally. I only keep a somewhat updated copy locally in case I lose internet connection (never happens here.) Working on the web is just as fast for me and I can do it from my iPad in my car when necessary.
Sugar is not perfect for insurance but if your requirements are not too stringent, it works just fine. I use the free "community edition" version, but with four agents in the shop you might want to spring for the 5-seat paid version that has more whistles and bells. I've been using Sugar for about 5 years now and I keep it updated (easy to do) and I've never had a major problem with it.
What about vTiger?
Sugar has a huge user community that will help with questions you post on their forum.
I also have tried vTiger. Nice system. It is a "fork" of Sugar (they stole it fair and square!) It has some nice invoicing modules built in where in Sugar you have to install an add-on module (which I've not done.) I have no need of invoicing. vTiger has a large user base but it is run by a few guys in India. Sugar is a fairly large corporation in the US with a large development team. I'm just not trusting my system to two guys in India just yet!!! But lots of people like it so what do I know?
What about customization?
My suggestion is not to start doing any customization until you have your work-flow sorted out. I find that for most agents, they can use Sugar out of the box with very little change. I'll be happy to tell you how I use it when we speak. Basically, I keep it simple and don't try to get too fancy with the system. I never use "campaigns" or "projects" etc. but some folks do.
What is your workflow?
Everyone always gets entered as a lead. Usually I do not usually use Contacts. A Lead might be "Jones, Tom." If it is a group case it might be "Jones Company" and if I think necessary I'll use a Contact for "Tom Jones" but then it has to be an Account (see below) and I have a different "rule" for accounts. Most often I don't need Contacts I don't usually need to keep data on what policy each employee takes.
The most important field to me is the Description field because that is where I "log" the information about a case... like a diary. If she is accepted I "convert" the Lead to an Account using the Convert module (built in.)
I see no reason to keep policy info in my database but sometimes I will and if so I'll do it as a Note/Attachment.
I don't use the Sugar Email module too often because I find it cumbersome. A lot of my emails are "did you get the file" and I don't have to save that. I'll just make an entry in the "log" that I sent an email. Same for phone data, but some guys will keep a record of each call using the "Log Call" feature. When you "close" a call it will go to History for that Lead or Account.
One thing I also don't do is upload documents to Sugar... such as app PDFs or insurance flyers, etc. Why? Because when you delete them they are not erased from the database... they stay on the disk, but you can't get to them at all. I prefer to save this stuff to my web server and put a link to it in the Lead record Description. Yes, it takes a bit longer to have to upload to my server, but I like doing it that way. (I password protect all apps that I save on my server.) That said, if you have plenty of room you can upload all the documents you like.
What is the worst thing about Sugar?
One weakness I find with Sugar is that you can't create a Contact for a Lead, only for an Account.
I'll be happy to answer other questions. Contact me. I don't charge for answers, even if you offer to pay (lots of people do... which is nice. I tell them to make a donation here if they want to.)
Al
I am here... same house, same wife, 30 years... I have no life!