Discussion Forums

Importing Outlook fields

 
Avatar
Lyncean
66 posts

I just imported a group of contacts from Outlook 2003 into Solve360 Pro.

Numerous fields whose names didn’t exactly match up are now duplicated: I now have a “Business Main” which is Solve360 lingo, and also a “Company Main Phone” which is Outlooks lingo and where the Outlook data is. I have a “Job Title” (Solve360) and a “Title” field with Outlook data.

There are now other fields I don’t want, that were imported anyway from Outlook (“Sensitivity,“ “Gender,“ “Anniversary,“ etc.)

Any other way around this? This was a test with a few contacts, but I’m about to import 2,500 more contacts and it would be a hassle to have to move all the data manually into the Solve360 fields.

I suppose we could delete the Solve360 fields and just go with Outlook names. But, with other staff members on our team bringing their data in one after the other, we’ll have to repeatedly delete the fields we don’t want.

Ideally there’d be a screen that displayed fields in Outlook and fields in Solve360, side-by-side, so that they can be matched up before the data is brought over. Certain fields could be unchecked so they wouldn’t import at all.

I think Now-Up-to-Date had this feature years ago, and I remember an old mobile phone syncing program that did too.

Avatar
Lyncean
66 posts

Hang on, I just discovered the “Map Custom Fields” feature in Outlook, the last step before it exports to the CSV file.

That’s the feature I was remembering from other programs. I guess I’ll size two windows on my widescreen monitor so I can see both at once as I match up the fields.

Any other tips on replicating exactly the Solve360 hierarchy time after time (since I have various groups of Contacts I’m bringing over) would still be appreciated.

Avatar
Administrator
3948 posts

As a reference here is a list of standard Outlook 2003 contacts fields http://is.gd/47ws

I did notice that there is a better mapping that can be used for two of the phone numbers which was set to:

  “Business Phone” => “businessphonemain”
  “Company Main Phone” => “companyphonemain”

We have now changed to:

“Business Phone” => “businessphonedirect”
“Company Main Phone” => “businessphonemain”

This is how we are now mapping the fields in currently:

“Title” => “title”
“First Name” => “firstname”
“Middle Name” => “middlename”
“Last Name” => “lastname”
“Suffix” => “suffix”
“Company” => Individual company records are created and links established
“Department” => “department”
“Job Title” => “jobtitle”
“Business Street” => “businessstreet”
“Business Street 2” => “businessstreet2”
“Business Street 3” => “businessstreet3”
“Business City” => “businesscity”
“Business State” => “businessstate”
“Business Postal Code” => “businesspostalcode”
“Business Country” => “businesscountry”
“Home Street” => “homestreet”
“Home Street 2” => “homestreet2”
“Home Street 3” => “homestreet3”
“Home City” => “homecity”
“Home State” => “homestate”
“Home Postal Code” => “homepostalcode”
“Home Country” => “homecountry”
“Other Street” => “otherstreet”
“Other Street 2” => “otherstreet2”
“Other Street 3” => “otherstreet3”
“Other City” => “othercity”
“Other State” => “otherstate”
“Other Postal Code” => “otherpostalcode”
“Other Country” => “othercountry”
“Assistant’s Phone” => “assistantphone”
“Business Fax” => “businessfax”
“Business Phone” => “businessphonedirect”
“Business Phone 2” => “businessphone2”
“Callback” => “callback”
“Car Phone” => “carphone”
“Company Main Phone” => “businessphonemain”
“Home Fax” => “homefax”
“Home Phone” => “homephone”
“Home Phone 2” => “homephone2”
“ISDN” => “isdn”
“Mobile Phone” => “cellularphone”
“Other Fax” => “otherfax”
“Other Phone” => “otherphone”
“Pager” => “pager”
“Primary Phone” => “primaryphone”
“Radio Phone” => “radiophone”
“TTY/TDD Phone” => “ttytddphone”
“Telex” => “telex”
“Account” => “account”
“Anniversary” => “anniversary”
“Assistant’s Name” => “assistantname”
“Billing Information” => “billinginfo”
“Birthday” => “birthday”
“Business Address PO Box” => “businesspobox”
“Categories” => Individual categories are created and links established
“Children” => “children”
“Directory Server” => “directoryserver”
“E-mail Address” => “businessemail”
“E-mail 2 Address” => “personalemail”
“E-mail 3 Address” => “personalemail3”
“Gender” => “gender”
“Government ID Number” => “governmentnumber”
“Hobby” => “hobby”
“Home Address PO Box” => “homepobox”
“Initials” => “initials”
“Internet Free Busy” => “internetfreebusy”
“Keywords” => “keywords”
“Language” => “language”
“Location” => “location”
“Manager’s Name” => “managername”
“Mileage” => “mileage”
“Notes” => “background”
“Office Location” => “officelocation”
“Organizational ID Number” => “organizationalnumber”
“Other Address PO Box” => “otherpobox”
“Priority” => “priority”
“Private” => “private”
“Profession” => “profession”
“Referred By” => “referredby”
“Sensitivity” => “sensitivity”
“Spouse” => “spouse”
“User 1” => “user1”
“User 2” => “user2”
“User 3” => “user3”
“User 4” => “user4”
“Web Page” => “website”

- The multiple address fields are combined into a single “address” field value in Solve360 (makes the system much easier to use and you really don’t lose any functionality).
- Categories and company records are automatically created and links established

We believe it is a better user experience to do the mapping automatically and simply have the user delete the unwanted fields than to force them through the mapping process.  This works well for most import formats, Outlook 2003 is fairly verbose.

Currently all these fields are required however only fields with data get automatically created i.e. if you remove the default data for Sensitivity, Gender, Anniversary etc the fields should not be recreated in Solve360.

Also, Title = “Mr. Ms.“ etc and Job Title = “President, Director” etc.  I think Outlook 2003 and Solve360 are in sync on this one.

Hope this info helps.

Avatar
Lyncean
66 posts

Very helpful, thanks. As with a couple of other things, the added info makes it all clear.  I agree, just dragging a few extra fields to the trash can is going to be a whole lot easier than going through field mapping in Outlook 2003.

I know we’re ahead of your Help function, so again—thank you for the remarkably fast and thoughtful replies.

Avatar
Administrator
3948 posts

You’re welcome.

BTW Our team deployed an update today that might help further.  The Outlook Express and Outlook 2003 export files will now be recognized and processed even if they don’t have the complete field set i.e. you can exclude/remove columns you don’t need from the Outlook export file.