Best practices for catching Customers/Partners upon import | Community
Skip to main content
A
Anonymous
July 22, 2013
Solved

Best practices for catching Customers/Partners upon import

  • July 22, 2013
  • 1 reply
  • 807 views
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?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by
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.

1 reply

A
Anonymous
Accepted solution
July 22, 2013
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.
Terms & ConditionsAccessibility statement

Loading footer...