2011 User's Guide Copyright

If your file uses only ASCII characters, save the file as a comma-delimited values (.csv) file.

1. 
   In Excel 2007, click the Microsoft Office Button , and then click Save As.
   

In Excel 2010, click the File tab, and then click Save As.

2. 
   In the Save as type list, click CSV (Comma delimited (*.csv).
   

If your file uses non-ASCII characters, save the file as a Unicode text (.txt) file.

1. 
   In Excel 2007, click the Microsoft Office Button , and then click Save As.
   

In Excel 2010, click the File tab, and then click Save As.

2. 
   In the Save as type list, click Unicode text (*.txt).
   
3. 
   Use Notepad to open the .txt file.
   

8. 
   Search for commas in the file. Enclose any data that includes commas with quotation marks. For example, if you have 23 State Street, Apt 2, change it to "23 State Street, Apt 2" in the file.
   

Make sure the first line of the file contains column headings.

Make sure that the .csv file does not contain:

• 
  Multiple lines in the first line (header row).
  
• 
  Quotation marks in the first line. In Microsoft Dynamics CRM, quotation marks are used as data delimiters.
  
• 
  Data separated with a semicolon (;) or comma (,). In Microsoft Dynamics CRM, semicolons and commas are used as field delimiters.
  

To use automatic mapping, which is required for importing data that contains references to existing Microsoft Dynamics CRM records, column headings must match field display name values in Microsoft Dynamics CRM.

• 
  To identify display name values, open the form for the record type as if you were creating a new record. The labels on the form typically match the display names, although it is possible for your system customizer to have changed the form label values. If you have the appropriate security role, you identify display names in the Customization area:
  

1. 
   In the Navigation Pane, click Settings, click Customizations, and then click Customize the System.
   
2. 
   Open the entity, and then click Fields.
   

• 
  If you are working in a multi-language environment, automatic mapping of columns uses the display names from the user interface language, set on the Regional Options tab of the Set Personal Options dialog box. More information: Set Personal Options (on page 194)
  

Make sure the first column heading is not the name of a record type.

Make sure data exists for all business-required fields.

The following list shows default business-required fields for commonly imported record types.

• 
  Account: Account Name
  
• 
  Contact: Last Name
  
• 
  Lead: Topic, Last Name, Company Name
  
• 
  Product: Default Unit, Unit Group, Decimals Supported
  
• 
  Campaign Response: Parent Campaign, Subject, Owner
  

You cannot use a data map to import data if your data is connected to existing Microsoft Dynamics CRM records. You must use automatic mapping, which means your column headings must match Microsoft Dynamics CRM display names.

• 
  The value in the column that refers to another record must be unique in the primary attribute for the related record. The lookup is not case-sensitive.
  

The Parent Customer attribute can be resolved either to an account or contact. The Import Data Wizard looks for a unique account or contact record. If there is a contact record and an account record that have identical values in the Account Name field in the account record and the Full Name field in the contact record, the record will not be imported.

• 
  The value in the column can also be a Microsoft Dynamics CRM globally unique identifier (GUID).
  
• 
  If the column in your source file that is used to create the relationship contains multiple values, edit the data to contain just one value.