SOLVED

Best practices for catching Customers/Partners upon import

Go to solution
Anonymous
Not applicable

Best practices for catching Customers/Partners upon import

Hello all,
 
I wanted to check in and see if you had any best practices for catching Customers/Partners upon import. Right now, I am doing this based on email and the naming convention. If the naming convention matches, we have a checkbox checked Any other thoughts?
Tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

Re: Best practices for catching Customers/Partners upon import

It's a bit like building rules in in your mailbox for filtering all your messages. You can get pretty good, but can't ever account for every situation. I'd say you're off to a good start with the practices you're following,  though I doubt there's any perfect solution out there.

Generally when I'm importing lists, data with customer/partners is a pretty common occurence, so I usually pull in the data on the SFDC side and use things like demandtools to resolve duplicates & match data up more efficiently.

InsideView is another interesting approach to importing.

View solution in original post

1 REPLY 1
Anonymous
Not applicable

Re: Best practices for catching Customers/Partners upon import

It's a bit like building rules in in your mailbox for filtering all your messages. You can get pretty good, but can't ever account for every situation. I'd say you're off to a good start with the practices you're following,  though I doubt there's any perfect solution out there.

Generally when I'm importing lists, data with customer/partners is a pretty common occurence, so I usually pull in the data on the SFDC side and use things like demandtools to resolve duplicates & match data up more efficiently.

InsideView is another interesting approach to importing.