Export data to delimited files

Most customer relationship systems include a backup function that exports data to files. These files typically are in one of the following formats: delimited text (.txt), comma-separated value (CSV) files , XML (.xml), or Microsoft Office Excel (.xls or .xlsx).

The Import Data Wizard requires all files to have a .csv, .txt, .xml, or .zip extension, so if your backup system creates other types of files, you need to convert the files. The text inside the .csv files can use your choice of delimiter: it does not have to use commas.

  1. Put each type of record into a separate file:
    • Specify a file name for each record type:
      • If you select Map Automatically then Import Data Wizard tries to match the file name with the record type name in Microsoft Dynamics CRM Online. For the most efficient matching, the file name and Microsoft Dynamics CRM Online entity display name should match.
      • If you are using a data map, the file name must match the value specified in the SourceEntityName parameter in the <EntityMap> element for the record type.
      • If you are using a data map but the file name does not match with the name in the map then the file is shown as "Not Mapped". You can manually map it in the Import Data Wizard.
    • Store Notes and Attachments in separate files from the records they are associated with.

      More information: How Notes and Attachments Are Imported

    • Store Addresses in a separate file.

      More information: How Addresses Are Imported

  2. The data in each file needs to be correctly delimited, and all files in one import must use the same delimiters:
    • Separate each column of data with a consistent field delimiter: a comma (,), colon (:), semi-colon (;), or tab character (\t).
    • If the data for any column includes the field delimiter, surround the data with a data delimiter: a double quotation mark (") or a single quotation mark (').

      For example, if you use a comma as the field delimiter and your source data contains an "Address" column that includes a comma, such as Route 1, Apartment 2, you would surround this data with data delimiters. Typically, double quotation marks are used as data delimiters, so your source row would include "Route 1, Apartment 2".

  3. If needed, convert your files to have the .csv extension. How you do this depends on whether your data uses ASCII or non-ASCII characters.

    If the data is in XML format,open the file in Excel.

    If the data is in Excel files and uses only ASCII characters, save each file as a .csv file.

    If the data is in Excel files and uses non-ASCII characters, convert each file to Unicode or UTF-8.

  4. If there are no column headings in a file, adding them is recommended.
    • Review the column headings in each file:
      • If you select Map Automatically, the Import Data Wizard tries to match the column name with the field name in Microsoft Dynamics CRM Online. For the most efficient matching, the column heading and Microsoft Dynamics CRM Online field display name should match.
      • If you are using a data map, the column heading must match the value specified in the <SourceAttributeName> element in the <AttributeMap> element for the attribute.
      • If you are using a data map but the column name does not match with the name in the map, the column is shown as "Not Mapped". You can manually map it in the Import Data Wizard.
  5. Make sure all your files conform to the following file size and row length limits:
    • Any .csv, .txt, .xml file should not exceed 8 megabytes (MB).
    • Any individual file in the .zip file must not exceed the limit of 8 MB and the total size of the .zip file including the Attachment folder must not exceed 32 MB.
  6. Remove any new line characters (\n) from the data in your source files. If data contains new line characters, the record will not import.
Did you find the information that you need?
Yes      No 
If not, what information do you need? (optional)