To SNIP or not to SNIP!

Hi all,

we are considering turning on this feature and I’m getting conflicting opinions. Really convenient of course as we can just forward on an emails to be archived to an email address rather than using the plug in. On the flip side, I am being told that this would start making the database very bulky and the site very slow. Also as the emails are sent to SugarCRM servers in the US, we may not be GDPR compliant (being based in the UK).

any thoughts?

Thanks!

Parents

0 Adam Frank over 5 years ago

Seshagiri Sondur, regardless of whether you use SNIP, or almost any other email archiving solution, the impact upon size will be similar. So this really comes down to the maths - e.g. how many emails do you anticipate entering the CRM, and how large are they on average? If you've not measured before, I encourage you to take the last 1000 emails as a representative sample and do the calcs off that.

For the typical implementation, emails themselves don't have to be a big hit on the database size - usually its the attachments that have more of a disk footprint... and even then, unless you are moving around a lot of images/rich media, that may not add up too much. I noted in the other thread that you're leveraging email-to-case and have images (I'm guessing screenshots?) in those emails - but unless you're talking substantial volumes, even that will take awhile to notice.

On GDPR - you'll need to consult your counsel on that one, but be aware that part of your MSA with Sugar touches on what Sugar is allowed to do as the data processor. Sugar is not the data controller.

Reply

0 Adam Frank over 5 years ago

Seshagiri Sondur, regardless of whether you use SNIP, or almost any other email archiving solution, the impact upon size will be similar. So this really comes down to the maths - e.g. how many emails do you anticipate entering the CRM, and how large are they on average? If you've not measured before, I encourage you to take the last 1000 emails as a representative sample and do the calcs off that.

For the typical implementation, emails themselves don't have to be a big hit on the database size - usually its the attachments that have more of a disk footprint... and even then, unless you are moving around a lot of images/rich media, that may not add up too much. I noted in the other thread that you're leveraging email-to-case and have images (I'm guessing screenshots?) in those emails - but unless you're talking substantial volumes, even that will take awhile to notice.

On GDPR - you'll need to consult your counsel on that one, but be aware that part of your MSA with Sugar touches on what Sugar is allowed to do as the data processor. Sugar is not the data controller.

Children

0 Seshagiri Sondur over 5 years ago in reply to Adam Frank

Thanks Adam Frank all makes sense! No we definitely don't intend to upload massive files. There might be the odd ppt/excel/word files but that's it. Just to clarify, we are with a reseller so don't have a direct contract with Sugar. In this case, can you confirm how long emails are retained on Sugar servers?