Contacts and Account Import Process

[mjchin]

Hi

I have a master list of account and contact information that I import. Part of the information is imported into accounts and part is imported into contacts.

The master list is updated daily because we receive store registration data on a daily basis and only one report is produced. That report is then converted to a CSV file and as you can imagine, it will grow in size.

The data that's imported into Accounts is using Name* as key and mapping to a store name in my master list.

The data that's imported into contact is using Last Name* as key and mapping to Last Name field in my master list. The "contact" information is using Primary Address, City, State, Zip.

In an initial test, I imported contacts from master list successfully, no errors were reported. I then made changes to some of the contact names in the master list and tried the import again (to simulate a change of phone number or address). I selected Import "Action Create and Update Records", however after importing I found instead of changes made to only the records I affected, the entire list was duplicated.

I was going to test the same for Accounts but thought I reach out to the community before attempting.

My question
Was there something I did incorrectly?
Is there a different key that I should have selected / select (for Accounts) or create (for both)?

This process for conducting the imports need to occur daily and records cannot be duplicated. Your assistance is greatly appreciated

Thanks
Marty

[tlck9]

On that latest version of Sugar which I have just installed. When I import as contacts, it will create an account providing I have included the account information.

However this will not populate the account with telephone number and addresses.

However when I import the account information there seems to be some problem, as it will not come up with account name, only Name* as an option. When I imported this with quite a long description it actually imported the desription as a seperate account....Ummmm

It looks like at the moment I can only import the contacts and manually create the account information, which is okay if you only have a few accounts, but for those that have hundreds this isnt going to be easy.

I am not sure if this answers your question, but when I have tested this, ensuring I have ticked the create and update field, it duplicates my information as well....

I remember importing with an earlier version and i'm sure that I did not have this issue then

[JBE2006Sugar]

As a newbie, I am having similar problems importing a CSV file from ACT 2009!

My problem is that the only useful info that gets imported in Sugar is the Account name and telephone number.

Address info is lost - nothing goes into the proper fields for either Contacts or Accounts,

Email addresses can not even be recognized at all (they look right in the csv with proper delimiters and qualifiers (")

and I have not even begun to figure out how to get history information into Sugar. (Given the fact that ACT doesn't do history exports, I suspect this will be a lost cause and we will have to rely on two systems for a little bit as old info becomes stale.)

To the point....if there any special processes to import an Act DB into Sugar other than the CSV and Tab delimted file route , neither of which appears to work despite proper mapping.

[christianknoll]

For tasks like that look at ETL Tools like Taledn Open Studio and you shoulöd be able to load all your data within a matter of some hours. We are happy to help you here and also support you with a ready to run ETL Model for that task and you specifric informations. Fell free to contact me on my personal email for a quote.

christian.

As a newbie, I am having similar problems importing a CSV file from ACT 2009!

My problem is that the only useful info that gets imported in Sugar is the Account name and telephone number.

Address info is lost - nothing goes into the proper fields for either Contacts or Accounts,

Email addresses can not even be recognized at all (they look right in the csv with proper delimiters and qualifiers (")

and I have not even begun to figure out how to get history information into Sugar. (Given the fact that ACT doesn't do history exports, I suspect this will be a lost cause and we will have to rely on two systems for a little bit as old info becomes stale.)

To the point....if there any special processes to import an Act DB into Sugar other than the CSV and Tab delimted file route , neither of which appears to work despite proper mapping.