Create a .csv File for Article Import

1. Create a .csv file to import articles.
   

   Note In Salesforce Classic, you import each article type separately, so you create a .csv file for each article type. In Lightning Knowledge, you can import articles of different types in one .csv file and set the record type during import.
   • There can only be one .csv file and one .properties file.
   • The .csv file and the .properties file must be in the root directory.
   • The compression process must preserve the folder and subfolder structure.
   • The .zip file name can’t contain special characters.
   • The .zip file can't exceed 20 MB and the individual, uncompressed, files within the zip file can't exceed 10 MB.
   • .csv files can't have more than 10,000 rows, including the header row. Therefore, you can have a maximum of 9,999 articles and translations.
   • .csv file rows can't exceed 400,000 characters.
   • .csv file cells can't exceed 32 KB.
   • Each article in the .csv file can't have more than 49 translations.
2. In the first row, specify the article's fields and metadata, such as title, language, data categories, and channels.

   Enter one item in each column. You can use the following fields and metadata to import content.

   Field or data	Description
   isMasterLanguage	Identifies the article as a primary (1) or translation (0). Required to import articles with translations, however, isMasterLanguage can’t be in a .csv file to import articles without translations. A translation must follow its primary article so that it’s associated with the primary article preceding it.
   Title	The article or translation's title. Required for all imports.
   Record Type	Indicates an article’s record type, for example, FAQ. Article import requires the 15-character, case-sensitive ID format.
   Standard and custom fields	Refer to an article type's standard fields using field names and refer to custom fields using API names. If the related article type field is mandatory, leaving a row cell empty can cause your articles to be skipped.
   Rich text area field	Use the rich text area custom fields to import .html files or images. Refer to an article type's rich text area field using its API name.
   File field	Use the file custom fields to import any file type (.doc, .pdf, .txt). Refer to an article type's file field using its API name.
   Data category groups	To categorize the imported articles, use category groups. Refer to a category group using its unique name prefixed with datacategorygroup.. For example, use datacategorygroup.Products to specify the category group Products.
   Channel	To specify where the imported articles are available, use the keyword Channels.
   Language	Specify the articles' language. Required to import articles with translations. Optional to import articles without translations. If you don't include this column, the articles automatically belong to the default knowledge base language and you can't import translations along with the primary articles.

3. In subsequent rows, specify the articles you want to import.

   Use one row per article, and enter the appropriate information in each field or metadata column. You can leave a column blank to skip importing data. For example, if some fields only appear in certain record types, enter values only for the appropriate articles of those types.

   

   Important All file names are case-sensitive and must exactly match what is in the .csv file.

   Consideration	Notes
   Standard or custom fields	Enter the articles' data for each field, except for rich text area fields where you must enter the relative path to the corresponding .html file in your .zip file. The article importer does not support subfields. If you have fields within fields, adjust your structure and content before importing into Salesforce Knowledge.
   Rich text area field	Always enter the .html file path relative to the location of the .csv file. Never enter raw text. If the specified path doesn't exist, the related article isn't imported. Note the following information about importing HTML and images. We recommend that you create one folder for the .html files (for example, /data) and another for images (for example, /data/images). To import images, include the images in an .html file using the <img> tag and src attribute. Ensure that the src value is a relative path from the .html file to the image folder. Images must be .png, .gif, or .jpeg files. Each image file can't exceed 1 MB. If you have multiple rich text area fields, create a separate .html file for the contents of each field. .html file contents can't exceed the maximum size for its field. If a date doesn't match the date format specified in the property file, the related article isn't imported. If an .html file references a file that isn't allowed, the related article isn't imported. If an .html file references an image that's missing, the related article is imported without the image.
   File field	In Lightning Knowledge, custom file fields are replaced with Salesforce Files. Enter the path relative to the file's location. If the specified path doesn't exist, the related article isn't imported. Note the following information about importing files. We recommend that you create a folder for your files (for example, /files). Each file must not exceed 5 MB.
   Category groups	Use unique category names to categorize articles. Use the plus symbol (+) to specify more than one category. For example, Laptop+Desktop. Note the following information about data category groups. Leaving the cell row empty causes your article to be set to No Categories. If you specify a category and its parent (for example, Europe+France) the import process skips the child category France and keeps the parent category Europe, because application of a parent category implicitly includes the category's children. When importing articles with translations and associated data categories, only the primary article retains the data categories. The article translations have no associated data category upon import.
   Channels	Specify articles' channels using the keywords. application for Internal App. If you don't specify a channel, application is the default. sites for Public Knowledge Base. csp for Customer. prm for Partner. Use the plus (+) symbol to specify more than one channel (for example, application+sites+csp to make an article available in all channels). When importing articles with translations and associated channels, only the primary article retains the channels. The article translations have no associated channels upon import.

Specify your import parameters in a property file using key names and corresponding values.